Using Audacity’s recommended method of setting the Latency correction, i.e putting the mic close the the headphones, I end up with a correction of -426mS on my MacBook Air M1. My old windows machine was around 85mS. The MacBook seems to work quite happily at this setting but I am surprised it is so long. What do other Mac users get?
I asked about this a year or so ago, but did not get an explanation.
I believe I designed that headphone technique. You need to be on headphones to do music or performance overdubbing and the quality of the test sound doesn’t matter. Only the timing. So it’s a natural.
Let me read this back to you. “My overdubbing is working perfectly. What am I doing wrong?”
Just kidding. You are experiencing a Forum Environment Problem. To respond to your question, a poster would have to be:
A musician.
Interesting in recording their work.
Can perform more than one component of the work (two voices or one voice and instrument).
Records on the computer.
In Audacity.
Is a member of the forum.
Familiar with posting replies.
Is willing to reply.
So I get that down to four people on earth.
I designed the technique and I guarantee it works, but I’m not a musician and I’ve never actually, musically, used it.
I don’t think a half-second is that bad. Are you using any other sound applications? Multi-Player Games? Skype/Zoom? are any of them running in the background? Google Meat will take over your sound services and you have nothing to say about it.
The new Macbook Airs can have some surprises. I have a New 13" M3 and it gets hot doing some pretty ordinary jobs. I wasn’t paying attention, but I think it did pause in the middle of a job to take a breather and cool off. It didn’t actually tell me to go make coffee, but it was implied.
I am a member of an on-line book club and I join using a much older ventilated MacBook Air. It gets very hot during the meeting—I can just hear the fans running—and I’m guessing the shiny new Air wouldn’t make it all the way through. I’m considering sending it back.
Koz