Page 1 of 1

Fluctutation with recorded audio in 6.0.1

Posted: Wed Nov 01, 2006 7:42 pm
by Tom_Verlaine_Jr
Hey guys...

I've recently upgraded from 5 to 6 and ever since I've had this problem with audio recorded in 6.0.1 where there are these rapid inconsistant level fluctuations (it can be seen in the clip waveform). Audio sounds fine with other packages (Cubase) and even while recording though Live

I use an Intel 1.7G laptop with 1G RAM, XPsp2 and an E-MU 1616 interface with the latest ASIO drivers, although I get exactly the same problem when using the laptop's onboard Realtec HD soundcard.

Since recording audio is essential to my music production (I'm a guitarist) it'd be great to find out what's going on

I've not been able to find an answer anywhere else on the forums, so it could be something daft on my part (I kinda hope it is...)!

Thanks!

Posted: Sat Nov 04, 2006 3:55 pm
by j24keys
Could be old plugins eating your CPU. Is your usage high at these levels?

Posted: Sat Nov 04, 2006 11:39 pm
by longjohns
do they look kind of like this?

Image

Posted: Sun Nov 05, 2006 10:33 pm
by Tom_Verlaine_Jr
I try to keep my CPU usage fairly low... rarely let it get too much over 30% and my laptop is pretty stripped down for music, so there shouldn' be a problem there.

Yes, those kinda do look a little like what I'm getting!

Posted: Sun Nov 05, 2006 10:47 pm
by longjohns
i have no idea if that's actually happening to you, but that's comb filtering by combining 2 waveforms at slight delays.

could there somehow be a signal chain problem where your signal is getting doubled up when recorded?

then the latency between the two signals could create that kind of cancellation pattern.

maybe a long shot but that's what popped into my head

Posted: Sun Nov 05, 2006 11:33 pm
by longjohns
or actually, are you using two mic's on your guitar? that could do it maybe

Posted: Mon Nov 06, 2006 8:40 pm
by Tom_Verlaine_Jr
That actually seems to fit... my guitar is DI'd into a single mono input, but it may well be that there are some routing or latency issues somewhere... Need to go check it out...