Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Issue with Speed/Time changes changing TC…

  • Issue with Speed/Time changes changing TC…

    Posted by Eric Johnson on October 22, 2013 at 5:13 pm

    Hi Everybody:

    Hoping you swell Premiere folk can help me out. I received a Premiere CC RED project for a Resolve finish.

    I first used the XML provided from Premiere and 90% of the timeline was totally off the mark.

    I then tried running the XML through FCP7, tried an EDL and tried an AAF, all of which resulted in the same exact timelines.

    So I switched form looking at what Resolve was doing wrong and started looking at Premiere. I am not a savvy Premiere user, but I found that every time a clip was retimed the TC appeared to change also. I don’t mean in the standard “fit to fill” lose/gain a frame do to the math of retiming. I mean TC offset.

    Normally this would be no big deal, since most timelines have few enough speed changes to be an issue. On this shoot though, they shot almost exclusively @ 120, so they always had the slow-mo. So almost every single shot was a speed effect.

    Here is a screen grab showing the type of offset, which happens to not be consistent, I am observing.
    6662_2ndcliptcmismatch.png.zip

    Has anyone seen this before? I would really like to give these guys a solution for future work, we had to work off of a high res export for this one…

    eric b johnson
    online editor | colorist | workflow
    https://vimeo.com/39073239

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

    This happens because the functionality/content marked as “Vimeo framework” 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.

    Eric Johnson replied 12 years, 6 months ago 1 Member · 0 Replies
  • 0 Replies

Sorry, there were no replies found.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy