Hey markyzno,
Still trying to get to the bottom of the Sonar/ mp4/quick time sync issue. I've posted a new thread on it here:
http://forum.cakewalk.com/Sonar-with-QuickTime-MP4-or-H264-not-functioning-correctly-still-m3261535.aspx#3261535 
 
You are using Sonar for sound design so I thought I'd ask you to look at it. I've asked if someone could try a small test, exporting audio out of Sonar from an mp4 on the time line. Bring it back into another program and check the sync. I've tried with every scenario I can think of, different machines etc. same result. Anyhow, trying to figure it out.
Cheers!
JG

jonogrant
 
1. I bring an MP4 into sonar
2. export out some of the MP4's audio either as a broadcast wave or as a basic riff wave (jotting down the start time code)
3. open the same MP4 video in Sony Vegas
4. bring in the audio exported from sonar into the vegas file at the correct time code or import the broadcast wave
5. Sonar's exported audio is 2.5 frames later then the audio attached to the MP4 (which is the same audio I exported out of sonar) 
 
Reverse test: 
1. open MP4 in Vegas
2. Export a bit of the audio, jot down the time code start
3. Import the same MP4 into Sonar
4. Import the Vegas exported audio into Sonar
(Audio comes into sonar early by 2.5 frames)
 
*Bringing the exported audio back into the SAME program has no sync problem.
 
Basic conclusion so far is that the mp4 in sonar is playing 2.5 late.
I should also mention that I've done these tests using audio from different times in the 30 minute video and the amount it is off by is consistent, so it's not a drifting issue.
 
The audio in an MP4 is AAC, wonder if that has anything to do with it..
JG
 
 
  

 
Very interesting...Everyday I import a video into Sonar,  create audio, export a wav from Sonar and load everything back into Vegas.  If I keep the wav file exactly the same size as the picture file (control-A) everything lines up in perfect sync always....
 
However....today I was working and froze a synth,  it was an old, 32 bit VST (Virtual Guitar)  and guess what??  It was 2.5 frames late, just on a fluke after reading your post I thought to try 2.5 frames.
 
So perhaps there is an issue with Bitbridge,  or perhaps you as using, as I do, some plugins that look ahead and is causing this.    
 

I've thought about plug in latency and sound card latency but the tests I've done don't have any plugs or synths loaded. i do have jbridge on some things but not in the test sessions. I've done tests on my sons computer that has no sound card or audio apps at all..same result. My issue is with sonar files that are running any quick time, mp4 or h.264 video. There is no issue with AVI or WMV and especially not just audio with no video, all that syncs up perfectly..
 
Someone suggested that lossy files like mp4s get padded, adding a short top and tail to the video. Looking into that one. 
Cheers!
JG
 
 

PS. Even if I select the whole track (ctrl+A) and export, it's late when I import back into Vegas.
Even if the video is only ten seconds long I get the sync issue. Which means it's not a drift of any kind. The offset is consistent no matter the length. Another strange thing is, the videos I get have a burn in time code on the display, and it's usually consistent with sonars smpte display. So even if I cut the wave right on the second mark like: 01:02:00:00 and manually bring it in and sync it to that visual time code in vegas, it's off. It doesn't make sence except to say that the export function is delayed in Sonar when working with mp4s etc. My only fix at this point is to set an offset under the clock settings that is 2 frames behind. (I can't set it any smaller than a frame)
 
JG