Welcome Guest! To enable all features please Login or Register.



Forum Jump  
Last post Sat, May 15 2010 by Dietz, 2 replies.
Go to last post
Posted on Sat, May 15 2010 17:05
by KompoB
Joined on Wed, Dec 07 2005, Berlin, Posts 11

Hey guys,

I'm working on Cubase 5 (Win 7 x64) and VEP.

I was stupid enough to install SD2/PLAY and add it to my massive Cubase/VEP default session. Did so jbridging the x64 PLAY file. Everything seemed to work fine - at first. I was even more stupid to then install the PLAY update which got out last week. - Since then, it's a big fat mess.

The session consists of about 300 patches, distributed in 2 VEP instances. The first instance always loads fine, the second one (which contains the PLAY patches), gets me a bluescreen saying either

"a clock interrupt was not received on a secondary processor within the allocated time interval" (if VEP is launched AFTER I've opened my Cubase project) or

"IRQL_NOT_LESS_OR_EQUAL" (if VEP is launched first and then Cubase/the Cubase project are being opened).

I've tried really EVERYTHING. De-installing PLAY, de-installing PLAY and re-installing the old PLAY, system recovery and no PLAY, system recovery and re-installing the old PLAY... nothing works - I always get that #$%*(! bluescreen ... argh.

If anything, please has anyone at least an idea how to OPEN the files without PLAY, so that at least I can use the reeeest of my session? argh



Posted on Sat, May 15 2010 23:40
by Dietz
Joined on Tue, Aug 06 2002, Vienna / Europe, Posts 7417

The easiest way to deal with a misbehaving plug-in in Cubase is still to move its DLL out of the folder where it resides. Cubase will then open the project with a message saying that the respective plug-in is missing, leaving everything else intact.


/Dietz - Vienna Symphonic Library
You cannot post new threads in this forum.
You cannot reply to threads in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.