4 Replies Latest reply: Nov 22, 2014 9:48 PM by Dslyecxi RSS

    Project Manager fails to trim after new "Consolidate & Transcode" method

    Dslyecxi

      Greetings,

       

      I use Premiere to create trailers and other material for a gaming studio. For recording, I use dxtory ( http://exkode.com/dxtory-features-en.html ), with Premiere/AE used to edit the footage, and AME for rendering. Any given project may consist of several hundred GB worth of source footage. When done with a given project, historically I've used Premiere's "trim" method from the project manager to store trimmed copies of the footage - as it's intended for. This can turn a project with 400GB of source down to a trimmed one that's only 80GB or so. This has worked fine in the past, but because of the recent change to the new "Consolidate & Transcode" feature, this fails in the current Premiere.

       

      I've created a full repro of this for anyone who would like to try it.

       

      The repro project: https://dl.dropboxusercontent.com/u/263501/misc/PremiereRepro/Copied_transcode_repro.7z

       

      Using Project Manager, I select the following options:

      https://dl.dropboxusercontent.com/u/263501/Misc/PremiereRepro/pp_transcode_2.png

       

      This should result in a ~9.9 MB avi that is 15 frames from the larger video, of the character panning the view slightly to the right.

       

      Instead, I get the following message after completion:

      https://dl.dropboxusercontent.com/u/263501/Misc/PremiereRepro/pp_transcode_1.png

       

      Looking at the directory for this new "trimmed" project, the filesize is the same as the source footage and no trimming has actually occurred.

       

      The event log says the same:

      https://dl.dropboxusercontent.com/u/263501/Misc/PremiereRepro/pp_transcode_3.png

       

      This method worked 100% reliably prior to the new "Consolidate & Transcode" feature. It seems to be entirely broken in the current one, at least for my purposes. Am I overlooking something, or is this a bug? I'm currently having to install an earlier version of Premiere to try to work around this, but obviously that's not the desired solution.