Cubase 4.1 Upgrade issue

[mausmuso]

Hi Guys,
I have upgrade dCubase to the new 4.1 but it wont run when Scope is running.
If Scope ASIO is not available it will load, although afterwards when I try to change ASIO to SCOPE in Cubase I do not get any real joy.

I get this message when I start Cubase with Scope live:
[The instruction at "0x03aa1ef3" referenced memory at "0x00000004". The memory could not be "read"]

Any advice would be appreciated
Regards,
mausmuso

[arela]

I've seen this on the cubase or nuendo forum, and i think there was a tricky way around this problem, and that is pretty much why i have not used my 4.1 exe file yet
There is a trick somewhere, as i recall, something with changing samplerate, restart and so on - though it seems to work with 44.1kHz only.

From the sideline: good luck

[mausmuso]

Thanks for the tip Arela,
I'll go trawling.
maumuso

[mausmuso]

For those of you who want more info on this issue, have a look in the Cubase Net Forum:
http://forum.cubase.net/phpbb2/viewtopic.php?t=82878
mausmuso

[arela]

thanks for the link, will need it sooner or later

[mausmuso]

Hi there a quick update to let you know how I got 4.1 working.

As reported by a number of people on cubase.net it works if on Cubase load, SCOPE is set at a sample rate of 44.1kHz.
Once Cubase is open you can then switch to 48KHz if you wish.
If you have a project open when you switch samplerates Cubase will ask whether you want to keep sample position (or something like that). I think the right answer is 'No'! otherwise it will move your audio about and you may lose track timing.
You can of course save your SCOPE projects (and your Cubase projects for that matter) in 48K when you're done, but remember next time you open to change the sample rate before opening Cubase.
I do not use 96KHz so I dont know what happens with that samplerate.
Its annoying but workable
regards
mausmuso

[krizrox]

There were complaints about something related to this over on the Cakewalk Sonar forum not too long ago. Seems like every time Steinberg releases an update these days, they manage to lose a few more customers. The unhappy campers all seem to migrate over to Sonar with their tales of woe.

The issue wasn't Scope related though - I have a feeling whatever it is is affecting other product users as well.


Hope you get whatever it is resolved.

[krizrox]

Yes Steinberg seems always to need 3 bug releases. But would that justify to move to Sonar ?

Apparently - I've lost count how many ex-Steinbergers have checked in over there singing Cakewalk's praises over the past year or so. Judging from this particular thread, I can see why.