PlanetZ forums - scopeusers.com

Has anyone here got Wavelab 7 (or even v.6) to work with the latest Scope Asio drivers (Version 5.1.2709)?

/Dave

No,
I am using a '24Bit Wave Source' for Wavelab 7 into Scope 5.1.27091 x64 on a Win 7 64Bit machine'

ho this is a good news in waiting for the asio issue will be corrected !
i didn't try it with waves driver (no asio in your project I suppose ?)

I have had ASIO modules in the project at various times, but not assigned in WaveLab preferences as the playback destination.

but for me wavelab (element) 7 don't startup with asio because wavelab have to scan the asio drivers I think.
It's not so possible to assign another drivers cause the startup doesn't work ...

Same with me. Steinberg support suggests I remove scope drivers, enable onboard audio in BIOS, start up Wavelab to use on board driver, then reactivate Scope hardware (and de-activate on board audio).
Seems like a lot of hoop-jumping so I haven't bothered.
PG at Wavelab knows about the issue but I guess he doesn't consider it worth his time. I've asked several times on their forum, without a response.

/dave

Hi Guys,
This issue was discussed sometime back.
Checkout here:
http://forums.planetz.com/viewtopic.php ... it=wavelab
I had to blow away SCOPE and load WaveLab 7 and then reinstall.
I think some others work out a better way.
Anyway once I had Wavelabe installed I have dont go back to ASIO input to Scope as it hangs W7.
I hope this helps.

i found an easy way to get wavelab7 running with scope installled:

just delete/rename the file "baios.dll" in the folder "Wavelab7/System"

monoman wrote:i found an easy way to get wavelab7 running with scope installled:

just delete/rename the file "baios.dll" in the folder "Wavelab7/System"

Can you rename it back again after install?

no, you can't rename "baios.dll" back again as soon as you open wavelabs audio preferences it will crash.

here's a second workaround:


leave "baios.dll" untouched (original)
delete/rename "AsioScope.dll" in the path "SCOPE PCI/App/Bin"

after running wavelab you can rename this file back to original and edit the audio preferences in wavelab with out crashing wavelab.

monoman wrote: delete/rename "AsioScope.dll" in the path "SCOPE PCI/App/Bin"

Thanks it does work for me !

babaorum wrote:

monoman wrote: delete/rename "AsioScope.dll" in the path "SCOPE PCI/App/Bin"

Thanks it does work for me !

No problem, you are welcome! I should apply for Steinberg's quality assurance

Wavelab 7.1 update was released today. But shame on Steinberg for not fixing the Scope asio issue!!!

Yes and your solution doesn't work completely ...
not able to recording with the waves ... is this the fault from VST ? VST are working just with ASIO ?
I have only noises and crackles when I record ...
But the files bounce seems to be work but I'm not still so sure ...

monoman wrote:Wavelab 7.1 update was released today. But shame on Steinberg for not fixing the Scope asio issue!!!

Normally it's for 7.2 planned

new for wavelab 7 and asio ?

There is a trics wich could permit to use wavelab with the waves drivers of scope but not to record in wavelab, you can only treat a file and export it.
We must waiting for a patch from wavelab to correct the ASIO compatibility.

Hello, today I spoke with assistance steinberg, relative to the bug wavelab.
responded that the card is old and does not solve the problem.
is necessary to make a request en masse .... so they are convinced that it is so outdated and he is now used by many.
send email to Steinberg and complain. thanks

here link <info@steinberg.de>

https://www.steinberg.net/forum/viewtopic.php?p=84244


above is the link from Steinberg

The aspect that solve the problem thanks