Premiere Pro CS6 stops during export (Adobe Media Encoder also)

Hello,
I have been using the Adobe CS6 Video Bundle for a few years now and suddenly I've been having an issue with exporting my timelines in an H.264 format.
Any H.264 video that I try to export that exceeds approximately 900MB stops in the middle of the export and gives me this message:
My video bundle has been doing some odd things lately and this is possibly the most annoying. My computer is a custom built workstation so it's not like my computer can't handle it.
-Intel i7 4.2ghz overclocked CPU
-32GB RAM
-Adobe Video Bundle installed in 120GB SSD
Any help or advice would be greatly appreciated.
Thanks,
Nate

Thank you for your response.
-I tried exporting an AVI and the file exported succesfully but with a warning "Adobe Media Encoder Could not write XMP data in output file." The file plays fine though and is over 5.5GB. So that's odd that my h.264 which is under 1GB won't fully export.
-Yes, the same thing happens when exporting directly from PrPro instead of using AME.
-In this project I am using NO Dynamic Links.
-I have not installed any codec libraries.
-I do not use 3rd party plug-ins.
-My destination drive has several terabytes.
Thanks,
Nate

Similar Messages

  • Premiere Pro CC not queuing exports into Media Encoder CC

    I try to make this simple...
    standard export from PP CC to ME CC
    File -> export -> media, then hit queue.
    Media encoder opens and just sits there. Left it for hours to see if anything would ever happen, and nothing ever did.
    I've restarted the programs and machine dozens of times and that does nothing.
    I can still export from PP CC.
    I have no CS6 products left on my box.
    I also tried to open the project from Media Encoder and load the sequence that way with no luck.
    Thanks for the help!
    On a Mac Pro
    Premiere version 7.0.1
    Media Encoder version 7.0.1.58
    Adobe Creative Cloud for Teams Member (so it's licenced and updated to the fullest)

    rforgaard wrote:
    I had this exact same problem, and I figured out the solution in my case.  I know the original problem report is ancient, but there are recent replies, so I am adding my solution here.  I spent untold hours figuring this out, so hopefully this will save someone else some time.
    There can be other causes to this problem, I'm sure.  I'm just telling you about what fixed this problem for me.
    Just to clarify, here is the symptom: Running Windows 8.1.  Standard export from Premiere Pro CC 2014.2 to Media Encoder CC 2014.2, using File -> Export -> click Queue.  Media Encoder opens and just sits there.  Premiere Pro is hung and has to be forcibly terminated.
    I spent countless hours on this.  I thought I had messed up my computer's configuration somehow, so (believe it or not) I re-installed Windows on a freshly formatted hard disk, re-installed Creative Suite, same problem.  (I can't believe I wasted all that time; I feel like a dummy.)
    I finally narrowed it down to a very simple test case with a very tiny one-clip sequence that is less than one second long.  Same problem.
    It turned out to be a problem in the Premiere Pro project file itself.  I suspect that a small file corruption somehow snuck into the project file, that was completely invisible.  In that clip in my project, if I removed the "Vocal Enhancer" effect, the problem with exporting to Media Encoder went away.  If I then re-added the very same "Vocal Enhancer" effect, the problem was still gone.  It must be some small corruption in the ".prproj" file that went away when I removed the "Vocal Enhancer" effect and re-added it again.
    NOTE: I DON'T think that there is some kind of bug with the "Vocal Enhancer" effect.  I don't think this problem has anything to do with "Vocal Enhancer" per se.  It is just some kind of small generic corruption in the project file.  When Premiere Pro tries to export that sequence to Media Encoder, the problem occurs.  It was just a coincidence in my case that removing and re-adding the "Vocal Enhancer" effect made the problem go away.
    BOTTOM LINE: If you find that you have this bug where Premiere Pro hangs when exporting to the Media Encoder queue, try the following: Create a brand new project with a single clip in it, and export it to the Media Encoder queue.  If that works, you know that it is not a problem with Premiere Pro in general; it's a problem in your specific project file.  Once you've made this determination, make a copy of your original project file, and remove clips from the project until the problem goes away.  Keep narrowing it down until you find the clip(s) that are the issue.  Then, try removing and re-adding any effects on those clips, or even removing and re-adding the clips themselves, to fix the problem.  Eventually, by removing and re-adding a specific effect or clip to your project, the problem will vanish (hopefully).  It's just a matter of narrowing down which half of your project the problem occurs in, then which half of that half, etc., until you have it narrowed down to one clip or group of clips that need to be removed and re-added.
    Having said all this, it is a bug that ideally should be fixed so someone else doesn't spend untold hours trying to figure out the problem.  To that end, I create a tiny ZIP file that just has project file and the single media clip needed to reproduce the problem, along with a small description "READ ME.txt" file that explains the very simple steps to reproduce the problem.  I have submitted this as a bug report to Adobe using their official online bug report form at www.adobe.com/cfusion/mmform/index.cfm?name=wishform along with a link to the ZIP file so they can download and reproduce the problem.
    If anyone else is curious about reproducing this same bug, you can also download the small ZIP file if you want to.  I guarantee it doesn't have any viruses or anything - it's just two small files to reproduce the problem.  To download the ZIP file containing that project file, media file, and "READ ME.txt" file, you can get it at www.forgaard.com/files/PremiereProBug.zip.
    I hope this saves someone some time.  This one sucked up a zillion hours of me chasing apparitions.
    I was having a problem with exporting a sequence to AME.  PPro would freeze and I would have to force the program to close.  This was on a project where I was just running out a bunch of interview clips for the director to look at.  One of them had a audio effect (DeHummer) on it, and it was the one that was giving me troubles.  I selected the audio and right clicked then "Render and Replace" then it would export to AME with no issue.  Thank you for your well written response to this thread.  While it may not have fixed the OP's issue, it did help with mine....
    Thanks,
    Phil

  • Premiere Pro CS6 extreme project bloating and Media Encoder

    Hi there,
    I'm interested in hearing if others are having this issue and if there's a fix.  I first noticed this bug in CS5 and it hasn't changed in CS6.0.1.  An editor I'm working with recently discovered the problem at the expense of a project being usable the day before clients are coming in to work on cuts.
    Here's what's happening: we have a 20MB commercial project, no warp stabilizer in play, no frequent "save as..." commands being used, both of which seem to contribute to project bloating based on some online research.  I've been using Premiere as a finishing timeline since CS5 and noticed back then, when we were making some settings in Media Encoder, that when you click and drag sequences into ME instead of using the "Add Premiere Pro Sequence" menu option, the Premiere project file size quickly increases and saves and autosaves start taking several minutes to complete.
    We've been using the "Add Premiere Pro Sequence" method to send things to ME on this project but the editor was getting impatient the amount of time it was taking for ME to load the project and get to the point where he could pick which sequences he wanted to encode.  He did a bit of research and found the click and drag method to be faster.  After a handful of times using this method, the project size went from 20MB to 3.71GB.  Our autosave folder is set keep 5 versions of the project and you can see the project size doubling from 477MB to 840MB to 1.6GB.
    I was able to import the 477MB project into a new project and save it out at its original size of 20MB.  However, this meant that we lost about 90 minutes worth of work.  I tried to import the 3.71GB file overnight and it had made no progress when I came in this AM. 
    Reading online, I found that the "Save As..." command had previously caused some kind of duplication of preview file links in the project code.  I opened up our 20MB project in TextWrangler and compared it to the 840MB project's lines of code.  The 20MB project had 400k lines and the 840MB project had about a million.  The difference appeared to stem from links to Preview files.  I wanted to try to clear those out to see if I could get the project size down but, probably because of the file size, TextWrangler crashed.
    Is there any way to clean out the bloat from these projects without importing into a new project?  Also, are there settings in Media Encoder or Premiere that will prevent the bloat from happening when using the click-drag method of getting sequences into ME?  We're using the "Use Preview Files" option, which greatly speeds up the compression in ME, but might be contributing to the issue.
    Here are the machine specs:
    Mac Pro 2.66 GHz 12-core
    16GB RAM
    NVidia Quadro 4000
    ATTO Fibrechannel card
    Blackmagic Design Decklink Extreme 2
    Thanks in advance for any thoughts. 
    Best,
    Jon

    Thank you for your response.
    -I tried exporting an AVI and the file exported succesfully but with a warning "Adobe Media Encoder Could not write XMP data in output file." The file plays fine though and is over 5.5GB. So that's odd that my h.264 which is under 1GB won't fully export.
    -Yes, the same thing happens when exporting directly from PrPro instead of using AME.
    -In this project I am using NO Dynamic Links.
    -I have not installed any codec libraries.
    -I do not use 3rd party plug-ins.
    -My destination drive has several terabytes.
    Thanks,
    Nate

  • Premiere Pro CS5 fails to export to Media Encoder CS5

    Hello all,
    I'm working with Adobe Premiere Pro CS5 Version 5.0.3 on two 64 bit Windows 7 computer systems (laptop and desktop). On my laptop everything works fine and has for some time. We recently installed CS5 on this desktop (new computer). Using the same settings that I use on my laptop, I can encode video by going to File->Export->Media and selecting Export. However, if I chose to Queue the media into Adobe Media Encoder version 5.0.1 it fails to work. Media Encoder opens properly, and the progress bar for exporting the media goes to 100% and disappears like it should. At that point no file appears in the queue. Any help as to what is happening? I'm not receving any error messages that could give me a hint...
    Thanks!

    Hi Bill,
    Thanks for the response. Due to the intermittent nature of this problem I wanted to test more thorougly and can confirm that the files are PCM at 44.1Khz. The error message is, "The file format is not supported", and IIRC the files opened fine in Flash (which will be explained later). Audacity successfully opens the files.
    I have resolved the issue and discovered exactly where the 'fault' lies.
    Adobe determines the file type by it's filename - rather than using methods in Cocoa library or by looking at the RIFF header. My files are titled, "yyyy.mm.ddName" (Reason/Record does not automatically add the extension in this case), however some files were titled "yyyy-mm-ddName.aif". The former (with periods) would result in the filename extension being truncated from the file's name, but the file 'Kind' is still identified as an "Aif C Audio".
    On OSX, any file with an unknown extension should also have it's file type checked using the Cocoa Library since the OS does keep record of the file type that can (and should) be used by applications.
    A fix to this in the code is that under OSX, the Cocoa Library file methods should also consult the file type - given that many programs on OSX may happily save without explicitly using an extension in the file name.\
    Flash (which didn't yield this problem) may have additional code to ascertain the filetype by seeing if it recognizes the data (given that Flash interracts with streammed data that would not have a file extension).

  • Premiere Pro CC - error on export through media encoder.

    Hi,
    I recently upgraded to Premiere pro CC.  Everytime I try to export through media encoder the exports errors right at the end of the render.
    It keeps prompting . Error - Disk Full.  Thng is that I have 339 gig Available on the destination drive.
    - I Cleared the disk cash.
    - all the footage is Canon 5d Mk3 footage 1920x1080
    - I've tried rendering H264 and mpeg2 footage .... It all errors at 99% stage
    screen shot....
    - adobe ... please help,
    Duncan.

    OK, So to be more specific it's hanging when I send it to Media Encoder Queue. I was just able to just do a direct export.
    I found the article on permissions and that was not the issue.
    I've made no changes to hardware and have done three projects with the same codecs, type footage, duration (1 hour range) with no problems.

  • Premiere Pro CS6 freezes during loading

    Having used thsi programm several times successfully all of the sudden since today, after a few seconds of loading process of Premiere Pro CS6, loading process always starts freezzing at loading stage : "loading ExporterQuickTimeHost.bundle" (Mac OS). Deinstallation and reinstallation didn't help.
    Can someone help me?

    The following is the crash report (extract) of Adobe Premiere Pro CS6. Maybe some of new has some system knowledge.
    Process:         Adobe Premiere Pro CS6
    Path:            /Applications/Adobe Premiere Pro CS6/Adobe Premiere Pro CS6.app/Contents/MacOS/Adobe Premiere Pro CS6
    Identifier:      com.adobe.AdobePremierePro
    Version:         6.0.0 (6.0.0)
    Code Type:       X86-64 (Native)
    Parent Process:  launchd
    Date/Time:       2012-10-03 22:54:32.002 +0200
    OS Version:      Mac OS X 10.6.8 (10K549)
    Report Version:  6
    Interval Since Last Report:          -6877 sec
    Per-App Interval Since Last Report:  457 sec
    Per-App Crashes Since Last Report:   3
    Anonymous UUID:                      C1440D44-6720-4316-9D5B-DA9C509698E4
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
    0   com.adobe.premiere.frontend       0x000000010c6c8e38 FE::Application::AttemptPanicProjectSave() + 18
    1   com.adobe.premiere.frontend       0x000000010c7207cc UnixInterruptSignal(int) + 44
    2   libSystem.B.dylib                 0x00007fff83bf01ba _sigtramp + 26
    3   libSystem.B.dylib                 0x00007fff83b8fdc2 semaphore_wait_signal_trap + 10
    4   libSystem.B.dylib                 0x00007fff83b9540d pthread_mutex_lock + 469
    5   com.adobe.QT32Client.framework    0x000000010d0895d6 ASL::SingletonSupport<ASL::InterfaceRef<QT32Client::QT32Client, QT32Client::IQT32Client> >::CreateClassRef() + 54
    6   com.adobe.QT32Client.framework    0x000000010d05f747 QT32Client::Create() + 23
    7   ...rterQuickTimeHost.framework    0x0000000133e1b01e ExporterQuickTimeHost::OnStartup(exportStdParms, exExporterInfoRec) + 28
    8   ...rterQuickTimeHost.framework    0x0000000133e1e6fe PrExporterModule::ExportEntry(int, exportStdParms, void, void*) + 68
    9   ...rterQuickTimeHost.framework    0x0000000133e1e4e1 xSDKExport + 81
    10  ...dobe.ExporterHost.framework    0x00000001047f71b3 ML::CallExporterModuleGuarded(int ()(int, exportStdParms, void, void), int, exportStdParms, void, void*, std::basic_string const&) + 131
    11  ...dobe.ExporterHost.framework    0x00000001047f7483 ML::ExporterPluginModule::CallExportModule(int, void, void) + 405
    12  ...dobe.ExporterHost.framework    0x00000001047f6fe3 ML::ExporterPluginModule::StartupFromDisk(unsigned int, bool) + 353
    13  ...dobe.ExporterHost.framework    0x00000001047c162c ML::ExporterModuleFactory::CreateUnknown(ASL::InterfaceRef&) + 308

  • Adobe Premiere Pro CS6 stopped working

    I wonder how Adobe Premiere Pro CS6 solve stopped working

    Provide the crash info and more details about your project.
    Working with your Operating System’s Tools | Mylenium's Error Code Database
    Mylenium

  • Adobe Premiere Pro CS6, format for exporting video to web.

    On the Adobe Premiere Pro CS5.5 I used the format "H.264" and preset "Apple Ipad 400x224, 16x9, 29.97, 400kbps." That preset isn't available in the Adobe Premiere Pro CS6 edition. What would you recommend that would be comparable and good for exporting a one-hour video for use on the web (Vimeo, to be specific)?

    You're in the wrong forum.

  • Adobe premiere pro CS6 stopped working July 10th, 2014

    Adobe Premiere pro CS6 stopper working yesterday,
    not only on my computer, my colleagues also have the same problem, I get a windows error and the program closes ...

    This was Microsoft patch week... did you install Windows updates?
    •What is your exact brand/model graphics adapter (ATI or nVidia or ???)
    •What is your exact graphics adapter driver version?
    •Have you gone to the vendor web site to check for a newer driver?
    •For Windows, do NOT rely on Windows Update to have current driver information
    •-you need to go direct to the vendor web site and check updates for yourself
    •ATI Driver Autodetect http://support.amd.com/en-us/download/auto-detect-tool
    •nVidia Driver Downloads http://www.nvidia.com/Download/index.aspx?lang=en-us

  • Premiere Pro CS6 Render and Export Screen Glitch and Freeze

    I use Premiere Pro CS6 on a 2012 Macbook Retina display - 16GB RAM, 751GB Flash Storage, NVIDIA GeForce 650m Graphics Card, 2 External 4TB hardrives for scratch disks, Thunderbolt connection. When I try to render and export videos I often get a graphical glitch like in the pic shown below and my computer freezes. It happens very often, especially when there are a lot of effects in the videos - I use the GenArts Sapphire plugin often.
    This has been going on basically since I bought my Macbook 2 years ago, but it is starting to become more and more common -  considering this was the most expensive Macbook Pro you could buy I am very annoyed with this - even on some videos where I have applied no plugin effects or any color correction it happens, especially when trying to export videos.
    Any help on this issue would be appreciated.

    I am having precisely the same problem as bricklaneeditor, and have exactly the same setup: MBP early 2011, 16GB RAM, 512 GB SSD,
    30" ACD, Mac OS 10.7.4 , PPro 6.0.1
    Indeed, a restart of Premiere Pro always fixes the problem -- for a while.  I've also seen similar behavior in Media Composer 6.0.1 once or twice so am wondering whether it's an issue with this machine/OS, as the playback software architectures are so different on those two NLE's. 
    I should also mention that the problem is not isolated to any particular file format -- have seen it with timelines containing 7D footage, HDV and ProRes files.  
    I strongly suspect some sort of problem on either Apple's or Adobe's end with the GPU in this machine, as it is ATI and not Nvidia -- and is, as far as I know, the only non-CUDA GPU, at least on the Mac side, certified to work with the CS6 Mercury Playback Engine.   
    Also wondering whether an over-the-top or a clean install of Mountain Lion might shake things up enough to make a difference.  (Otherwise I'm in no big hurry to upgrade my OS.)  Is anyone seeing this problem with PPro under 10.8?  Might be worth installing 10.8 over an external HDD clone of the System drive and booting temporarily from the clone just to see if the problem persists in Premiere.  
    Anyone have any thoughts on these possibilities? 

  • Premiere Pro CS6 stopped working, for one user profile

    So Premiere Pro CS6 wouldn't open today. Opened fine yesterday, and the days before that. The program didn't crash yesterday or close improperly. I just get the logo splash screen, but I don't see the usual text stream of applications starting up on it. After a long time I get a Windows message saying it can't open the program.
    - I used Bridge to update to the latest version. No help.
    - I made sure Quicktime was updated.
    - I cleared the preferences by moving the whole My Documents\Adobe\Premiere Pro\6.0 folder somewhere else (as a backup). Next time I tried starting the program it created a new \6.0 folder but that's as far as it went.
    - I deleted AppData\Roaming\Adobe\Adobe Premiere Pro. Starting the program recreated the folder, made a Trace Database file but only put two entries in it:
         DynamicLink     1     5
         FE.WinInit.LocPlugins 1     5
    And then it stops there. No other files created.
    - Tried starting the program holding the Shift Key, and again with the Alt key, and again with both. No change.
    - Rebooted after every change.
    I tried logging out as the video user account and logging in with my personal account, and then Premier Pro opened just fine.
    Problem is, I need it to work on the video user account because it was created specifically for our video editing PC. Our company logins also tie into our email and other programs. This one was created specifically so more than one person could share Premiere Pro settings and resources, and there was a battle with our IT to get it because they despise generic accounts.
    I've seen other threads here mentioning startup problems but the solutions listed there don't work for me. Manually trashing the \6.0 folder didn't help. I don't have a .pref file or Preferences folder other than the \6.0 one. I haven't made any changes to the PC. The video drivers must be OK or it wouldn't start under the other user account. How do I fix this one?

    This was Microsoft patch week... did you install Windows updates?
    •What is your exact brand/model graphics adapter (ATI or nVidia or ???)
    •What is your exact graphics adapter driver version?
    •Have you gone to the vendor web site to check for a newer driver?
    •For Windows, do NOT rely on Windows Update to have current driver information
    •-you need to go direct to the vendor web site and check updates for yourself
    •ATI Driver Autodetect http://support.amd.com/en-us/download/auto-detect-tool
    •nVidia Driver Downloads http://www.nvidia.com/Download/index.aspx?lang=en-us

  • Why is Premiere Pro CS6 crashing during render at 50% completion?

    I am running Premiere Pro CS6 on MacBook Pro, flash drives. The Mac is brand new. Nothing else is running. No other non-factory programs are installed.
    Regardless of what I do, during export to any output type, Premiere crashes when it's rendered to 50%.  I take the same project and only render part; crash at 50%. I try another new project, with nothing but a single video file, crash at 50%.
    <frustration>I am about to run to Final Cut, and I really don't want to. I am losing money and time that I don't have.</frustration>
    Any feedback would be majorly appreciated.
    Thanks,
    Aaron

    ...MacBook Pro, flash drives....I take the same project and only render part; crash at 50%. I try another new project, with nothing but a single video file, crash at 50%.
    Make sure you are not running out of available space
    on your target drive for the export.

  • Premiere Pro CS6 stopped loading correctly - will not load new or existing projects?

    It's been about a month since was last editing a project succesfully. When I try to load a new or existing projecet, I get the error message "Adobe premiere pro has stopped working. Windows is searching for a solution..." But there is no solution given, it just closes. I have tried updating my NVIDIA driver with no luck. I am running on Windows 8.1 64 bit. Anyone else have a similar problem?

    Thanks for your reply, GautamBahl.
    So I did have two graphics cards running, disabled the onboard one and still did not work.
    I created a new admin account on my PC, and I am able to create a new project in Premiere now (am not able to while signed into my original account). Since all of my files and settings are on my original Windows account,  I would like to get it working on that account. Do my findings give any indication as to how to fix the problem so that I am able to run Premiere signed in to my normal user account?
    I appreciate the feedback!

  • Adobe Premiere CS3 crash with Export Adobe Media Encoder

    Hello,
    I having a problem with Premiere. When I want to export my sequence with Adobe Media Encoder, Premiere crash. I tested the solution proposed by this link: http://kb2.adobe.com/cps/404/kb404804.html but no success ...
    My computer configuration:
    - XP 64
    - Dual Xeon
    Thank you,
    Kevin

    A link with many ideas about computer setup http://forums.adobe.com/thread/436215?tstart=0
    Computer DETAILS are always good to provide
    Work through all of the steps (ideas) listed at http://ppro.wikia.com/wiki/Troubleshooting
    If your problem isn't fixed after you follow all of the steps, report back with the DETAILS asked for in the questions at the end of the troubleshooting link

  • Premiere crashes when trying to export with Media Encoder via Dynamic-Link

    I work with clips from a networkdrive and I think the problems relates to this fact. My User-Account is an Admin-Account. I don't have any other Accounts. I also set Premiere, Adobe Media Encoder and every dynaimclinkmanager and -mediasever I could find to "run as administrator". Importing Clips in the timeline and work with them works well.
    Setting Adobe Media Encoder as "run as admin" solved the issue in the past, that it sometimes didn't render clips out sent from premiere via dynmiclink saying that it couldn't find specific files (which were instances of the actual premiere-project in the tempfolder), thogh these files were actually there.
    Thanks for help!

    I can only recommend having all files stored locally on internal drives.  Use network drives only for backup and archiving.

Maybe you are looking for

  • Trying to print w/ an Epson Photo R260 and a Buffalo LPV3 USB Print Server

    Long story. I had a home network with my iMac, my wife's PC and a Brother Multi-Function (networkable) printer...everything worked great. Tried to add an Epson Photo R260 so I can print photos and DVDs. Purchased a Buffalo LPV3 USB Print Server. Spen

  • Use of BEFORE_EXPORT Method in transaction SOBJ

    Hello,    My Requirement:       I have to add database table entries to my task before releasing the transport request, if my Transport task contains eCATT object type.      So I have developed a function module which adds table entries to transport

  • New Requirement credit management SAP SD

    Hello GuRus i am new in SAP SD please help My client want to implement credit management as For Ex. Company want to give credit limit to its Agent 100000 inr For example 5 customer is associated with this agent then company again want to give 30000 t

  • Configration and sales doc.get_config_mode error

    Hi, while I am trying to release into accounting it give an error "Internal error in communication between configuration and sales doc.GET_CONFIG_MODE" "Internal error in communication between configuration and sales doc.GET_CONFIG_MODE Message no. V

  • Calling alternating functions

    I have two functions called functionA() and functinoB(). As the play head travels down the timeline I'd like to call functionA() on frame 100, functionB() on frame 200, functionA() on 300, functionB() on 400 and so on. However, instead of having to t