• SONAR
  • bitbridge problem since 2016.10(22.10.0.19) (p.2)
2016/11/07 15:13:46
bsheen
I've only rolled back to the last update and it did not.  I haven't gone back as far as may 2015.
 
It seems like its only with the MixIR2 vst within Sonar.  The other 32bit vst open up ok.  MixIR2 works as long as I don't try to open it.  This only happens in Sonar and within the Chainer vst.  Chainer in standalone mode works fine.  You open mixir with no problems.
 
Once you try to open mixir within chainer in a project it gives that teleport error, and basically locks up sonar as well.  When you close out the error, everything looks normal in Sonar until you go to click on something then it locks up.
 
2016/11/07 15:16:03
bsheen
Note: I've just installed the 64bit application of mixir2 and it opens up in the fx block fine.  Obviously I can not test it with Chainer, because chainer only allows 32bit apps to be loaded.
 
2016/11/07 15:16:53
bsheen
But again everything works as it should in standalone mode within windows.
 
2016/11/07 15:23:59
scook
The only other thing in the SONAR environment would be a VST reset. If that does not resolve the issue then jBridge may work. The best solution when married to 32bit plug-ins is run a 32bit host. Even then, the plug-ins still need to be supported and maintained or expect them to fail at some point in the future if everything is updated around them.
2016/11/07 16:05:12
bsheen
Appreciate all the help. I will give that a shot and see what happens.  Thanks again!
2016/11/16 20:08:00
gmp
I had this happen 2x today on the same project, then rebooting each time. I’m using 2016.10  I've never had this happen before  - ever. There is a setting under preferences/VST/Bitbridge.
 
Mine was set to 132 mg for server 1. That seems too low, so I changed it to automatic (uses as much RAM as needed). Does anyone else know anything about this setting? It seems like automatic is a better setting.
 
Yet when opening Sonar again I see that my setting has changed to 0 mg for server 1. This is strange, maybe it’s not really a setting, but simply a report as to how much RAM is currently being used
2016/11/16 20:13:21
bsheen
I have yet to figure out why its happening other than the 32bit MixIr2 plugin does not like the latest update of Sonar.  The 64bit version runs fine.  And so far...(knock on wood) all other 32bit vsts are running fine.
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account