Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Premiere CC 2014.1 Project Manager

  • Premiere CC 2014.1 Project Manager

    Posted by Michael Ron on October 28, 2014 at 12:01 pm

    Hey,
    I work in a post-production facility and we are having some problems with the Project Manager.
    The latest update, where they redesigned the Project Manager tool solved the previous issues (long GOP files not being trimmed), but seems to have also created a new one – A lot of our editors are getting the following general error message when trying to use the Project Manager’s consolidate and transcode:

    After doing some testing, it seems like the problem has to do with sound – sequences with mixed audio information (i.e. 48KHz and 44.1KHz files) can not be trimmed via project manager. after converting all audio files to 48KHz the problem is usually solved.
    This is an annoying issue, but one I figured we can work around as long as we know where the problem is coming from.

    However, today I ran into a project that has all 48KHz 16bit AIFF audio and is still showing the same error when trying to export via project manager.
    The strange thing is that when trying to delete the audio (meaning, using the project manager on video only) it works fine, which is consistent with the above mentioned audio issue.. But I am 100% positive that all the audio files on the sequence are 48KHz 16bit. I did notice that some of them are 6-channels audio and some are 4.. Don’t know if that makes any difference at all.
    For now we’ve migrated the project to AE using an XML, but I would still like to understand this issue better so that I can help solve it next time around.

    We are working on Mac Pros with either MXFs or mov ProRes 422 LT – usually not in the same sequence; and our CC applications are updated to the latest versions.
    The settings we are using for the Project Manager are Consolidate and transcode, to quicktime ProRes 422, matching individual clips.

    If anyone has any info on this issue or knows of any other reason this might be happening, I would love to hear it.

    Thanks!
    Michael

    Andy Field replied 10 years, 8 months ago 5 Members · 5 Replies
  • 5 Replies
  • Peter Garaway

    October 28, 2014 at 5:07 pm

    Hi Michael,

    Sorry for the troubles. There are a few known issues that we’re aware of that can cause this error,

    – Transcoding to a drive with insufficient space

    – Sequences with Merged Clips

    – Sequences with audio only from an A/V clip (This appears to be limited to ProRes presets).

    All three of these cases would result in unknown error in 8.1. We’re working on fixes for these issues now.

    Peter Garaway
    Adobe
    Premiere Pro

  • Michael Ron

    October 29, 2014 at 7:49 am

    OK, so the issue must be the audio only from an A/V clip.. We tend to do that a lot, using syncs from certain clips without necessarily using the video.
    But thanks for the answer, and hopefully this will be solved soon in a future update.

    I’d also like to know for future reference, is there a place where users can view all currently known issues with Adobe softwares?
    It will help deal with the editors frustration, as well as our own (IT team), since every update we have to pretty much guess what the issues are, consuming valuable editing-time from our video editors and AE artists.

  • Colin Crockatt

    February 9, 2015 at 4:15 pm

    Any fix for this yet? I’m having the exact same issue probably for the same reason (audio only used from video clip. But whatever the reason I desperately need the project manager feature to work reliably as I work for a company that is regularly passing projects between different editors and minimizing project size is really important for us.

    I am running CC 2014 up to date on the latest mac book pro:

    2.6Ghz Intel Core i7
    16 GB 1600MHz DDR3
    OSX 10.9.5

    Thanks!

  • Marcello Mazzilli

    February 15, 2015 at 1:44 pm

    The whole PROJECT TRIM part seems to be full of bugs… A TRIM PROJECT operation might result in success but then opening the trimmed project you will find total crap.. with things moving around and the trimmed clips not being the ones you wanted (trimmed in different points or so)

    siRoma di Marcello Mazzilli
    Corporate video productions in Italy
    http://www.siroma.com

  • Andy Field

    September 2, 2015 at 7:27 pm

    Adobe software folks – it’s now a year since the original post – and it’s still not fixed – tried to consolidate a problem with mixed audio bit rates – the dreaded unknown error is back

    This pretty much makes the consolidate function unusable without a lot of extra work

    Please fix this

    Andy Field
    FieldVision Productions
    N. Bethesda, Maryland 20852

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