After having the latest 9.5 update for weeks now I am scratching my head on whether the 64 bit processing option is worth the CPU hit. Wondering if I am really hearing anything above what my dog fido can hear.
not huge here but about 7-10%. Guess i am just lucky.
Seems strange one would get REDUCED given 32 to 64 bit - perhaps it likes being ānativeā 64 bit on a 64 bit OS? THEN, why am I seeing a little āhitā??
I did this and only Steinberg Plugs showedā¦interesting.
I really need to rethink the whole 64bit instance.
Wondering if itās worth the headache for the minimal gainā¦would love to have a fully 64bit supported DAW, I meanā¦itās 2018 and weāre still tinkering with settings⦠Gotta now check all my plugins.
Does that means also that if i would use vst 2.5 vst plugins in 64 engine cpu wont go up when i used it in 32 bit engine as previous settings. Iam noob to cubase. I juzt got 9.5 version. Lots to learn
Cheers
Depends I would say, the vst3 plugins that do 64Bit float calculations internally (that is an option the manufacturer has to make)
Donāt have to convert 32bit float to 64Bit float and back again, that saves cpu cycles.
Waves vst3 plugins do this convention regardless, even if you are sending them 64Bit float and they internally calculate in 64Bit float.
It is worth to mention that the external FX ping, is broken when in 64Bit mode.i guess we could use the 32 bit mode to ping the external FX, write the values down, use the 64 bit mode and insert the ping values by hand.
What if I use a mix of Cubase plugins + VST2 plugins? Would be still worth going 64 bit?
Also, I have a bunch of Waves plugins (CLA-76, CLA-2A, REDD, ADT, TG12345). If those plugins are Vst3, why they are not listed as plugins that support 64 bit processing?