• SONAR
  • Timing off when using Punch in recording. Help! (p.2)
2013/04/24 18:39:27
The Maillard Reaction


Some real basic questions:

1) Does this happen when you overdub in general or just when you "punch in" and overdub?

2) What audio driver are you using? WDM or ASIO? 

If you are using ASIO you may need to employ the manual input of the latency. Some ASIO driver report their buffering in a way that SONAR only automatically compensates for some of the timing and you have to do a ping test and manually input the additional timing info. 

So, if you are using ASIO confirm that your delay compensation is solid with a ping test.

3) What sample buffer are you using on the audio driver?
4) How are you monitoring your guitar playing? Through SONAR round trip? On the I/O hardware dsp monitor mixer? On a outboard mixer before the I/O?


If the problem you are having is not some sort of specific bug than it may just be some minor misunderstanding about the set up. Some of the answers to the questions above may be helpful and maybe illicit a suggestion for a solution.




best regards,
mike 
2013/04/25 10:30:31
Ilovelife
He has a Focusrite 56 Saffire. Firewire.
The thing is... We use to punch in record on Sonar Producer 8.5 with no problem. We would do 50-60 punch in takes of me doing a different riff on each take and it would line up perfectly.... Not with Sonar X2!
2013/04/25 10:35:21
Ilovelife
Hey Mike,
To Answer your questions...

1) Does this happen when you overdub in general or just when you "punch in" and overdub? No, just when we leave it record for about 20 takes...

2) What audio driver are you using? WDM or ASIO?  ASIO

3) What sample buffer are you using on the audio driver?  We are using the default.. 64
4) How are you monitoring your guitar playing? Monitoring through his Audio Interface Headphone out.
 
Also, This never happened in Sonar 8.5. We could punch in and do 50 takes non-stop, and it would record fine with no timing issues and the waves would show up instantly after stopping the punch in record session....  In Sonar X2 AFter about 20 takes and we stop it, it takes about a 45 secs. for the waves to show up.
2013/04/25 10:37:54
Ilovelife
Yes, this is the same issue we are having...it seems that maybe the first 3-5 takes are in perfect timing...after that...each take moves further and further off.
2013/04/25 11:40:07
DeeringAmps
<RANT>
YOU CAN NOT LOOP AND PUNCH-IN WITH SONAR X1 or X2!
ITS BROKEN!
8.5.3 works PERFECTLY!
And TRUST ME, the FIRST TAKE is spot on, Take 2 is OUT OF SYNC!
Take 3 is WORSE, and it lags MORE on each successive take...

I hope this ENDS the discussion.
Don't ask questions or offer solutions.
Do a "Ping" test (as Mike describes it).
IT DOES NOT WORK!

</RANT>

T
2013/04/25 18:49:55
The Maillard Reaction
Thanks for answering the questions lovelife, it sure seems like you had a handle on all that stuff.

Hi Tom, wow, I hadn't heard of it yet. It sounds nasty too.

Is it also happening with non ASIO drivers? I have had a long standing observation that when I loop record in SONAR the clip is not as long as the loop. There is a very small gap, just a few samples. The timing of a loop is fine but if you make it into a groove loop and drag out a length of groove clips the timing will slowly drift by the length of the "gap" and it accumulates. I have been been asking for that bug to get fixed for years and years. It's still there in 8.5.3

I wonder if this is somehow related. Maybe that little gap is showing up in the punches as well?

I never saw it with WDM just ASIO on my MOTU stuff. I don't think it happened on every bodies ASIO gear, but back when I had hopes for a fix a lot of folks checked and confirmed they could see the gap when they zoomed in 100%.

Anyways.

Sorry for the distraction with the questions.


best regards,
mike



2013/04/25 20:40:28
DeeringAmps
Mike,
Haven't tested with the WDM Drivers.
I've never used groove clips with audio; interesting though.
The clip is a few samples short?

No distraction, just me in a rant...

Take care,

Tom
2013/04/25 22:54:45
swamptooth
in your windows audio settings make sure playback and record advanced settings for sample rate and bit depth are set to the same values.  this was a known issue with early win 7 and might be a part of the problem.  apparently rogue poorly coded programs would use the audio drivers but not reset the sample rates when finished.  might be worth a look.
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account