Jan 19, 2010 03:49 am check yer latency
crackle and noise if i record more than 4 tracks
Posted on Jan 19, 2010 02:58 am
merray
Member Since: Jan 19, 2010
I have just installed audition 3 ,I have a behringer fca 202. computer specs are p4, 3ghz, 2 gig ram. I have guitar rig 4 as plug in.
My idea was to play various instruments building track by track.It seems to work perfectly until I get to the fourth track .at this stage it starts getting noisy(crackle breaking up),if I delete one of the earlier tracks the noise disappears ,so I assume its just the number of tracks causing the problem
I am totally new to this so most of the settings are default settings.
Any help in reguards to this would be much appreciated
thanks. Ray
[ Back to Top ]
Jan 19, 2010 03:49 am check yer latency
Jan 19, 2010 04:19 am latency is 4ms
sample rate is 48khz
buffer size 192 samples
are these settings ok?
Jan 19, 2010 06:35 am well its starting to get a little small for that amount of tracks whilst having that much ram, but still you can do things to combat this.
can i ask what exactly what you have on each track fx wise?
I use pod farm with EZdrummer and i can get around 4 tracks of guitar going on 192, but i also have 4 gig ram.
main thing is, is to not have any fx at all on any tracks you dont need, to keep the pressure off the cpu.
what i do also is, if i start to get drop outs, i will go in and turn off pod farm on all the tracks im not using while recording on 192.
of course when im done recording, i change the buffers to say 786 or 1024 or something big like that.
you'll be able to run a crap load of tracks then with no hassles, its just not adequate for recording is all.
by the same token, as your finding out, you cant run big amounts of tracks on 192. small buffers for recording, and big ones for mixing.
you'll be surprised how you can manipulate the situation by simply turning things off, like all FX and any plug ins or synths that you dont absolutley need for that time.
Jan 19, 2010 11:15 am I would try setting your buffer size to 512 and see if that does it.
Jan 19, 2010 01:35 pm Recording with this type of setup is outside my experience, but I thought of a possible cause of your problem. If I understand correctly, you lay down multiple tracks one at a time. If you playback one, two, three at a time the signal is clean. Add a fourth and it starts to break up.
Could it be that you are adding to the strength of the output signal with each added track, so that the four track signal is too hot for some part of the playback signal path? Maybe what you are hearing is a clipped signal as it plays back and not a defect in the tracks themselves or in the mix.
Just a thought.
Jan 19, 2010 06:17 pm Your latency needs to be upped (perhaps): try 50ms, and kick up the buffer size to at least 1028. Run it, and see what happens. If it works, leave it, if it doesn't, and it still crackles, up the buffers again.
Jan 19, 2010 07:01 pm only problem is you'll notice the latency on anything around 512 and over.
you could try 512, you could try 384 you could try 256.
it depends on the music style and how responsive you need the timing. Vocaly, bigger latency will drive you nutso.
Metal, youll need the response, other styles not so much. i just assumed you were doing metal because, well, metal rules.
If you really wanted to get techy, you can set up an offset, so you could have your latencey on 1024 and the offset will automaticly put it in the time frame you allocated. you'll need to direct monitor though, and im not sure how you would do that using a guitar simulator as a plug in.
a good thing to get used to though right off the bat, is to limit the FX you use till the mix stage.
Jan 20, 2010 05:26 am thanks everyone for the help ,lots of things here to try,I have to many effects and plugins running,so i will start there.
metal rules? I'm 58 years old, metal still does it for me
Jan 20, 2010 07:48 am ha ha ha, cool man, was joking but, metal still does rule. good to see youre liking it still.
should run better now with little FX
Jan 20, 2010 12:26 pm Another thing in Audition, when all those effects are applied you can simply lock/freeze the track while tracking the rest of your song (little button up near the sends in mixer view). This writes all FX to a new .wav and references that until unlocked/unfrozen. This will take a huge load (depending on how many FX you have going) off the CPU and reduce or eliminate the clicks n pops. If you apply any delay or reverb to a track, freeze it mas those are very CPU intensive.
When you are done tracking, crank the buffer size, unfreeze and mix.
Jan 20, 2010 08:36 pm ah dude! yes!
I totally forgot about freeze. that's the ticket for sure.
cheers Cap' dunno how i could have forgotten freeze, i will use that today no doubt.
Jan 20, 2010 09:45 pm I can't be the only one here who monitors latency free--that is, listening to and performing (recording) whilst monitoring the mix from the mixer. I'm not listening to the recording as its being made, in other words. I record, usually with buffers set as high as 2400, with no issues. However, MIDI soft synths are another story. Buffer sizes seem to be irrelevant, but the ASIO latency can't be any higher than 4ms. I accidentally have monitored with latency this low on vocals, and it was unacceptable--the weird echo is impossible. But as far as everything but MIDI goes, direct monitoring simply doesn't matter (for me). I know some folks like to hear vocals, say, with some reverb on them that doesn't get included in the take, but the workaround for me is outboard gear running to a separate track(s). Same for guitar--I only use outboard. No help, of course, for those using plug-ins for guitar, like a scenario mentioned above.
Cpt Tripps, your right about the freezing of tracks, but once I reach a certain plugin/track count point, the tracks frozen have to stay frozen, even during mixing (especially during mixing, what with the slider and mouse movements going on.)
I'm currently using Samplitude, and I'm guessing that freezing here is basically the same as in Audition.
All this being said, it looks like merrey should be able to run much more stuff than he is without hearing the clicks and pops. Don't quit now, merrey--I'm 53, and it just keeps getting more fun with each passing blessed second. I'm now working on soundtracks for a fellow employee's short-form videos, in addition to new things for our band.
Jan 21, 2010 04:11 am not sure you can use guitar sim's without the daw monitoring though.
Jan 21, 2010 05:37 am I increased the sample rate to 384 ,latency 8ms,this made a big difference .I can now do 5 tracks before any noise. I didn't notice the increase in latency when playing, can probably up it a little more.I will play around with some of the other suggestions offered over the next few days.
Thanks again for all the help
Jan 21, 2010 12:39 pm 512 is about the max for me, anything higher and I start to notice the delay.
Tim N, I run my buffers at 256 and monitor latency free for as many tracks as I can record. I can run a few reverbs and delay along with a ton of comp and EQ before I ever start to get any clicks/pops.
But to achieve this I am running a quad core with 3 hard drives (OS, scratch for audition, and tracking are all on different drives) along with 9GB o ram. CPU plays such a heavy role when using verb, delay, VTSi.
I used to leave things frozen on my old low end dual core and have been in heaven ever since I upgraded.
|
Related Forum Topics: |
If you would like to participate in the forum discussions, feel free to register for your free membership.