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

[Steve Connor]

Interesting read, thanks for posting

Steve Connor
“FCPX Professional”
Adrenalin Television

[Brian Mulligan]

And Paul Harvey’s… The rest of the story…..

adobe.ly/GSzXmE

Brian Mulligan
Senior Editor – Autodesk Smoke
WTHR-TV Indianapolis,IN, USA
Twitter: @bkmeditor

[David Cherniack]

Adobe’s response:

https://blogs.adobe.com/premiereprotraining/2012/03/a-couple-of-timecode-issues.html

David
AllinOneFilms.com

[Michael Phillips]

A description of the actual bug and circumstances in which it arises would be good to know in case there is a workaround that can be used in the meantime. God knows there are similar issues in every software package.

Michael

Michael Phillips

[Simon Ubsdell]

[David Cherniack] “Adobe’s response:

https://blogs.adobe.com/premiereprotraining/2012/03/a-couple-of-timecode-iss...”

Hmmmmm, yeah. I’d say if you read the full details of what he wrote Jeffery managed to shame them into this concession though, wouldn’t you!??

Still at least they’ve responded … sort of … wouldn’t get that from Apple in a million years!

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

[David Cherniack]

[Michael Phillips] “A description of the actual bug and circumstances in which it arises would be good to know in case there is a workaround that can be used in the meantime. God knows there are similar issues in every software package.”

I think David McGavran explains it succinctly. “QTChange uses a value for calculating frame rate and timecode of 23.98 (2398/100) instead of the expected 23.976 (23976/1000 or 24000/1001)”.

Other software packages that read QTChange files correctly must be aware of the 23.98 time base and reinterpret it to 23.976.

As for workarounds I haven’t tried it but there is a way to batch change the timebase of clips in PrPro.

David
AllinOneFilms.com

[David Cherniack]

[Simon Ubsdell] “Hmmmmm, yeah. I’d say if you read the full details of what he wrote Jeffery managed to shame them into this concession though, wouldn’t you!??”

Shamed? Far from it. Adobe takes its shortcomings seriously. David McGavran has gone to extraordinary lengths to help out individual users having issues with their software. This is just another instance. If anything, reading Jeffery’s blogs on the issue, I’d say he’d be the last person on Earth I’d want to help out. Various four letter descriptors come to my mind. David, on the other hand, is a complete gentleman.

David
AllinOneFilms.com

[Frank Gothmann]

Here is an official response from Adobe, one day after a single blog-post regarding a single bug.
When others report total project and media corruption in X, Apple’s response is zero.
Speaks volumes.

[Michael Phillips]

So the issue is when using third party software to create metadata and essence outside of PPro with a different interpretation that deviates from standard calculations? Seems to me that Adobe did a great good job of reaching out, identifying the source of the problem (outside of PPro) and will be addressed in a future release. He also reached out to the author of the program to work a solution at the source.

And what good is there is trying to “shame” someone? We all work under deadlines, priorities, compressed schedules, with variables we can or cannot control. You can read the release notes of known issues with any software release and go on some blog rant about “how could they release this with that issue?” all the time. More helpful would be to find out why the original timestamps needed to be re-adjusted in third party software (which then caused the timecode rate issue) in the first place and see if there is a better solution to be had. That would be a complete description of the problem at hand, and potentially a better solution.

Michael

Michael Phillips

[Simon Ubsdell]

[David Cherniack] “If anything, reading Jeffery’s blogs on the issue, I’d say he’d be the last person on Earth I’d want to help out.”

Hey, I only posted this because I thought his rant was amusingly written – and I guess four letter words don’t offend me as much as perhaps they ought to. Sorry if you didn’t like it.

And yes, if we’re being very serious about this, Adobe’s response was ultimately very good indeed and they’re probably one of the few companies on earth who would respond as well as this.

Apologies if anybody has taken offence to this. But don’t anybody tell me you haven’t ranted inappropriately from time to time 😉

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