!!!!!!!!! WAVELAB 7 & SCOPE ISSUE RESOLVED !!!!!!!!

[babaorum]

A great news for the wavelab and wavelab element 7 users with scope, there is a corrective patch (regedit file) sent by the creator of wavelab himself !
You can with this simple .reg record and all in ASIO mode :

https://dl.dropbox.com/u/3150024/AsioSc ... d_XITE.zip << for PCI boards and XITE

good work with wavelab and :

thanks to PG !!! and thanks to sonic core to have sent a DSP card to Steinberg staff !!!

that works great under windows 7 64 (wavelab element 7 32/64)

baba

[dante]

This is some very cool news !

[wouterz]

I'm not a WaveLab 7 user yet (I'm still on v6 on XP) but that's good to know

[Musicmarp]

Hi,

i did use this patch and wavelab7 works. I can use the asioscopedrivers in and out but now, i can't start Cubase 5.5 anymore.
Does this happen with other members?

grtz

Marc

[babaorum]

All works fine here.
You must be sure you have checked that in cubase to use the two softwares simultaneously :


regards

[Musicmarp]

Hi,

if cubase don't start i cannot change this settings. There is no way to start cubase. I've mailed this issue to Steinberg support.
Where can i find the original source of the zipfile/patch?

grtz

Marc

[babaorum]

You can on the steinberg support forum for 'wavelab and wavelab element 7' (you must have an account)

But the zip is a copy of the original and this is the one I used and no problem with cubase here (cubase 5.5.3 64bits, wavelab element 7 64bits, windows 7 SP1 home premium 64bits)

To comeback one step before you could remove the field from the windows register (with regedit command) and see if cubase starts again.

You must remove these values (which are inside the .reg) :

[edit]
[HKEY_CLASSES_ROOT\CLSID\{DD320B40-17F0-11d2-9CAD-006097A97422}\InprocServer32]
"ThreadingModel"="Apartment"

[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{DD320B40-17F0-11d2-9CAD-006097A97422}\InprocServer32]
"ThreadingModel"="Apartment"

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\CLSID\{DD320B40-17F0-11d2-9CAD-006097A97422}\InprocServer32]
"ThreadingModel"="Apartment"
[/edit]

[Musicmarp]

Thank you for the advice,

but after removing this values cubase evolves a litle bit further in the startup than before. When arriving at loading VSTmultitrack, the mesage apears that cubase do not work anymore ( appcrash).

Maybe more values have to be removed?

Grtz

Marc

[babaorum]

ho yes !


[HKEY_CLASSES_ROOT\CLSID\{DD320B40-17F0-11d2-9CAD-006097A97422}\InprocServer32]
"ThreadingModel"="Apartment"

[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{DD320B40-17F0-11d2-9CAD-006097A97422}\InprocServer32]
"ThreadingModel"="Apartment"

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\CLSID\{DD320B40-17F0-11d2-9CAD-006097A97422}\InprocServer32]
"ThreadingModel"="Apartment"


sorry.

[Musicmarp]

You mailed me exact the same 3 values to remove as those you did give me before. I did remove those already.

Marc

[garyb]

try rerunning the Cubase installer. hopefully that wil fix whatever is buggered up.

[mausmuso]

Unfortunately the patch did nothing for me (or appeared to do mothing).
I am running Wavelab 7.2.1 on a Win 7 64 Bit machine (Scope XITE 5.1).
It loads ok but when I click on Options/Audio Streaming Settings it hangs.
It works OK as is with the 24Bit Wave Source playback, but I cannot select anything else.
Any advice would be appreciated.
Maus

[garyb]

that patch was done by Steinberg. they might know best.

[Musicmarp]

I've did have contact with the steinberg support and my problem of being unable to start cubase is solved. The issue about wavelab is not. This is what they mailed me about it:

The issue is directly related to the ASIO driver.
The ASIO driver is created by the manufacturer of the audio device.
Any related issue to the ASIO driver have to be fixed by its manufacturer.

He also told me that the asioscope.dll does have problems with a lot of other software.
I hope this problems will get fixed in the scope6update. This problem makes me wait to invest in an Xite.

grtz

Marc

[babaorum]

I'm not sure that you apply in right order.

If you can use cubase again ok, it's right.

If you can't use wavelab without the waves drivers, it's because you have removed the .reg from the register of windows ? Am I right ?
So if yes, you must apply the .reg patch to use wavelab with ASIO drivers. Be sure you are in 7.2.1 version for wavelab I think.

I remember to you that I'm on windows 7 64 , with cubase 5.5.3 64, with wavelab element 7.2.1 and all is right now, all works fine, the issue is corrected for me. And I can start wavelab even if cubase is opened in preferences : if the check 'let's free the ASIO driver if cubase runs in background' (or something like that for me cubase french version).

So other people have the same conclusion, there isn't issue normally now.

last stuff I'm not with XITE I have Luna II + Pulsar II PCI boards with scope v5.1, maybe there is another issue with the XITE version, so you have to contact Sonic Core (tell them that in PCI version of scope that's ok now)

[babaorum]

Ok that's it !
XITE has another driver. Philippe from wavelab has changed the correction for the XITE driver :

Re: ASIO SCOPE solution

Unread postby PG » 06 Jul 2012 13:18
Indeed, the Scope XITE 5.1 uses another sonic-core driver.
I have updated the REG/ZIP file. Download and execute again...

Philippe

Maybe you are ok now , tell us !!!


I updated the link in the first post to download the patch for PCI and for XITE

have fun,

baba

[ChrisWerner]

Thank you very much baba and Philippe, I can confirm that Wavlab runs on the Xite now too.

[Musicmarp]

I could use wavelab with the microsoft driver but it wasn't possible to record. I could load a wave file via the browser, edit it and save it for use later. So i could not record the mix out in scope because the wave dest driver don't work. After installing the regpatch i've had access to the asiosource and not the wavesource. Also cubase 5.5.3 64bit(win7) didn't work anymore. Even after removing the regfiles you mailed me. Now this issue is fixed after the help of Steinberg support.
I can not use the " release driver when app.....in background" because i use 2 screens (dual head). One with the cubase and one with scope. So when this " release driver..." is on, when working on the scope screen the sound of the running cubaseproject stops until i turn back to the cybasescreen.

I think you mix the mailreply of me and another member. I do not use X-ite.

Grtz and thanks

[babaorum]

After installing the regpatch i've had access to the asiosource and not the wavesource

It is exactly the objective of the patch ...

here when I applied the patch I have the choice between ASIO and wave drivers in wavelab :


I don't understand, cubase still works fine here with or without the patch I don't see the link between this patch and cubase ...

Maybe you have a conflict with another device in your PC ...

[Musicmarp]

You don't understand what i mean. In scope there's a difference between an asioscope-sourcedriver and a asioscope-wavedriver. I do not mean the windowswavedriver MME if i quote wavedriver.