Re: At least FCPX knows how to count - Premiere apparently does not

I ran into some similar issues recently while screwing around with 5DtoRGB - which, like QTchange, writes TC from the camera metadata to transcodes. Proper TC for the first frame of the clip should have been 22:04:43:00. Premiere read it as 22:03:23:14, a difference of one minute(!), nineteen seconds, ten frames.

So I decided to test this out. Using the Canon E1 plugin for FCP7 Log & Transfer, which also generates TC based on the camera metadata, I created a ProRes Quicktime and imported that from my Capture Scratch into Premiere. Start TC read as 22:04:43:00. No problems. I also generated ProRes QTs from the same footage using AME and MPEG Streamclip, and brought in the straight h.264 from the card as a control. Picked an arbitrary frame, 00:00:09:09 (22:04:52:09 in the E1 transcode), and everything matched up across the clips.

So it seems like the problem is a disconnect with how Premiere treats 23.976 TC generated by different sources, such as QTchange or 5DtoRGB? But this is something that Avid and FCP7 seem to be able to account for...

It's distressing, to say the least, given how widespread the use of DSLRs (particularly the Canons) shooting 24p has become. The wacky side-effects that come from merging second system audio certainly don't help anything, either.