Skip to main content
N
NMNHTV13
Participating Frequently
May 16, 2012
Question

Exporting Premiere Pro CS6 project fails to encode with certain assets in timeline

  • May 16, 2012
  • 1 reply
  • 30791 views

I just upgraded to Creative Cloud and enjoyed until it came time to render my first video.

The Media Encoder crashes no matter what I do!!!!!

I am rendering timelines with Canon MXF files and I need to transcode them to AVI so my friend can use them in his older version of Vegas.

I even tried encoding just a simple 15sec timeline with a few 5 second clips and that crashed too.

I NEVER had an issue with the previous version when i was using CS5.5.

What has changed???? I am very disaapointed whats the point of my editing a project if i can't ever output it????

I have several client project due and now I can't finish any of them. And your India based tech support doesn't even know what Adobe Media Encoder is!!!!!

    This topic has been closed for replies.

    1 reply

    Nariman Sodeifi
    Community Manager
    Nariman SodeifiCommunity Manager
    Community Manager
    May 16, 2012

    I'm sorry you are having this issue and that support didn't even know about AME.

    But I'm glad you found your way to this forum.

    Thought this is user to user forum, Adobe staff monitor and reply to forum posts often.

    Please provide the following info so we can help you with this issue.

    Are you on Mac or Windows (what version)?

    Are you exporting out of PPro or opening importing projects directly in AME and then exporting?

    Can you encode to any other format/codec?

    Can you import other files (not Canon MXF) and export to AVI?

    Is this AME CS6.0 or 6.0.1 (get this from Help > About) ?

    Are you exporting to a single presets or mulitple presets at same time?

    N
    NMNHTV13Author
    Participating Frequently
    May 17, 2012

    I am using Creative Cloud on a Window 7 PC

    Whether I export the timeline out of Premiere or use the Media Encoder it still crashes.

    The version 6.0.1.31

    For my work I record using either my Canon XF Series cameras which export the Canon MXF file wrapper.

    I also use a DataVideo digital recorder for recording multicam shoot when i'm using my field video switcher which outputs M2T files.

    I have inidividual timelines in different projects that have either MXF or M2T files in them, both types of timelines fail to render. (I also tried other formats and they failed as well. In fact my PC "bahhed" so much I thought I had sheep in the office.)

    As an experiment I imported just the MXF files into AME and they did successfully transcode to AVI. I then took those new AVI files into Premiere and tried to export to another format and that worked.

    However I don't see the point of having to export my MXF files to different format before I can even work with them. If that was the case I would've purchased a transcoder and continued to use the version of CS3 I had on my old XP machine which worked fine. I only upgraded because I couldn't use these newer HD files in the older version of Premiere.

    I am only exporting a single present going from Canon MXF to AVI DV Widescreen (My friend's other project files are SD so i'm down converintg thse files for him.)

    G
    genefama
    Known Participant
    May 22, 2012

    @PaulSahota92

    Please don't double-post.  This is the third topic in which you've posted the same info.  Please restrict your participation concerning this particular issue to your own thread here:

    Adobe Forums: How to render and export

    Any additional posts from you about the same issue in other topics will be deleted.

    Jeff


    Todd just gave a serious answer to a question that Jeff says should'nt have been asked.  Yet I doubt anyone is posting here for fun. I can make a list an arm long of problems I've had with Premiere Pro CS6 for Mac over the last few days and post it on five different discussion groups. None of the problems I've mentioned--which are only a sample of those I've experienced--have been addressed by Adobe or the Community Professionals. Let's hope the fixes Todd mentions make this version actually work. Then we won't have to waste our work-hours testing the bugs and posting multiple cries for help.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices