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

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