So here it goes. Set up a couple of SD3 drum clips, turn on the loop button and set from start to end on the ruler. Start the loop to insure timing on the turn around is good.
Now arm a trk to record and record lets say 5 take lanes. I'll solo out each take lane to find the "keeper" delete the junk and collapse the take lanes so my take is back in the channel. Press play to hear the loop. Now here's where it starts to get messy. Each pass of the loop gets further and further away from being on time.
 Now not 100% sure on this but, I do beleive I have tried with & without "Remove DC offset" aswell as "Nudge".
Any idea's on this?
 
Kev.

Are you by any chance running 32-bit SD3 Bitbridged in SONAR x64? And what sample rate and driver mode (ASIO or WDM) are you running? If WDM, I recommend trying ASIO if the Tascam supports it.

Also, I'm assuming you are recording audio, and you're saying SD3's playback is getting out of sync with both your audio and the metronome if you enable it on playback.  If that's right, is SD3 getting ahead or behind?

I have the same "out of sync" issue when looping playback. 

I'm on Windows 7 64 with Sonar X2 64 pro, but had the same problem wit X1 pro when using Fxpansion Geist (64 bit). I've seen others post about, and it's a nuisance (especially in the composition stage when I'm vibing and clicking).
Wish I didn't have to, but I been working around it by drag copying clips out to a suitable length

Same here, tracks will slowly drift out of time when looping a section. As soon as you stop and start again it goes away, then slowly drifts out of time again.

Hugely annoying when you're practicing a difficult part or experimenting with the arrangement.

Several others said they also have this bug last time I posted about it.

I confirm I've seen this too.  X2 32-bit on W7 64.  I noticed it immediately as I went from 8.5 to X2. Maybe the midibuffers setting could fix. I tweaked mine off another thread a couple of days ago, but haven't done any serious testing yet as I've not needed to loop for long periods.

I'm pretty sure it's something MIDI related, I can get Sonar to drift just playing a drum midi track, the notes played back in a loop all coming from the same drum VST will drift out of time.

Happens with different vst instruments, for example a bass line playing on its own (MIDI again), no other tracks, notes slowly drift out of time with each other on the same midi track.

Hugely annoying when you're jamming up a solo doing a stack of takes to pick a good one.

Thanks Brundlefly for reminding me about my drivers...I had to change them from ASIO to WDM Pre quickfix 308 and forgot to try the ASIO again. So I switched back and tweeked the buffers. Don't know if that was the culprit but it hasn't drifted off time sence.
Best of luck to the rest of you dealing with the drift.
Thanks again.
Kev

PS I should add that I checked out SD3 properties and I am SD3x64.

I switched back [to ASIO drivers] and tweeked the buffers. Don't know if that was the culprit but it hasn't drifted off time sence.

Glad to hear you got it fixed. In my experience, the great majority of these looping sync problems turn out to be hardware/driver/config/synth-specific issues.


One bonafide bug to be aware of is that having a MIDI FX on any track (regardless of which one, and whether enabled or not) will cause SONAR to play some notes from the measure following the end of the loop range, which can have the effect of making things sounds out of sync, though the error should be consistent, not getting progressively worse with each pass. I just confirmed this bug persists in X2. 


Personally, I've never been able to replicate a progressively worsening sync error when looping, though I've tried many times with different synths and scenarios in various versions of SONAR over the years when it's been reported by others. This is why I tend to think it's probalby due to some sort of hardware/driver interoperability issue in most cases - possibly involving O/S and even motherboard/chipset-level issues that make it difficult or impossible to troubleshoot remotely.

The worst I ever see is that if you try to null a live MIDI-driven synth against a bounced audio track, you might hear a trace of a transient right at the beginning of the loop, and if you start-stop the project inside the loop, that error may persist throughout the loop. But this error is on the order of a sample or two, does not get progressively worse, and is only audible when doing a null test. You'd never hear it as a timing error in normal circumstances. WDM driver mode seems to be more prone to this than ASIO, which is one reason I prefer ASIO.

This phenomenon may also manifest more with some synths, depending on how consistently they render MIDI to audio from one pass to the next. Session Drummer is not the best in this regard, but again, I wager you'll never be able to hear it unless you're trying to null live MIDI-driven playback against a phase-inverted bounce.

All that said, there does seem to be an inordinate number of new reports of this drifting sync problem with X2, suggesting that some change might have been made to the audio engine (maybe in conjunction with attempting to make playback more "gapless") that might not be playing nice with some environments.

It's not just X2 X1 and 8 and 7 all have had these issues. They are NOT wholly hadware config related issues and are quite easy to replicate. the midi - audio engine for plugins is not doing so well. ASIO at 1.5 ms latency helps ALOT but its not perfect. Audio to audio loops fine midi hardware loops fine MIDI- VST/DX babow!!! HOPE THEY FIX THIS

BTW try this on the matrix and see what happens EEEWWWW