At least FCPX knows how to count – Premiere apparently does not

[Aindreas Gallagher]

Is anything bar avid ever going to work at this rate?

Reality – melting. I invoke Picard.

https://i0.kym-cdn.com/photos/images/original/000/001/582/picard-facepalm.jpg?1240934151

http://www.ogallchoir.net
promo producer/editor.grading/motion graphics

[Richard Cardonna]

What I can’t understand is why would this fellow say that PPro is unuseable, because of this issue? What about the thousands of projects done? are they unviewable?

BTW Aindreas

Startrek your my man. Check this scotish version:
https://www.youtube.com/watch?v=Khrpy4V0-U4

RC

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

[Shane Ross]

Unusable in the situation he needed it…which is a very common workflow. DSLR from a Canon camera with dual system sound, and timecode added with QTChange. That is a VERY common workflow.

Shane
Little Frog Post
Read my blog, Little Frog in High Def

[Richard Cardonna]

Got it would this be ttue with any dslr?

[Richard Cardonna]

Got it would this be ttue with any dslr?

[Jeremy Garchow]

Older DSLRs, yes. Newer DSLRs write actual tc.

[Oliver Peters]

[Jeremy Garchow] “Older DSLRs, yes. Newer DSLRs write actual tc.”

Well, only the newest Mark III. Not what most of us get to cut with. And, who’s to say that TC will be right or at least any different than that written by QtChange or Grinder? Not to mention, you still don’t really want to cut with native H264 footage – at least I don’t.

– Oliver

Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com

[Michael Phillips]

And many programs might actually prefer using 00:00:00:00 as a start for clips that don’t have timecode as some programs (as seen here with this example) interpret timecode in different ways. Some programs will use creation date and timestamp and write it out to HH:MM:SS:00 always ending in :00 while others also interpret a frame count. Depending on program and frame rate, you could be off by 29 frames. Not to mention proper calculations of 23.976*(100/1000) and 24*(1000/1001).

Another NLE when interpreting timecode does not take into account UTC, so if shooting before or daylight savings time and conforming afterwards will cause a 1 hour mismatch. Depending on schedules, applications used and such, a mix and match of any of these methods will cause headaches.

That is why 00:00:00:00 can actually be a nice method with no interpretation needed other than frame rate as to how that counts for sources that do not have the timecode embedded by the camera itself.

But I will add that having time of day interpreted by creation date and timestamp is handy for editors to have an additional piece of metadata to help them find a piece of media – like when a producer or director goes; “I think we shot something last Tuesday afternoon right after lunch”. That timecode (if interpreted) could be tracked in a separate timecode column for doing those types of searches with a shoot date.

Michael

Michael Phillips

[Franz Bieberkopf]

Richard,

It should be stated that the issue is with the way PPro reads data written by another piece of software – QTChange. If you don’t use that software, this isn’t going to affect you at all, regardless of what DSLR you use.

Franz.

[Simon Ubsdell]

[Franz Bieberkopf] “It should be stated that the issue is with the way PPro reads data written by another piece of software – QTChange. If you don’t use that software, this isn’t going to affect you at all, regardless of what DSLR you use.”

Yes, but strictly speaking there are two parts to the story only one of which is about QTChange.

This is what Adobe have to say about part 2:

Premiere Pro also has an issue with round-tripping start timecode with AAF files. This is our bug. We have fixed this bug in an internal build, and we are now testing it and determining how we will be able to address this issue in a future release of Premiere Pro.

I don’t imagine that many people need to round-trip with AAF but for those who do it’s worth being aware of this issue.

Simon Ubsdell
http://www.tokyo-uk.com