Flux Evo Channel v20.12.0.49880-R2R

quote by rikyjachothe idea behind "phase group" is great, but I don't see how that can achieve a better result than using mautoalign, sound radix pi, or similar plugins

I read you, rikyjacho. But the Evo Channel is way more than the "phase group " .

yeah that's correct, just wanted to throw a comment in about that since u dedicated a comment specifically on the phase group stuff.

I'm particularly curious about if the evo channel's dynamic and non linear processing add partials to the signal, since the old r2r version cannot be loaded inside the latest r2r plugindoctor and therefore cannot be tested, at least on my end, but from what I've seen in the tests that I've conducted, almost all of the flux dynamic plugins barely seem to add any partials to the signal, even at their fastest settings (some of them does add partials just when very fast lookahead is applied), just when the signal is pushed very very hard they add some, but in the form of IMD; partials will eventually alias but it seems to be a trivial point.

I know they promote their plugins as "transparent" but if every dynamic plugin of theirs in the version 3 barely add partials and are responding in a similar linear fashion, then it seems to me that they are almost doing the same kind of processing, therefore it can be said that all of their dynamic plugins are identical bc they work very similar to each other. furthermore, since they respond more in a linear fashion, I think they shouldn't be called dynamics processors, they should be called something else. Those plugins seem to work as if they are forcing a hold time or something, similar to how the obsolete and hyper marketed metric halo's channel strip dynamic stuff worked.


quoting andy from cytomic about the metric halo's compressor:

"This plugin must have a hold time that isn't exposed to the end user. This means that even at the fastest compression time no compression is occurring, it is at a constant level, which is more like a automating the volume fader in your DAW. This can be useful for some things, but I have never seen such a built in hold time on an analog compressor in a console, but if anyone has the original analog hardware I would love to see some recordings of sine waves at different amounts of compression on the fastest attack / release times possible, perhaps there is such a hold time, who knows?"


"So in summary (this has already been stated many many times on this thread) if no harmonics are generated then no audio rate compression is happening, it's more of slow volume automation you get, just like drawing in an automation curve in your DAW. "


https://gearspace.com/board/music-computers/418022-lets-do-ultimate-plugin-analysis-thread-88.html


https://gearspace.com/board/music-computers/418022-lets-do-ultimate-plugin-analysis-thread-89.html

@Nephente
@Nanook
=>

quote by NanookYes I do. Don't you?
... and it seems it's the same in Reaper, according to Nephente.
I thought the previous R2R releases were just too old for latest Win10 but it seems the latest version (I'm assuming this is the latest release for EVO channel) behaves the same.
this can't be some bug from Flux's part, it has to be the protection, isn't it?

Nope, no bug AFAIC. Neither in Samplitude .

I use an " old " Windows 10 x64 ( 1709 - Fall Creators Update ) on a simple laptop.

that means the newer Windows 10's are the culprit. I remember using the old R2R release and not having this problem. (don't use FLUX plugs that much, in fact not at all lately) but I was just testing something and then I realized FLUX's do that. I thought the FLUX release is too old but it seems something related the the newer Wind if it works for you with an older release.

quote by Nanookthat means the newer Windows 10's are the culprit. I remember using the old R2R release and not having this problem. (don't use FLUX plugs that much, in fact not at all lately) but I was just testing something and then I realized FLUX's do that. I thought the FLUX release is too old but it seems something related the the newer Wind if it works for you with an older release.

Couldn't it be linked to the graphic card ? Pilot of the graphic card ?
But I don't know much here...
As in this " 1709 " version it works as it is, I forbid it to update, applying an old French adage : " Le mieux est l'ennemi du bien. " ( approx : " 'Better' is the enemy of 'good enough' ." )

or: "If ain't broke, don't fix it" :).
I just installed this new version of EVO and, the oddest thing, to complicate the matters further:
works in Reaper! (so I can't say why the OP has problems in Reaper)
but ... it still doesn't work in Sequoia/Samplitude. installs OK, you can open it once, but if you close the GUI, next time you open it it's all white, no controls. If you close the DAW and re-open, the same thing, works at the first launch ...
so it can't be Win, can't be the graphic card ... quite a mystery.

quote by Nanookor: "If ain't broke, don't fix it" :).
I just installed this new version of EVO and, the oddest thing, to complicate the matters further:
works in Reaper! (so I can't say why the OP has problems in Reaper)
but ... it still doesn't work in Sequoia/Samplitude. installs OK, you can open it once, but if you close the GUI, next time you open it it's all white, no controls. If you close the DAW and re-open, the same thing, works at the first launch ...
so it can't be Win, can't be the graphic card ... quite a mystery.

I've found about this today :

Flux audio / knowledge-base :=>

thanks DAW. yes, that makes sense, unfortunately I did not move any files, they are installed where they should be, default location. One thing I can think of is that they have this weird 4 level sub-directories, like it's an AAX plugin
EvoChannel.vst -> Contents -> Resources / x64
maybe Samplitude/ Sequoia can't cope with 4 levels of subdirectories.
could be something from the VstPlugins.ini like
DirectoryRecursionDepth=2
DirectoryDisplayDepth=1

I should try changing those and see.

quote by Nanookthanks DAW. yes, that makes sense, unfortunately I did not move any files, they are installed where they should be, default location. One thing I can think of is that they have this weird 4 level sub-directories, like it's an AAX plugin
EvoChannel.vst -> Contents -> Resources / x64
maybe Samplitude/ Sequoia can't cope with 4 levels of subdirectories.
could be something from the VstPlugins.ini like
DirectoryRecursionDepth=2
DirectoryDisplayDepth=1

I should try changing those and see.

The " resources " on my side are at this level :

C:\Program Files\Steinberg\VSTPlugins\Flux\EvoChannel.vst\Contents\Resources\Skin

C:\Program Files\Steinberg\VSTPlugins\Flux\EvoChannel.vst\Contents\Resources\GEngine

and 1 level more for the fonts :

C:\Program Files\Steinberg\VSTPlugins\Flux\EvoChannel.vst\Contents\Resources\GEngine\font

and even more with :

C:\Program Files\Steinberg\VSTPlugins\Flux\EvoChannel.vst\
Contents\Resources\GEngine\shaders\gpu\deferred

all working fine, as mentioned before.

the same for me except no "Steinberg" sub-folder. VSTPlugins is in the Program Files.
well, I give up - it's something to do with how Flux handles the whole GUI thing. And I've noticed everyone downvoted that page from the Flux site, the first link you posted; apparently it doesn't solve the issue for those who have it.
thanks anyway DAW for all the help.