PlanetZ forums - scopeusers.com

Hi guys,

I recently tried the XTC with cubase 5.1 but it doesn't seem to work. 1st I don't have problems in normal mode. I have 1 pulsar II + 1 Luna2. I activated XTC in scope, used the default XTC project, close scope run cubase. Cubase crashed when loading the CW plugins sometimes there's a reboot of the computer (something like Msvcr71.dll crash). I tried to keep only the XTC delay in the vst scope plugin subfolder for example and had the same result. Is there something to tweak in Scope or in config files or in cubase to have it working? Are there known issue with cubase I didn't found solutions on the forum.

I use win XP SP3 (32 bits) and scope 5.1 (I installed XTC at the setup)

Thanks for your help!

Theres a few tips and hacks here :

http://www.hitfoundry.com/issue_04/cub_xtc.htm

Hi Dante,

OK great thanks for the quick reply and the link I'll have a look and try this asap.

The thing is the crash appears during the scan of the XTC plugins, this doesn't make me very confident. Anyway I'll try to follow this step by step and keep you posted.

As I thought I got the same results --> crash during the scan of the SC plugins. I think this is not a pbm of one plugin in particular as I tried letting only XTC delay...

If anyone had the same experience, it would be great to share...

I won't use XTC for the moment.

Thanks

Did you follow the link to the docs here ? :


http://forums.planetz.com/viewtopic.php ... atch+guide which lead to:

http://forums.planetz.com/download/file.php?id=2173
http://forums.planetz.com/download/file.php?id=766

Sure I did.

Thanks for the link which is interesting. I'll review in details the doc if I missed something.

Last précision, the error is STOP:0x0000050
PAGE FAULT IN NON PAGE AREA

This looks like an incompatibility of the driver? Maybe someone know something about that?

Thanks

New one on me. If I got that, I'd be trying (as a last resort after trying re-installs etc) the same setup on another PC to eliminate whether its hardware or software.

i'd be checking for bad ram...

OK thanks.

Bad RAM would be surprising because this is the only thing that makes the system crashed.

if everything is correct with the system, it shouldn't crash. it can't be just your computer with bad drivers.
unfortunately there are a number of things that will cause a blue screen, and almost all of them are hardware related.

the power supply not providing the correct voltages under load, bad ram, a bad motherboard, an irq shared between the Scope card and a usb controller, are the usual suspects.

Ok thanks for your help Gary.

I'll try to look further (or not use XTC...)

interfearence wrote:OK thanks.

Bad RAM would be surprising because this is the only thing that makes the system crashed.

Yeah but it could also be unsurprising if swapping the ram chips around fixed it

I've seen that before.