Same old timing issue

[Shane Ross]

[jack fox] “if actual play length stays the same,even though the timecode suggests it is longer, what is the harm?”

Well, if you are making a show for broadcast, it is a HUGE thing. Because broadcast needs precise timings. If you think your show is 44:30, when in fact it is 44:28, then you are two minutes short. Meaning that you didn’t meet network spec and your show will be rejected.

[jack fox] “Also my current suspicion as to the anomaly is not drop frame, but the difference between 23.976 and 23.98.”

23.98 is just a short rounded way of saying 23.976. Just rounding up to lose a number, that’s all.

Shane

GETTING ORGANIZED WITH FINAL CUT PRO DVD…don’t miss it.
Read my blog, Little Frog in High Def

[Jack Fox]

I think my show is 26:46 and it is, but my timecode (after conversion) suggests it is longer, which it is not. I do understand that 23.98 is short for 23.976, but I’m wondering if some software has rounded up. When I put a timecode track on the media before exporting I get the same timecode that is shown in the FCP timeline after export to quicktime movie, even though the frames and timecode detected on playing is displayed as longer (aproximately 6 frames). The difference between the original (40702) and the export (40708) on a 28:15:22 sequence is the same ratio as that of 23.976 and 23.98.

jmf

[John Fishback]

I read a thread recently that said AfterFX will export differently with settings of 23.976 or 23.98. I’ve not tested that myself. I’m pretty sure FCP’s 23.98 is 23.976.

John

MacPro 8-core 2.8GHz 8 GB RAM OS 10.5.5 QT7.5.5 Kona 3 Dual Cinema 23 ATI Radeon HD 3870
ATTO ExpressSAS R380 RAID Adapter, PDE Enclosure with 8-drive 6TB RAID 5
24″ TV-Logic Monitor
Final Cut Studio 2 (up to date)

Pro Tools HD w SYNC IO, Yamaha DM1000, Millennia Media HV-3C, Neumann U87, Schoeps Mk41 mics, Genelec Monitors, PrimaLT ISDN