RMV causes severe errors/problems in cubase 6.5 x64!

[Dr.Noise]

I recently switched to a 100% 64bit DAW and ever since then I've been getting constant RMV crashes in cubase 6.5 x64. I'm using the RMV 64.dll (x64 version with full 32 stereo outs). I tried reinstalling the v5.0.7, installing a different version, but the same thing happens. And it seems to be 2 different types of crashes:

1. Happens when opening the plugin GUI, giving an exception error:

And a black plugin GUI screen:

Plugin still works (no host crash and samples still playing), but is not editable and causes the exception error every time I try to open it.

2. Happens when switching samples using the previous/next keys or the built in browser. Starts to randomly freeze the whole program for seconds at a time, sometimes causing the RMV waveform display to show a blank waveform, sometimes freezing the whole RMV GUI. Reopening the interface (not reloading the plugin) clears the plugin GUI freeze for a few seconds, but as soon as I try switching the samples again, the problem re-appears.

Both problems happen only about once every 10 mins, and the rest of the time the plugin loads and works fine. I used RMV in a cubase project template which loads fine most of the time. However, when it happens, every 10 mins of working on average, I'm forced to restart cubase, as reloading the plugin is not only a huge hassle (re-linking and re-applying all the channels/effects/routing), but actually causes a critical error which usually either crashes cubase or refuses to load the plugin until restart of cubase.

I should note I'm an expert PC user with ZERO other problems with the PC, software/hardware, cubase, drivers, malware, etc. No problems with any other x64 plugins in cubase, and no problems using the x86 version of RMV in cubase 6.5 x86. Hence I'm pretty sure this is an RMV problem.

PC: Win7 x64 SP1, i7@3.5GHz, 6GB DDR3 1600, Intel SSD 120GB, GTX 560 Ti 1GB DDR5, all the latest patches and drivers.


Is this a known bug? Is there a fix/workaround?
Any help is appreciated.

[LfmC]

I've got the same problem; random freezing of RMV when changing sounds. Any fix for this?

[Peter from LinPlug]

Thanks for the report guys, I've not yet being able to reproduce this. Its not yet being a known issue; what we had is that some people who upgraded their 32 bit system (in opposite to completely setting up from grund) had some issues because the way windows tried to move data (the registry in praticular) was not always successful. However, this not really looks like such an issue, I will try on other systems to see if I canmake such thing happen somewhere to help you guys. I get back once I know more.

[Peter from LinPlug]

I wish I could say more, but after almost 20 minutes and walking through about 1000 sample loads there was not slightes glitch with RMV 5.0.7 64 bit on a dual core Win 7 machine; I did some tests (not as long) on other machines and it seemed ok too. So I'm having no idea.
Were you loading from RMV library or other samples ? Where were these samples located, internal drive or maybe USB or network drive ? Any info you could give might help us. Does RMV play back the samples while you switched them ?

Thanks for your assistance

[Dr.Noise]

Thanks for the reply, Peter.

I'm still fighting with this bug, so here are some more details:

DAW: Cubase 6.5 x64
I use a cubase template containing RMV 32-0 64. The samples are my own, mostly from commercial sample CD's (wav) which are located on another physical internal drive (F: in my case) and are added through the RMV "ADD" option in the setup tab (with a custom short name), enabling them to show in the built in browser and loaded from there (I rarely use the small "L" on the drum pad to load the samples using search). The loaded RMV in my cubase template I use is preloaded with my samples and routing for each pad.
I switch samples almost always during playback, use all 32 stereo outputs of RMV and use a lot of routing... not sure what else to tell you? I use single shot samples, only 1 sample per pad (and use the waveform view in the pad settings), midi channel pads is set to 10, I don't use loops, pad setup is off..

I've now tried rebuilding the cubase template from scratch, reinstalling cubase (and re-setting the prefs for it) and reinstalled RMV 3 times, and last time even went through the registry manually and cleaned up everything that has anything to do with RMV, and the problem seemed to go away for a day, but the very next day, it was back.

What seems to cause most problems is opening the GUI and, at times, switching samples. But lately I've been having almost no problems with sample switching, but the exception error and the black RMV GUI screen seem to happen all the time now (although trying to open it a few times in a row, each time gives a popup of the exception error, but sometimes it opens fine - maybe once in 10 tries)
Actually, I think I might have found the cause of glitches while switching samples: Using RMV sends 1-2 with no internal effects, and instead using them to send the signal to outs 31-32 where I would use VST send effects; kind of like an extra 2 sends per pad, but with VST effects. Since I stopped using this setup, the freezing while switching samples seems to have went away, although I can't be sure, as I can't user RMV for more than 30 mins without having the exception error issue.

Hope some of this can help you.

[Peter from LinPlug]

Thank you Dr.Noise, for this detailed info, I couldn't ask for more. Unfortunately I still cannot make it happen, while I was very close to your way of working already, and on a very similar spec'ed machine, I today tried with routing to last output to see if it makes any difference, but not here.
Then I played with open/close GUI for more than 100 open/close cycles without any issue, both tests on running sequencer firing Note events to RMV so audio was running while switching samples and GUI but it all went smoothly here.
All you say sounds pretty as I would expect it and leaves few to no room for doubts or anything I would argue about.

LfmC, what is your system specification ,maybe we can find anything in common. Also, how exactly do you work to produce an error.

I must admit I'm a bit lost, in any case if everyone reading has something to add, please do.