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

[Franz Bieberkopf]

Simon,

Yes, thanks for adding that. I just found this thread quite vague on what the actual issue is and whom it might affect; the talk of DSLR models exacerbated that.

Franz.

[David Mcgavran]

Hi Guys,

Haven’t posted to the cow before but read it quite often… Dennis and Todd seem to have this place covered 🙂

Just wanted to drop in and say hi.

Cheers

Dave

[Jim Giberti]

[Simon Ubsdell] “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.”

Yeah, this hardly a make or break PP issue.

[Simon Ubsdell]

[David McGavran] ” Hi Guys,

Haven’t posted to the cow before but read it quite often… Dennis and Todd seem to have this place covered 🙂

Just wanted to drop in and say hi.

Cheers

Dave”

Thought I’d just drop one last line correcting the title of this thread.

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

[Chris Harlan]

[Jim Giberti] “[Simon Ubsdell] “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.”

Yeah, this hardly a make or break PP issue.
“

Its hard for me to get worked up about this. I started with NLE’s back when they were highly specialized, and there weren’t enough users to do any kind of wide Beta testing. So, I just expect–rightly or wrongly–that there will be some bugs. And my mentality is generally to work around them. The important thing for me has always been the acknowledgment of issues and open communication about work-arounds and timetables for fixes.

[Jeremy Garchow]

[Oliver Peters] “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.
“

Just pointing it out.

The 1DX has tc as well. Seems to be somewhat of a trend!

[Mike Molenda]

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.

[Rafael Amador]

[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”
That workflow is OK for FC that do not manage Canon stuff natively. No so needed with PP.

In his long post the guy don’t even mention the kind of stuff he is dealing with.

In any COW forum the first thing we would have told him is: PLEASE SPECIFY YOUR SOURCE MATERIAL, SEQUENCE SETTING AND WORKFLOW.
rafael

http://www.nagavideo.com

[David Mcgavran]

I will grab a copy of 5DtoRGB and see what it is up to

Cheers

Dave

[Walter Soyka]

[David McGavran] “Hi Guys,Haven’t posted to the cow before but read it quite often… Dennis and Todd seem to have this place covered 🙂

Just wanted to drop in and say hi.

Cheers
Dave”

Just in case someone hasn’t read the linked Adobe response, I think it’s worth pointing out here that Dave McGavran is the Premiere Pro engineering manager.

Timecode is the sort of thing that needs to just work in an NLE, so seeing this incompatibility go from bug report to problem identification to a publicly announced solution for a future release in three days is really refreshing.

I made a remark here a few weeks ago about being interested in the vendors that were interested in me. This is the sort of thing I was talking about.

This didn’t months of hue and cry. It took a user’s bug report. Adobe recognized that timecode was important and treated it as such. Adobe recognized that communicating with users was important and treated it as such.

Dave, my thanks to you and the Premiere Pro team.

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