23.98 FPS work-around?

Hello,

I am receiving quicktimes at 23.98 fps, but as we all know, Logic does not run at that frame rate. Should I be working at 29.97 then and having the music editor do a pull-down after submitting the AIF at 48K? Should I be working at 24fps? Should I ask for an output at 29.97? Any help would be much appreciated - we usually work at 29.97 so I'm not used to having to reset the frame rate in logic songs.

Thanks!

G5 dual 2.5GHz, Logic 7.2.1, Mac OS X (10.4.8)

Posted on Jun 4, 2007 4:10 PM

Reply
18 replies

Jun 6, 2007 2:21 PM in response to Randall Thomas

Hi Randall,

Glad you mentioned this... it can't always be taken as a given -- especially with indy filmmakers -- that the timecode burn they provide will be at the same rate as the fps of the movie! (I just went through that actually, where I got a 29.97 burn on a 23.98 movie. I was going crazy for a minute there!)

So let's add that to the list...

• timecode burn at the same rate as the movie

But to answer your question, yes, provided you get a movie that fits the criteria above, Logic's frame rate setting won't influence sync. The key is to simply disregard Logic's timecode counter, with the one exception of jockeying the bits value to place pops.

Now... to be really really really really really picky about that aspect of things...

If Logic's frame rate is set to 30 fps, the duration of a single bit is going to be smaller than that of a bit @ 24 fps. The difference is pretty miniscule:

1 bit @ 30 fps = .4167 milliseconds (that's less than 1/2 millisecond)
1 bit @ 24 fps = .5208 milliseconds (a tiny bit more than 1/2 millisecond)

The difference is .1041 millisecond. Probably not enough to worry about.

Anyway, back to your question. Let's say that I was scoring a scene of a 23.98 fps movie and Logic was set to 24 fps, just so that Logic's counter would be in the ballpark.

Start time for this example is 01:20:00:00 according to the t/c burn. And let's say that I finagled with Logic's SMPTE view offset so that Logic's t/c counter exactly matched at the beginning of the cue. Of course, at the end of the cue the t/c burn and Logic's t/c counter will no longer match. But that's OK because the basic principle is this: regardless of Logic's frame rate setting, that movie is going to play at its native frame rate. Logic's fps setting doesn't influence the playback speed of the movie. And since picture always plays back at its native speed, the picture's t/c burn becomes your absolute t/c reference.

I think I can say all of the above with certainty, per my tests (some described above, others I've done on my own) as well as the fact that on my current project, some of my Logic files were set to 24 and some to 29.97 with no sync errors reported by the editor.

Jun 6, 2007 2:25 PM in response to iSchwartz

BTW, on the subject of communicating information about 2-pops, here's a typical email message I'll sent to an editor after I post a cue up on their server. Note that I include the SMPTE time of the head pop in the filename:


======= C U E S # 13 - 18 =========

filename: Cues13to18-01 15_0522.aif
description: Music final 2-mix

=POPS=
head: 01:15:05:22
tail: 01:22:03:03


========clip coupon here=========

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

23.98 FPS work-around?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.