Thanks, yes I meant to say it’s a Macbook pro 2012 2.3Ghz Intel core i7 which has 4 dual core CPUs, 250GB free HD space (SSD), so there should be plenty of oomph there.
Though TBH if I’m going to have to shut down wifi etc. in order to use Audacity then I might decide to try something else… but maybe you were suggesting for testing purposes…
I mean it used to work fine on my old 2002 Dell XP laptop without having to mother it too much
Yes I was just testing using built-in speakers. To see how the latency thing was.
Do you have bad sound that appears as if it’s latency shifting?
but maybe you were suggesting for testing purposes
Maybe. I have too many times when my laptop fans kicked in for no good reason and Go > Utilities > Activity Monitor told me “web page content” was taking up 125% of system resources and most of the memory. Apparently I can have a fist-fight between two companies about who’s going to sell my personal data and to whom.
Audacity is a 32-bit app, not 64 and not multi-processor compliant. It doesn’t take much to leave it bleeding by the side of the road.
You seem to be skittish about turning off WiFi. What are you running and are any of them audio services? Audacity doesn’t Play Well With Others. That’s one of the reasons it’s not recommended to record Skype or Games.
Does the latency ever change within one single performance? That’s very serious.
Yes I too know all to well that Google Chrome mission to take over the computer…
The only things I generally run are web browsers, word processor, email and the like… but sometimes itunes (not that it’s usually doing anything) and others. Will see what happens after a reboot then. I don’t have a problem turning wifi off, just a bit of resistance if Audacity was regularly going to need what seemed to me like it might be excessive molly-coddling. But for testing then yes I agree a clean sheet is needed.
Strange if no one else is experiencing this problem though.
What is the “Preferences > Devices > Latency : Buffer Length”?
Try changing that value in steps of say 20 ms, both down to 0, and up to 200 ms. Don’t worry about whether the latency correction (the track shift) is ‘correct’ during this testing - what you are looking for is consistent results. The default buffer is 100. Can you get consistent results with a larger or smaller buffer?
(Mac’s are a bit weird in this respect and sometimes work better with a smaller buffer).
Note that any changes to the sound set-up is likely to change the amount of latency, so it’s important to set up latency correction using the exact same audio set-up as you will be using when recording. If you change the set up in any way, you may need to repeat the latency correction procedure.
@koz: magnitude of the problem: track shift is currently set to -377ms. Sometimes that works, sometimes it’s 200ms off (roughly) or more.
I set the latency using the air between the mic and the speakers as a rough and ready loopback cable.
Ambient Noise Reduction was already turned off
Am still mystified - can’t imagine what is causing the problem - my setup seems pretty ordinary to me, but obviously isn’t.
@steve: buffer length currently 100. I assume that’s the default - when I installed Audacity 2.2 yesterday I cleared out all the old prefs and plugins (AFAIK)
Will see if I can find a loopback cable to set the latency and do the other steps suggested. It will probably be some time before I get round to all of that, and actually get a coherent set of results, but I will post back in due course.
The default click track has three identical clicks and one counter click. What’s that, a fox-trot?
Is it possible you’re aligning to the wrong clicks? Oddly, it’s better to sneak up on proper alignment rather than hit it first time out. That lets you listen to the one that’s almost right and hear that you’re aligning to the right clicks.