Problems with Wavelab / Scope

garryguy · Post by **garryguy** » Sun Dec 02, 2007 6:33 am

Hi,
I have a problem with audio recording, using Steinberg Wavelab essential. Not sure if this is a wavelab or a Scope problem, however, I hope to get an answer here.

Wavelab offers the use of different drivers for play / record:
ASIO Scope, MME-WDM Creamware and MME-WDM Microsoft. Each is fine for playing audio, recording only works with the ASIO driver. Recording with the MME-WDM drivers results in horrible cracking.
Since I'm using the ASIO Drivers in Cubase I can't use both programms together. The problem occurs independent of the number of buffers and memory used for buffering.

Has anyone an idea?
Many thanks, Gerold

WIN XP, Service Pack2
Pentium 4; 3Ghz
1GB Ram
Gigabyte 8IPE1000 Mobo

Yogimeister · Post by **Yogimeister** » Sat Jan 12, 2008 10:15 am

Same problem here ....

Any clues?

Post by **garyb** » Sat Jan 12, 2008 10:18 am

try changing wavelab's priority to "above normal"..(cntrl-alt-del/ processes/right click on wavelab/ choose set priority)

Polarity · Post by **Polarity** » Sat Jan 12, 2008 12:14 pm

Do you have installed Win XP in ACPI mode?

Crackles in recording: I got the same problem recording Cubase mix inside Wavelab, every time I tried to use Windows in ACPI mode.
These problems with Wavelab went away only when I switched to Standard PC mode (turning off Hyperthreading was not enough).
No other tuning of wavelab or scope ever worked for me to resolve it.

Two PCs using Pulsar in years and the same problem both time: crakles in Wavelab when using WDM drivers.
You have no other chance I think.

However, converting to Standard PC mode have sense if you still have a P4 or similar CPU.
Now with multicore CPUs I think it's a "shot in your foot" to disable Hyperthreading and ACPI mode...

You could direct your source to be recorded (full mix?) back inside an ASIO input of Cubase (instead Wavelab) and rec it on a track of your sequencer.
I'm doing this (for other needs, for synchro matters) since a month and till now I didn't regret it (compared to using Wavelab for that).

Hope, it's useful.

dubcotics · Post by **dubcotics** » Sun Jan 13, 2008 8:35 am

hi,

same here, been struggling with it for a while , now I only record via sts for short takes, wavelab was straightforward tho for such purposes,

regards,

didier

H-Rave · Post by **H-Rave** » Mon Jan 14, 2008 5:59 am

if you use them both together wha's your cpu usage and asio usage like and how much memory do you have, just the fact that you're running them both together seems very cpu consuming ?

dbmac · Post by **dbmac** » Mon Jan 14, 2008 6:44 am

Try a higher ULLI value in Scope/Settings.

/dave

valis · Post by **valis** » Mon Jan 14, 2008 2:14 pm

Check your 'audio priority' level in cubase. Chances are it's set to High or Very High and is getting enough timeslices over Wavelab that wavelab isn't able to service the wav buffers fast enough. The downside here is that if you reduce Cubase's priority you'll impact its performance too. You can try increasing Wavelab's priority (and there are actually in depth buffer settings for Wavelab's internal buffering of Wav/MME as well you can tweak) but what you really need is to increase the priority of the WAV driver too eh?

Most people would use Cubase to record ONLY, and simply use wavelab when you needed to do an editing task outside of cubase (editing samples or other audio sections before importing to cubase's audio pool, etc). There's not much reason to need to record into Wavelab if Cubase is already running, and people often come here with this complaint because they're trying to record output from Cubase into another app. Just route back to cubase itself and into a new track, mute the track so it doesn't get sent to an output again and record away!

H-Rave · Post by **H-Rave** » Mon Jan 14, 2008 2:43 pm

Or an audio mixdown.

Post by **garyb** » Mon Jan 14, 2008 2:52 pm

and you've got a seperate harddrive to record to, right?(a drive to record to and one for your programs)

Polarity · Post by **Polarity** » Tue Jan 15, 2008 3:33 pm

I think I know what kind of "crackles" he has with recording in wavelab.
They are not the same crackles you can get with CPU overload or too low latency...
they are just slightly different...
lighter ones.

Am I right?
It's tha ACPI-hyperthreading thing...
could be a thing/bug that happens with P4 CPUs?

widy · Post by **widy** » Wed Jan 16, 2008 12:20 pm

hi

i also got this crackls during record via wave dest out from scope ...
but if i swithc ulli from 13 to 7 and back to 13
and than swithc 44 to 48 and back to 44 khz in settings.. it works fine

dont know why .... but doesn't matter ..because this workaround fix my problem .... maybe it works also in your setup

lg widy

korgano · Post by **korgano** » Fri Mar 07, 2008 7:35 am

Hi, I have the same problem too.
with my
q6600

wavelab cracles in recorded files.

check here for my story:
http://www.planetz.com/forums/viewtopic ... sc&start=0

korgano · Post by **korgano** » Sat Mar 08, 2008 8:59 am

How should I route in SFP project to be able record with ASIO2 24bit in SFP project, with wavelab?