Quote:
Originally Posted by
TNM
➡️
I have disabled turbo on my 2.8ghz macbook pro, so your 2.5 was probably running at a higher clock speed as mine doesn't go above 2.8 (for heat reasons i prefer it, and noise reasons).
so your Logic results correlate perfectly with my pro tools results, although my test was over 128 tracks with a different audio file playing on each therefore a lot more stressful to begin with before adding any plugins.
I can't understand how you think 70 instances is frugal. For it's intended use it isn't, IMHO. This is a track insert plugin.. yes,if a reverb had 70 instances, that would be frugal. But of course no one needs 70 reverbs, ever.
What happens when you want to start playing kontakt or sculpture on one of those tracks? or 16 Vi's, maybe 32 which is totally normal? Effects on each of those Vi tracks?
and other effects on those audio tracks?
Anyway:
As thought, i did my fab filter test:
64 stereo audio tracks. (128 playing).
1 ProQ2 with 7 bands on, 1 ProC2, 1 Saturn and 1 pro Ds per channel.
44K as yourself.
128 buffer as yourself (like logic, PT uses 1024 internal buffer which is why, as with yourself, it made no difference).
Total cpu usage for these 256 (64x4) fab filter plugins = 40% max on pro tools meter, 298% on real cpu meter.
So, ~30% lighter than just one waves omni on each of 64 audio channels.
(128 tracks are actually playing in the project at all times btw, for extra room for higher test counts).
BUT.... the fab filter project reloads in 10 seconds vs a minute - the waves project takes longer to save here on exit than the fab filter takes to load.
basically i concur your cpu usage tests 100% but i disagree that said results = efficient.
At least, they have vastly improved things since butch vig vocal channel, which uses 4x the omni channel with all processes enabled.
That's the most ridiculous cpu usage for any channel strip plugin, or any single plugin period that I have ever seen, for a basic streamlined Eq, comp, saturation and single de esser.
Omni is a revelation in comparison and makes the Vig plugin totally redundant.
Your test results are very interesting. I have FF pro bundle and was wondering if I could gain anything additional from the Omni Channel versus just using separate D esser, Comp, Eq, Saturation whatever I want in any order on my channel strip....but then I was thinking "ok, maybe the advantage of having everything in one Plug-in is less CPU usage vs all the different individual plugins..." Guess not!
and to my old macbook pro (maxed out, top of the line 2013 model), FF plugins are already seeming to be CPU hogs that make me want to keep reaching for Logic Stock plugins .
so if not CPU savings I think the only think I might gain from Omni Channel is a different way of mixing as FF plugins are SUPER visual, and channel strips are minimally visual and SUPER "use your ears, buddy" oriented
