Well wave drivers have up and died, so now asio in wavelab?

An area for people to discuss Scope related problems, issues, etc.

Moderators: valis, garyb

Post Reply
Basic Pitch
Posts: 627
Joined: Fri Aug 15, 2003 4:00 pm

Post by Basic Pitch »

Hi gang,

Well I am really at a loss here but for ever since SPF 3.1c I have always had wavelab recording wave destination directly from mix l/r and all has worked out well, untill a few days ago, now it constantly crackles and sounds like hell, so.....

I have set Wavelab to read ASIO Scope and set in/outs to 1+2/1+2 or what not as these can be changed. So now in the mixer I just set the outputs of the master mixer channel to direct to the corresponding asio channels to wavelab, but even like this I am getting some minor crackles now, not sure whats causing this.

For those of you who use wavelab how do you have your routings set up? and for those who have used the wave drivers, whats the deal with those modules, is it common for them to just all of a sudden one day start to sound like shite :wink:

Cheers and thanks in advance.
Top
arela
Posts: 858
Joined: Tue Aug 27, 2002 4:00 pm
Location: Norway

Post by arela »

Same here, last night i recorded from Audition, via sfp + fx and back to Audition (wave's IN /OUT) ...and got a lot of crackles
Never had theme before.
Going from 32 bit to 16 bit solved the problem. (Source is 32 bits files)
Not shure if this is a Audition 1.5 problem,
or sfp?
Maybe a conflict between floatig/integrer protocols?
Top
User avatar
BingoTheClowno
Posts: 1722
Joined: Wed Nov 12, 2003 4:00 pm
Location: Chicago
Contact:
Contact BingoTheClowno

Post by BingoTheClowno »

I don't understand yet why would this make a difference for the wave drivers, however, if you go into the Direct X properties (Run->dxdiag, Sound tab) and chose Basic Acceleration option, that will improve the crackling (I mean it will reduce it). I don't understand why would this make a difference, this setting I thought is related to DirectSound output.

Try it!

<font size=-1>[ This Message was edited by: BingoTheClowno on 2004-07-06 17:11 ]</font>
Top
oxygenial
Posts: 79
Joined: Mon May 12, 2003 4:00 pm
Location: Sweden
Contact:
Contact oxygenial

Post by oxygenial »

This happens to me all the time, in all apps! The only solution I've found so far is either change from 16 to 32bit or vice vers, or just recreate your 32bit project from scratch and it'll work for a while again!

Having similar problems with both Optimaster and MiniMax, which both will cease to function properly after a while. I just delete them from the project and adding them again, and they'll work for a while again!

<font size=-1>[ This Message was edited by: oxygenial on 2004-07-06 18:01 ]</font>
Top
Post Reply

Return to “Problem Solving”