Helpful ReplyAudio artifact that isn't really there

Author
soundman32
Max Output Level: -90 dBFS
  • Total Posts : 45
  • Joined: 2007/10/09 03:57:32
  • Status: offline
2012/05/12 09:06:14 (permalink)

Audio artifact that isn't really there


I was recording some overdubs for a band this week and during playback we heard an audio artifact (a click or sqwelch) that we've never heard in any other mixes on this song.  It is repeatable every time when playing back within Sonar, but the original wav files don't contain this click, mixdowns don't contain it.  Soloing each track individually, you can hear the click.
I thought it might be a hard disk throughput issue but there aren't that many tracks (24).

It is just so repeatable at exactly the same point in the playback, if I start from the beginning or half a bar before.

I'm convinced if I load all the tracks into a new project, everything will be ok. Except then I have to re-create all the levels, fx and settings, which is quite a big task.

Any ideas?

Sonar 8 Producer Edition.  Windows 7 (32-bit).  All standard plugins, no VST instrument tracks, all audio.
Tascam 1804 Firewire sound card.
#1
Ace.trouble
Max Output Level: -89 dBFS
  • Total Posts : 57
  • Joined: 2010/08/16 10:44:43
  • Status: offline
Re:Audio artifact that isn't really there 2012/05/12 09:13:37 (permalink) ☄ Helpful
Hi!

You have a 32-bit Windows PC. So it's not like 24 tracks is nothing. If many or even all of these tracks also feature VST plugins... well, then it's no surprise you'll hear clicks, stuttering noises etc.

With your 24 tracks project what do you have your sound card's Buffer Size currently set at?
Try increasing it and see if the noise disappears.

I've had quite a similar issue. I ran 34 tracks at 128 samples Buffer size, so naturally the playback wasn't fluid.

At first I thought there was something wrong with the recorded wav file, 'cause the noise (like a hiccup) would always be at the same spot, just like you've experienced, too.

When I increased the Buffer Size to 512 samples, it was fine.
post edited by Ace.trouble - 2012/05/12 09:23:18
#2
soundman32
Max Output Level: -90 dBFS
  • Total Posts : 45
  • Joined: 2007/10/09 03:57:32
  • Status: offline
Re:Audio artifact that isn't really there 2012/05/12 09:25:48 (permalink)
That was it.  Thanks Ace. 

I have been recording with ASIO latency at 128 (bytes I presume) for a couple of years without any problems.  

With this particular project, the click goes away at 1024.  I tried the other settings (256 & 512) but they give the same problem.

The mixing latency page in Sonar is all greyed out so I can't change it, but it shows 2 buffers in playback Q and effective latency is 2.9ms.  Which, granted, sounds a bit small



#3
Ace.trouble
Max Output Level: -89 dBFS
  • Total Posts : 57
  • Joined: 2010/08/16 10:44:43
  • Status: offline
Re:Audio artifact that isn't really there 2012/05/12 09:32:02 (permalink)
Okay, glad that worked!

But remember, you wouldn't exactly wanna RECORD with 1024 Buffer Size, 'cause latency would be too high.
But increasing it for playback is cool.

If you still need to record additional tracks for that project, keep the Buffer Size low, but temporarily freeze other tracks/FX that you don't need.
#4
Cactus Music
Max Output Level: 0 dBFS
  • Total Posts : 8424
  • Joined: 2004/02/09 21:34:04
  • Status: offline
Re:Audio artifact that isn't really there 2012/05/12 20:30:32 (permalink)
Just so you know, It doesn't matter what the buffer size is as far as recording goes too. Only if you try and use real time effects or Guitar rig. Sonar adjusts the latency so all is still synchronized perfectly no matter what the Round trip latency is.

Johnny V  
Cakelab  
Focusrite 6i61st - Tascam us1641. 
3 Desktops and 3 Laptops W7 and W10
 http://www.cactusmusic.ca/
 
 
#5
Jump to:
© 2025 APG vNext Commercial Version 5.1