Tip of the day! Importance to set correct SMPTE CLOCK, 1 hour in MODE!  

 
You need to change the SMPTE CLOCK 1 hour in in SYNC Preferences 01:00:00:00:00. to stay in correct sync with audio.

 
Use 30 FPS Non Drop. not 29.97 FPS df as shown at the picture

It's apply to anyone. If you use a audio card, midi interface that you do working with sonar it is important to change SMPTE one hour in, even for those that work ITB.

So make a long story short! So why take a chance getting problems down the road if you can prevent them today?
Changing it to 1 hour in (01:00:00:00:00) will guarantee you that you will have the best experience working with any DAW now or in the future.

SMPTE was originally developed in the days of black and white television. Drop frame (as in 29.97d) had to be created with the invention of color tv, because a colour show was slighly longer than the same black and white counterpart.
Thus the reason for drop frame for SMPTE to be interchangeable with different media types.
Drop frames occur at 00:00:00:00:00,  but not at 01:00:00:00:00.
Hey, I hope a 40 year career in  television gives me the creative licence to simplify the explanation for the masses.

I didn't understand any of that.  But I trust you guys. If I make this change will it affect my current projects?

Barczar


I didn't understand any of that.  But I trust you guys. If I make this change will it affect my current projects?

No, it shouldn't unless some of your projects are syncing to external harware using SMPTE,  or previous video files.

  So if I make the adjustment as proposed by Freddie, shouldn't the "Timecode Format" also be adjusted to "29.97 FPS ndf"?

Does this explain why some clips (with a proper time stamp) get imported so far in the time line that you sometimes don't notice them at all and start wondering why the clip didn't show up?

I change my offset to match what my client sends me. 

As Freddie points out everyone usually starts at 1 hour.  The simple reason for that is problems when crossing "midnight".  in the past machines need pre roll so starting before 00:00:00:00 caused problems.

When I work on TV shows my offset is 00:59:50:00 for the 1st segment.   That gives me a 10 second  pre roll and the show starts at 01:00:00:00.

I'm supposed to be given Drop Frame for reasons mentioned,  but because newbie editors simetimes don't know this I can receive anything.

I make it a habit to check the frame acuracy from the burnt in TC to Sonar's just to make sure I'm going to keep sync.  But that has not been an issue for many years.

If seg 2 (after the 1st commercial break) starts at say  01:12:18:04....I set my offset 10 seconds before that.  Then when I send my OMFs to be mixed into the TV show the music stems drop right into place for the audio mixer.

When I do film work I start my cues in Sonar 10 seconds before the 1st frame of music for the exact same reasons.     

Alegria


  So if I make the adjustment as proposed by Freddie, shouldn't the "Timecode Format" also be adjusted to "29.97 FPS ndf"?
 

I think that is just where his screen capture was when he copied it.
Set it to where you need it
Example below
30 is the norm for mulititrack audio studios.
29.97 when syncing with NTSC video.
25 for PAL and SECAM 
30 for ATSC video(north america)
24 for film
 
The important part is for all synced devices to be the same.
 
 

Jyri T.


Does this explain why some clips (with a proper time stamp) get imported so far in the time line that you sometimes don't notice them at all and start wondering why the clip didn't show up?

Yes that is one possible reason. Especially if they are Broadcast waves which use the SMPTE  timestamp

Great tip Freddie!