If I use either the A4 or Rytm Overbridge VST, it works normally now except for one persistent problem - each time I close my set or if I try to delete the plugin or track with the plugin, I get a “Live unexpectedly quit…” warning message.
I have started a ticket but is anyone else dealing with this?
This is on the Ableton Live 32-bit version running on Windows 7 64-bit version.
I have the same problem on Windows 8 and Ableton Live 32bit!
Same problem here with w7 64b and ableton 32b
Im hoping there will be a golden tip to fix this otherwise i just bought overhub for nothing
I get a blue screen when i try to load the analog rytm plugin
Why don’t you just switch to 64 bit Ableton? And jbridge any 32 bit only plugins that you have.
For me it has to do with backwards compatibility of my projects. Most of my plugins are 32 bit, i havent been convinced they will all run with Jbridge. Or can you confirm that it runs flawlessly with all plugins?
Just back up your Ableton folder and try it.
Same blue screen or system hang issues here as well on Analog Rytm. A4 seems to work better. Win7 64bit, Cubase 8 32 bit. Same reason here I stay with DAW 32 bit, some of my old 32bit plugins simply don’t work that well in 64bit, even with Jbridge.
However I started to notice a few things. I have the impression the rytm plugin is more CPU heavy. If I run a project with let’s say 8 VSTi’s and I open the rytm plugin I get 100% CPU load on all 4 core (I7 -2600), also got a blue screen related to page faults (memory spike?). And another one causing my graphics card to reset. After looking that one up also seemed a Graphic stress overflow on the open GL base. I even play high graphics games sometimes without ever having issues. Also only with the rytm plugin. Could find a workaround for that, but nevertheless still system hangs…
I never had performnace issues with all other plugins, hardly stress my machine, but especially the rytm plugin (16 bit, only stereo ch enabled) is still buggy in my opinion on CPU and memory load. If you run it in a simple project with only a couple of VSTi’s I can just get away with it and I don’t think my pc specs are that low : 16GB * SSD* Core I7*GTX760
And not everybody is running his DAW in 64bit. But since I have a cubase 64bit version installed as well, I will continue my tests on that as well. At least that can eliminate memory limit issues.
Grtz,
Ok, just loaded the same project in Cubase 8 64 bit and no more crashes so far. Crashed immediately in Cubase 32, so I guess no other choice right now than for a bit more heavy projects, work in a 64 bit DAW. I’m pretty sure now as well that hangs and blue screens, especially when working in 32bit DAW are memory related. You hit the 4GB limit and seems the plugin can’t cope with that, hence the page swap errors I received. Normally it should swap memory to disk and if that’s an SSD it’s still ok to work that way. I think the VST can’t swap memory to disk or something. Maybe an interesting test could be with a new project, first open Elektron plugins and only after that other VSTi’s, maybe than the Elektron can allocate real memory since it’s residing in the first ram pages, just a thought…
So for me buggy on memory load part in DAW 32 bit. I try to report it to Elektron, I’m pretty sure there are other people still working in 32 bit as well.
CPU seems also better in 64 bit, hard to say if that’s related to Elektron plugins.
Cheers,
thanks for the extra info, i really hope Elektron will be able to fix this