

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… I think the VST can’t swap memory to disk or something. Normally it should swap memory to disk and if that’s an SSD it’s still ok to work that way. You hit the 4GB limit and seems the plugin can’t cope with that, hence the page swap errors I received. I’m pretty sure now as well that hangs and blue screens, especially when working in 32bit DAW are memory related.
Nascar stock car for sale 64 Bit#
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. Ok, just loaded the same project in Cubase 8 64 bit and no more crashes so far. At least that can eliminate memory limit issues. But since I have a cubase 64bit version installed as well, I will continue my tests on that as well.
Nascar stock car for sale Pc#
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Īnd not everybody is running his DAW in 64bit. 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. Could find a workaround for that, but nevertheless still system hangs… I even play high graphics games sometimes without ever having issues. After looking that one up also seemed a Graphic stress overflow on the open GL base. And another one causing my graphics card to reset. 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?). I have the impression the rytm plugin is more CPU heavy. However I started to notice a few things. 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. Same blue screen or system hang issues here as well on Analog Rytm.
