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
 
 
 
 

That's how far off your interface is.
Use ASIO drivers and let Sonar set the latency.
 
HTH,
Tom

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!

Thanks Tom.
I have been using the WDM drivers successfully for as long as I can remember, so this is a recent development.  Is there a benefit to switching to the ASIO ones? (i.e. are they considered more stable?) 

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.

Saffire pro 24 with both X1 and X2 maybe the buffer sizes are the same for both but maybe it needs a little tweaking in X2. The differences are not enormous but you can tell there is a difference in feel.

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.
 

Before this gets off topic, I'll reiterate that the OP's interface is MOTU 828 MK II. And I'll point out that the error he's reporting is on the order of 750 milliseconds - way more than any normal latency issue could account for. Given the size of this error, and the fact that there is no single setting in SONAR that would cause both audio and MIDI to be offset by the same amount, I have to think this is a project-specific issue due to some plug-in misreporting latency or otherwise misbehaving in SONAR.
 
Bri, are you seeing this in any other project? If not, I suggest you start by temporarily removing any 3rd-party FX plug-ins that you haven't used in other projects, especially anything added since you noticed the problem.
 
 

Brundle's right on the 750 milliseconds being very odd?
HOWEVER, when using WDM drivers you have to test and set the offset manually for each
buffer size. ASIO will let Sonar adjust "on the fly" so to speak.
Although some interfaces are not "spot on" in their reporting to Sonar.
 
Disable all your effects (e key, right?) and see if that affects the timing.
Tom

I did mean to second the suggestion to use ASIO driver mode. ASIO is preferred/recommended by most interface manufacturers, I think. And it's generally a little easier to see and manage what's going on with latency compensation using ASIO.