[Rafael Amador] "That workflow is OK for FC that do not manage Canon stuff natively. No so needed with PP."
Giving non-timecoded sources proper TC and reel info is not necessary if you're going to stay entirely within any individual app -- but it's critical for conform. I don't see a problem with the workflow in general.
[Rafael Amador] "For years, the "QTChanger" developer (Vouke Valh) has proved to be one of the guys with better knowledge on TC issues around the COW forums. Just to say that I doubt very much that he has made the newbie mistake of apply 23,98fps instead of 23,976fps to generate TC."
I don't want to speculate because I don't know all the specifics, but if the Adobe folks say that QtChange's timecode output could be improved and that they have a patch in place for a future release that works around the issue, I believe them. (I also like the approach of taking ownership and "fixing" it in Premiere anyway, even if another developer's code is creating the problem.)
Also, this bug isn't happening with all 23.976 media with timecode -- just the timecode output from a few apps. I just tried this to see for myself. Export a 23.976 clip starting at 1:00:00 from FCP. Import it into Premiere Pro, and the timecode is correct. Restripe the TC on that clip with QtChange, and Premiere Pro gets 59:56:09.
Walter Soyka
Principal & Designer at
Keen Live
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
RenderBreak Blog - What I'm thinking when my workstation's thinking
Creative Cow Forum Host: Live & Stage Events
