sadly I reverted back to oldschool here...
32bit nuendo and vst2 plugins. this simply just works...
the 64bit nuendo seems to handle plugins slower, the same plugins work way faster in 32bit, I dont know why this is.
also I had a major issue with some old 32bit plugins crashing my 64bit nuendo bigtime. I tried the j-bridge, as I seen many posts in this forum about that working better. it did work better, but still I had massive lags and some minor issues with j-bridge, so...
yeah, back to what works...
thanks for posting tho
At the risk of soundding like a broken down gramophone, the biggest cause of trouble in the 64-bit world is using 32-bit plugins via the cobble that is the BitBridge, be it the stockie or J-Bridge.
The best way to minimize the pain is to set up your 3rd party (ie Shared) plugin folders in such a way that your host will never scan both 32 & 64 bit versions - the way I have set it up is like this:
C:\Program Files\64 - contains all 3rd party 64-bit plugins.
C:\Program Files\32 - contains 32-bit only plugins
C:\Program Files\32_Shared - contains 32-bit plugs that also have a 64-bit version installed.
64-bit hosts scan the 64 & 32 Shared folders, never the 32 one.
32-bit hosts scan both 32-bit folders
Result = stable system, no crashes, no trouble.
Plugs used? Antares (all), Slate (all), UAD (all), Lexicon PCM, Waves Mercury, etc etc etc - never a single crash caused by a plugin to date (crosses fingers & scratches head due to no other wood available)
Intel E5-2687W 8-core Xeon, 32Gb RAM, Windows 7 Pro x64, RME RayDAT, UAD-2 Octo x2 & Quad x2 (fully loaded), Adam A7 x5, WK ID Console
Nuendo 1-6, Cubase 6-7, WaveLab 5-7, DTS/DD encoders, Surround Edition etc, Waves Mercury
Blu-Ray authoring, DVD authoring & high resolution audio specialists.
Detailed Specs on request