Strange timing offset problem (SONAR X2)

Hi,
I am noticing an odd timing issue with a project I'm working on that seems to have just started. 
Everything gets recorded late.  So if I record an audio track starting at 2:00:001, I have to go back and set that clip to start to 1:04:810 in order for it to play in time.  It's very consistently this exact offset.  I'm not experiencing much latency at all when recording, it sounds like it's in time.  Oddly enough, it seems that the same thing is happening with midi data!  Is there some offset setting that I'm not aware of? 
 
My latency is set at 4.4msec on an intel quad core running sonar x2 with MOTU 828 MK II. 
I have no 'Record Latency Adjustment' in the preferences set to anything but 0 (the Manual Offset).
 
Any ideas? 
Thanks,
bri
 
 
 
 

I did a test the other day two songs one in X1 Studio and one in X2 I noticed the metronome was of in X2 by a fraction.
 
Better experience of recording in X1. Not sure why this issue has raised its ugly head again. X1 is definitely more fluid. X2 a bit sluggish hope they come up with a patch before moving on. You would expect timing these days not to be an issue. As when it is I am sure it can cause other things to fall out of place.
 
It's what you call sloppy programming!

Dappa1
I did a test the other day two songs one in X1 Studio and one in X2 I noticed the metronome was of in X2 by a fraction.
 
Better experience of recording in X1. Not sure why this issue has raised its ugly head again. X1 is definitely more fluid. X2 a bit sluggish hope they come up with a patch before moving on. You would expect timing these days not to be an issue. As when it is I am sure it can cause other things to fall out of place.
 
It's what you call sloppy programming!

What interface are you using and what's the buffer size?  
 
If X2 was that different vs. X1 just for pure recording, no doubt there would have been plenty of reports about that by now...  And FWIW, I have the opposite reaction - X2 feels smoother than X1.   I know it's more about the subtle workflow changes, but since I haven't noticed any latency issues at all I'm good with those subtle workflow changes.

I'm fairly certain there are at least a few other users that have the Saffire Pro 24, so hopefully they can help by looking at their configurations.
 
FWIW, I'm using a Focusrite 18i6 but that's USB vs. Firewire and I'd image different/newer drivers.
 

Thanks for all of the suggestions.  I opened up a brand new project and recorded some test audio, which was completely fine, as well as the midi, so brundlefly, I believe you are right...something is amiss in this project.  I guess the good news there is that my audio card settings are ok. 
 
  After your tips above, I was certain it was a plug-in I'm using called Artillery II, but even after disabling all fx (using the e button), and recording with fx disabled, the same exact amount of offset on a brand new track with no efx going straight to the master bus.
 
I am actually more puzzled now than before ;) 
It is a big project (65 tracks, 15 softsynths, lots of audio), but I'm not seeing any lag and can't imagine this would result in the kind of problem I'm experiencing.
 
 
   

acatalyst
...but even after disabling all fx (using the e button), and recording with fx disabled, the same exact amount of offset on a brand new track with no efx going straight to the master bus.

 
If it has something to do with Plugin Delay Compensaiton, you will need to completely remove the offending plug-in from the project, becasue SONAr maintains continues compensating for disabled plug-ins because you could hit the button at any time, which would cause a big hiccup otherwise. and PDC affects all tracks in a project because they have to be delayed to sync with the track hosting the plug-in.
 
I suggest you try taking that plug-in out of a copy of the project or possibly freezing it as thebiglongy suggested. In general, latency is not something that goes up with load (you just get dropouts until you deliberately increase latency by raising the buffer size), but if it's PDC-related, freezing should be the same as removing. You can also try PDC Overrride, which disables PDC on input-monitored tracks, but from what you've described, I don't think that's going to help in this case. Whatever's causing this likely needs to be removed from the project.
 
 

Finally got around to brundlefly's suggestion of actually removing the Artillery II plugin, and that did the trick!  Since it's sort of a buffer-type plugin (glitch and loopy stuff), I suspected it may be the cause, but it wasn't until I actually created a new version of the project, deleted the plug, and saved that I was able to record again with 'normal' timing.  So, for everyone's benefit, if you use this plug, don't add it to your project till you're done with recording and are in the editing stages. 
 
Thanks to everyone (especially brundlefly) for helping me resolve this issue!
bri