Just FYI to those who are dealing with bridging x86 (32-bit) plugins with 圆4 hosts, I wanted to mention the four "bridges" I know of that are currently out there and some quick comments.ġ) Sonar BitBridge 2.0 - the best x86 bridge out there, in my opinion. So cheapest solution to this problem, probably buy a new set of piano samples, stick with cubase 5 - as last poster said, it is usually pretty stable.BitBridge 2.0 + JBridge + VST Bridge + Reaper 圆4/x86 bridge = encouraging for 圆4! btw, am definitely not out of RAM when Ivory crashes, I can load anything else no problem. So the only connection with my new RAM is that I'm now able to load up much more stuff at once - and in this situation Ivory crashes. Makes no sense, Synthogy never heard of this, but that's what's happening. No idea why this would be, but seems Ivory runs fine if not too much else loaded up, but crashes cubase if there's past a certain number of plugins open, or maybe certain size of samples, or combination of both. However, I can load it no problem into an empty or less busy project - BUT, if I then go on to load many more VTS's/samples, the project, once closed, won't re-open (crashes during loading). I then noticed that if I loaded Ivory into a busy project it would crash immediately. Well have stayed with 5.5 for now - I noticed that some large projects were crashing, some were fine - the only common factor I could see was that the crashing ones contained Ivory VST (64 bit plugin).
CUBASE 7 VST BRIDGE 64 BIT
Thanks for replies - really useful to know about that RAM test program, it was actually dead simple to run (burnt the ISO to boot cd in the end) though it took hours to complete! It didn't find any errors no errors, so this wasn't the problem, but it's good to be sure.Īs for the 32 bit bridge thing, that may be relevant here too - the plugin that seems to be causing the crashes is Ivory, and though this is a 64 bit plugin, it's one that was released as an update by Synthogy to make it compatible with 64 bit daws - maybe it is then akin to a bridge rather thana purpose designed 64bit VST? Speculating wildly here of course, should probably e-mail Synthogy to check if they know anything.Īnyway am now even more convinced it's a software problem, nothing to do with my system - CPU adequate, RAM adequate - hence back to my question of should I upgrade to cubase 7 for stability reasons? To put it annother way, is the actual coding, the dealing with VSTs, with 64bit systems, with large ammounts of midi-data & complex scripts - is that something that's been improved since vs 5.5?
CUBASE 7 VST BRIDGE TRIAL
There is a Trial Version on their website.
CUBASE 7 VST BRIDGE PRO
What finally helped for me was using Vienna Ensemble Pro and let most of my 3rd party Vstis run there. So for me it occure that perhaps only one ? 32bit Plug in may limit the overall amount of possible plug ins to 63. Reinstall the plug ins didnt`t helped too. I tried to rebuild my template (The original template was build on my older 32bit msystem) but that didn´t helped. The same happend by any other FX Plug ins or vsti
(Instruments and FX Plug ins) I could for example recall the issue by insert a reverb plug in like Roomworks SE. i had 63 plug ins in it and the 64 the crashes. So i count all my ussed plug ins in my projekt and. There is a known issue that when you have more than 63 or 64 (not quite sure about the exact amount) 32 bit plug ins than the system will crash. The Cubase vst bridge is used for 32bit plug ins on a 64bit system. In my case it seemed to be an issue with the vst bridge. I did a lot of research an tried almost everything but nothing helped at first. I had the same issue on a nearly similliar system a few weeks ago.
0 kommentar(er)
