scope v5 to scope v5.1 , wavelab 6 , asio scope pci error

[microraver]

I updraded from scope v5 to scope v5.1 (Win7 32bit), before i used wavelab 6 with asio scope pci drv without problems !
Now i got a error ,see attachment !

Already deinstalled scope and wavelab 6 , first reinstalled wavelab and using generic asio drv ,then reinstalled the scope 5.1 and vice versa , same problem !
I can use the MME driver for scope but there is a hughe latency ! was mutch better wit the asio scope pci drv !

anyone with a solution ?
payed 98€ for nothing , keyfile from v5 is also working the only difference i have in keyfile v5.1 is 'SC SCOPE v5.1 Application' and just have Arpeg02 as extra plugin !

wavelab6 error.JPG (18.51 KiB) Viewed 11171 times

[Fluxpod]

Why did you buy it?Only difference is the 64 bit driver (and the arpeg 2?).Hopefully you get the next update with bugfixes(which need to happen) for free.

The error is strange.Did you try different asio modules?Maybe 2 ch only will help.

[microraver]

Hi,

Yes i tryed different asio modules , I also have Win7_64bit that i use for xperiments but have the same problem !
Now i gonna put my C; drive backup with scope 5 and just upgrade from there without deinstall and see what happens !

Why did you buy it?Only difference is the 64 bit driver (and the arpeg 2?).Hopefully you get the next update with bugfixes(which need to happen) for free.

The error is strange.Did you try different asio modules?Maybe 2 ch only will help.

[microraver]

Ok,

I have my backup back with scope v5 and just upgraded to v 5.1 and wavelab is working again !! ( 64bit not )

So when i first deinstall v5 and then install v5.1 , asio scope driver is not working for wavelab !@#|&!!!

[babaorum]

I don't have this message but wavelab element 7 freeze at startup !
when I was on scope v5 wavelab worked fine and now with scope v5.1 wavelab element doesn't work ...
garggggllllll

I told this issue to the wavelab forum on steinberg.net and PG respond to me that there is maybe a pb with the register in this key :
HKEY_LOCAL_MACHINE\SOFTWARE\ASIO

Could someone tells us what he has in this register key ?
In scope v5.1 I have this one :


thanks

baba

[microraver]

Hi,

Can't help you i have the same key in register but i'm on wavelab 6 !

asio scop pci.JPG (23.79 KiB) Viewed 10467 times

Look there http://forums.planetz.com/viewtopic.php?f=1&t=29729 i think this is the solution !

grtzzz...

I don't have this message but wavelab element 7 freeze at startup !
when I was on scope v5 wavelab worked fine and now with scope v5.1 wavelab element doesn't work ...
garggggllllll

I told this issue to the wavelab forum on steinberg.net and PG respond to me that there is maybe a pb with the register in this key :
HKEY_LOCAL_MACHINE\SOFTWARE\ASIO

Could someone tells us what he has in this register key ?
In scope v5.1 I have this one :


thanks

baba

[babaorum]

no with wavelab element 7 that doesn't work. Do you have tested with 6 ?

[krass]

I have the exact same issue as babaorum has, but with Wavelab 7.
Also on Win 7 64bit, with the Scope 5.1 64bit drivers.

Over the Xmas period I've communicated a lot with Steinberg on this, worked through all their
suggestions with no luck. Then hit the Steinberg support forum and saw babaorum's message
posted there, and thought it might be good to pay a visit here too

After reading both forumes, I decided to uninstall the Scope 5.1 software, Wavelab 7 runs fine then! Also, Wavelab 6 runs perfectly fine with Scope 5.1 64bit!

Anyway, as Cubase and other apps on my PC are working absolutely fine with Scope 5.1 64bit, I suppose this is still a Steinberg issue, and will keep on working it with them.
In the meantime however, I will also log a ticket with SonicCore to see what they know/can do.

I'll keep you up to date.

Regards,

KrasS

[babaorum]

if wavelab 6 works with v5.1 64 !!! it's a good news cause I think so it's not a big pb and maybe Philippe Gautier could correct quickly this issue !

Change the .dll name from scope64 to scope is not the solution because after that cubase 64 can't run the audio engine ...

I prefer keep cubase alive in waiting for wavelab will ...

Thanks for the confirmation of the informations.

baba

[krass]

Baba,

No probs!
By the way, did you see this post? Apparently there is a way to 'kind of' solve this... that is if
you don't need to use ASIO drivers in Wavelab...
(It works for me when I uninstall Scope, select MME win drivers, and then reinstall Scope.
It does not work when I uninstall Scope, select my SSL Soundscape ASIO drivers, and then
reinstall Scope!)

http://forums.planetz.com/viewtopic.php?f=1&t=29623

I agree with you that renaming the DLL, or pointing to the AsioScope.dll doesn't make sense,
as we're on 64 bit...

Regards,

characterstudios

[krass]

So... I have it working for my situation...

As per my previous post I did the following:
* Uninstalled Scope 5.1
* Started Wavelab 7, and configured it to use my SSL Soundscape ASIO drivers
* Installed Scope 5.1, rebooted
When starting Wavelab 7, it froze again!

I also did the following:
* Uninstalled Scope 5.1
* Started Wavelab 7, and configured it to use Windows MME drivers
* Installed Scope 5.1, rebooted
When starting Wavelab 7, it worked fine.

Now, as I have no need for the Scope ASIO drivers (my Pulsar is connected to my
SSL AlphaLink through ADAT), I decided to try and remove all references to the
Scope ASIO driver from my registry.
That included keys in the following locations:
* HKEY_LOCAL_MACHINE\SOFTWARE\ASIO\ASIO SCOPE PCI
* HKEY_CLASSES_ROOT\CLSID\{DD320B40-17F0-11D2-9CAD-006097A97422}
* HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{DD320B40-17F0-11D2-9CAD-006097A97422}

The result of this is that Wavelab 7 now starts fine, and initializes using the
Soundscape SSL drivers.

So, while I'm aware that not many people will use their Scope/Pulsar card in
the same way I do, it clearly points to the fact that Wavelab has an issue initializing
ASIO if there is any trace present of the Scope 5.1 drivers...

I hope this is useful for someone else, and I've communicated these findings to
both Steinberg and SonicCore too.

Kind regards,

KrasS

[Cochise]

...I decided to try and remove all references to the
Scope ASIO driver from my registry.
That included keys in the following locations:
* HKEY_LOCAL_MACHINE\SOFTWARE\ASIO\ASIO SCOPE PCI
* HKEY_CLASSES_ROOT\CLSID\{DD320B40-17F0-11D2-9CAD-006097A97422}
* HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{DD320B40-17F0-11D2-9CAD-006097A97422}

My issue with Reaper was solved swapping the 32 bit AsioScope dll with the 64 one, in the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{DD320B40-17F0-11D2-9CAD-006097A97422}\InprocServer32

Don't know if this can be useful in this thread, but... since such a key isn't mentioned.... for sake of completeness...

[babaorum]

It's really scope ASIO drivers cause I tried to uninstall scope v5.1 and install ASIOforALL drivers and wavelab element 7 started fine. When I reinstalled the scope ASIO wavelab froze !

[Throttler]

same for me. no asio for wavelab

[katano]

no ASIO for wavelab here, too...

[Throttler]

"Wavelab 7 has a problem, when Scope is installed, it is not able to initialize
our ASIO driver, although all other applications can. Steinberg is informed."

answer is from S|C Support Team

[maggiau]

What I did without uninstalling everything.

Exit Scope
Desactivate the Xite driver in the control panel (hardware)
rename the programs Xite directory to anything
start wavelab
Select the MME asio in wavelab
exit wavelab
reactivate the driver in the control panel
rename the xite directory to its old name
start scope and wavelab ok !!

[Creative-Sound]

Guys,

Still having same problems, even with the latest version Wavelab 7.2 64 bit. Running Scope 5.1 (2x Pulsar PCI) and A16 Ultra as main sound configuration.

Cheers.

Solved Many thanks.

[babaorum]

Maybe you have unstall and re-install wavelab or scope and you must doing again this tips.