Premier Pro CC and Media Encoder crashing on long file export.

Please forgive the length of this inquiry. But it is complicated and has a lot of variables.
I have an hour long mixed format timeline both Red 3K footage and Black Magic ProRes 1080P footage that I want to make a DVD from and it takes forever and crashes half way through. I have tried doing it every way possible and the only way I was able to get even a partial export was using the "MPEG 2 DVD" export option in Premier CC. It goes fast at first telling me it will take about 2 hours but even though it starts quickly doing about 15 fps it slows down to less than 1 fps and finally just stops and crashes my Cuda Core enabled Macbook Pro Laptop.
I really don't know who to ask about this since there are so many different variables. I never had a problem like this on my MBP with PP6 on a 4K timeline exporting to DVD or Blue Ray or to H-264 or Even Prores. But I wasn't mixing formats either. But on this project the first 20-30 minutes of footage goes through fine in a couple of hours but something seems to be bogging down the system on longer projects. My work around was to break the project up into multiple exports and combining them on the DVD timeline but I can't do this on every project. I thought maybe it was a corrupted clip somewhere in the timeline but when I broke the timeline up into several parts I had no problems.
I did notice a dramatic variance in the time it took to export footage based on the sequence settings. A one minute timeline comprised Red 3K footage and ProRes 1080P footage Here are some sample export results:
From a Red raw 3K timeline 2880x1620  with 1080P Prores footage upscaled 150%)
to .m2v Mpeg 2 720x480 format    1:48 Minutes ***
to .mov  Prores 422HQ  1080P                         22 Minutes
to .mov H.264  1080P                    22 Minutes
to .m2v Mpeg 2 1080P                                                22 Minutes
From a 1080P timeline Prores footage at 100%  (Red footage downscaled to 67%)
to .m2v Mpeg 2 720x480 format                         13 Minutes
to .mov  Prores 422HQ 1080P                             13 Minutes
to .mov H.264  1080P                                                             14 Minutes
to .m2v Mpeg 2 1080P                                                            14 Minutes
Since I am going to DVD,  I chose the fastest option  Red to m2v Mpeg 2 720x480 format which only took 1:48 per minute. Why? I have no idea. Maybe someone here knows the answer. But again these numbers are for a ONE MINUTE clip when I tried to convert the whole hour timeline to  the 720x480.m2v DVD File the Red timeline froze my computer after several hours even though I had set sleep mode to “Never” and turned the display off manually and I had to convert it in multiple chunks. In 20-30 minute chunks it did go fast about 1:48 per minute like the test indicated. But I would like to be able to convert the whole hour and not to have to try to stitch the clips together in my DVD authoring program.
I don’t want to have to avoid using multiple formats on the same timeline or waste time transcoding everything to the same format.
Can anyone give me any suggestions as to why the computer is crashing or bogging down in long exports and what timeline settings I should be using?
I have plenty of room on my Scratch Disk and 8 Gig of RAM and according to my Activity Monitor during the export process  have about 800 Meg of System Memory during export but the CPU Usage is 98% and in my Activity Monitor I see under “Process Name” ImporterRedServer flashing up at the top of the list about every second during export.
Why .720x480 mpeg DVD setting is so much faster than all the other export codecs?
And if there are any other settings I can use to get higher speed exports in HD? 14x1 seems a little slow especially since every time it crashes I have to start over.

Hi,
Since a long time I did not encounter the crash of Media encoder with
long file export.
But I take care of a lot of details before the export :
- clean up Media cache and Media Cache Files within PP CS6 and/or CC,
- delete all render files with Preview Files,
- rendering of sequences until the rendering is completed,
- PP CS6 and/or Pp CC opened during export to AME and/or Encore CS6,
I guessed to leave Adobe but this company remains the last with a
serious authoring software (Encore CS 6).
I tested :
- Avid Media Composer, Final Cut Pro X, both are very good software but
no really authoring software for these video editing softs.
Th only way is to "flood" Adobe with "bug reports" and "wish forms"
which are not very easy to use.
And also to call the Adobe support day by day until they send they
escalate the bug.
Le 16/05/2014 16:51, alainmaiki a écrit :
>
      Premier Pro CC and Media Encoder crashing on long file export.
created by alainmaiki <https://forums.adobe.com/people/alainmaiki> in
/Premiere Pro/ - View the full discussion
<https://forums.adobe.com/message/6384665#6384665>

Similar Messages

  • Premiere Pro CS6 and Media Encoder CS6 Color shift on export

    Hello,
    I am working on an early 2008 Mac Pro with 2 X 3.2 GHz Quad Core Intel Xeon Processors 32 GB of RAM a NVIDIA GeForce 8800 GT 512 MB Graphics Card and I am running OS X 10.8.2.
    I have the updated Version of Adobe Premiere Pro CS6 and Media Encoder CS6 through the awesome Subscription program that Adobe has started.
    My footage is shot with the Canon 1D Mark IV shot 1920X1080 at 24 FPS
    I am importing the camera files and then exporting them after I cut them up in to Quicktime Pro Res 422 HQ files
    With the technical explination out of the way here is my problem. I have color right from the camera files that I like. and with out doing any thing to change the color I export the footage and get a dramatic color shift. The exported file looks desaturated and slightly green.
    I have tried using Media Encoder CS6 to export my footage and that has the same result.
    I started my career as a photographic retoucher and use photoshop and light room constantly so I am pretty confident that i know color. I also calibrate my Lacie 526 and Lacie 324i montiors monthly as well as have a sensor that will slightly shift the profile depending on the time of day.
    I have attached three screen shots that show the color shift exactly. Now what I need is a solution. What I am not seeing is color settings for Premiere. I am totally open to any suggestions on what I might be doing incorrectly.
    Ben

    Benjamin Peterson wrote:
    I started my career as a photographic retoucher and use photoshop and light room constantly so I am pretty confident that i know color. I also calibrate my Lacie 526 and Lacie 324i montiors monthly as well as have a sensor that will slightly shift the profile depending on the time of day.
    I've been doing this for a few years now, and have come to some conclusions. Basically, the difference between still photography and video is like the difference between playing the trumpet and the sax. What you bring to the sax from playing trumpet is your ability to read music, what you know about composition, blending while playint with others, ect. But playing trumpet tells you nothing about how to physically play a sax. So it is with still photography and video.
    For starters, your carefully calibrated computer monitor is just that, a computer monitor. It doesn't display the correct working space for video. What you need for WYSIWYG in video is a monitor that can show you the Rec.709 working space. Rec.709 has a different gamut, a different gamma, probably a different white point (D65), different phosphor colors, etc., etc., etc. Enought differences that it's difficult to make a computer monitor that can successfully display Rec.709. Yet there are a couple of computer monitors that can do this (a few Eizos, one HP). The vast majority of people doing serious color correction work in video use a production monitor for just this reason.
    But a production monitor isn't enough. You also have to make sure that the signals you're sending the production monitor are correct. There's a sub-industry making signal converters for signals from NLE video cards (usually RGB based) -> signals for production monitors (usually YUV based).
    That said, it is certainly possible to get a very good match between your NLE suite and a DVD / BD as displayed on an HDTV. But it's not as simple or easy as a calibrtated computer monitor for still photography use.
    This is probably part of your problem. But Quicktime is probably the root of it. Quicktime is, well, I guess the polite way of saying it is that Quicktime is problematic. It gives all kinds of problems. Most people have abandoned it. You should too.

  • Premire Pro CC 2014 and Media Encoder Crash During Launch

    Premire Pro and Media Encoder crash during startup and are unusable. I am using Windows 7 Ultimate and already tried reinstalling Adobe Creative Cloud from scratch and it's still happening. I also tried following Adobes KB articles directions to rename the Adobe folder in my documents and appdata to no avail. When I try to launch either application, I get a generic windows crash message "Adobe Premire Pro CC 2014.0 has stopped working" and when I click problem details, it lists this:
    Problem signature:
      Problem Event Name: APPCRASH
      Application Name: Adobe Premiere Pro.exe
      Application Version: 8.0.0.169
      Application Timestamp: 536f4f89
      Fault Module Name: ImageRenderer.dll
      Fault Module Version: 8.0.0.169
      Fault Module Timestamp: 536f2c18
      Exception Code: c000001d
      Exception Offset: 00000000001f5382
      OS Version: 6.1.7600.2.0.0.256.1
      Locale ID: 1033
      Additional Information 1: 0b2d
      Additional Information 2: 0b2df4702c3fc6489bf922fb8e966350
      Additional Information 3: fa9f
      Additional Information 4: fa9f59f642d335ee71c6667e52000d39

    I am having a similar problem.
    Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
    The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
    I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
    My timeline is 2K, 58 minutes in 23.976
    Only effects applied are Lumetri LUTs - no third party.
    I've exported as recently as a week ago without issue.
    Running OSX 9.5 on an X99 board
    3.75 GHz 8-core
    64GB 2400 MHz RAM
    EVGA Titan Black 6GB
    Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
    Thanks Adobe, for checking this out.

  • Media Encoder crashes on batch sequence export

    I edited an online video dictionary (about 7,500 five second clips) and have them all in sequences in Premiere pro CC waiting to be exported. I hae been battling for two weeks now day in and day out to try and export... I am limited to batch exporting this project and have never had problems with adobe softwares in five years ( a great track record). I have tried many ways of importing or exporting the sequences to Media Encoder CC, and have experienced crashes every single export attempt. As soon as I add more than 5-10 clips the program crashes when I start the que. I have tried 5 different computers, and still have not been able to solve this problem. I badly need to deliver this product, does anyone have a patch that will keep ME from crashing when you add more than a couple clips?

    Hi rdobbins,
    Please mention the operating system, the version of Premiere Pro CC and Media Encoder CC and he type of the files used in the project. Is there any third party plug-ins used in the project. If possible, please mention the crash logs as well.
    Regards,
    Vinay

  • Premiere Pro and Media Encoder crash while rendering H.264

    Very recently, a problem's popped up where Premiere Pro and Media Encoder (CC) will crash while rendering H.264.
    It's only while rendering H.264 - other formats seem to work fine.
    And I don't mean that it returns an error, I mean it hard crashes with a Windows "Adobe Premiere Pro CC has stopped working" popup.
    It doesn't crash at a consistent time during the render, even on the same project. Occasionally, it won't crash at all, but this is usually not the case.
    I've tried disabling CUDA and my overclock to no avail. Please help!

    On the topic of opening a project on the exact same version of Premiere Pro CC 2014 (yes it is definitely up to date, and the 2014 version), to overcome this export crash problem that ZachHinchy has brought up - you can't. Technically speaking, one should easily be able to open a Premiere Pro CC 2014 project from one system on another system running the exact same up to date, legitimate version of Premiere Pro CC 2014 without any kind of error. But for some reason, this has been disallowed(?) by Adobe. It has facepalm written all over it. Does anyone agree that this is at least a little bit silly?
    I have tried exporting a Final Cut Pro XML from my project to try and open the sequence at uni on a Mac, so I can render my project when I finish my edit. It half works - the clips are there, but the sequence is gone - i.e. 12 hours of painstaking sequencing and micro-edits that had me at several points in time wanting to insert my hand through my monitor with enough force to make a large hole. I really cannot afford redo this sequence, as my assignment is due tomorrow, and I have to work at 6 oclock in the morning, so I also cannot afford to stay up till the early hours of tomorrow morning. Wish me luck that some miraculous event has taken place overnight that will somehow allow me to just open my project, on the same version of Premiere, on a Mac, without hassle. (Apple OS is not friendly to anything but its own selfish nature, so I am having doubts).
    Adobe please, if you can do anything at all to help, you will save my assignment, and my faith will be restored. Otherwise, I'll just get my money back and buy Final Cut instead.
    I cant even
    If I find a way to fix either of these problems, I will post straight away.

  • Premiere and Media Encoder Crashing During Export of Quicktime Files

    Premiere CC and Media Encoder CC crashes when exporting Quicktime H.264 files. Sometimes the export will work, sometimes it crashes the app. After crashing, the app will freeze while loading "ExporterQuictimeHost.bundle" and requires a hard re-boot of the system to startup again.
    I have tried removing some Quicktime codecs from the Quicktime library folder, as suggested in other threads. This has not solved the problem.
    I am editing with Quicktime ProRes 4444 files.
    Any help on this would be greatly appreciated. Here's some system info:
    Mac Pro Mid 2010
    OS X 10.9.4
    2 x 2.66 GHz 6-Core Intel Xeon
    36 GB Memory
    NVIDIA Quadro FX 4800 1536MB
    Blackmagic DeckLink HD Extreme
    Cuda Driver Version 6.5.14
    Creative Cloud CC 2014

    I'm having similar problems. I can't export anything now...either from Premiere or from Media Encoder. My sequence is ProRes HQ, I am exporting using sequence settings.
    It gets about 75% of the way through and bails with this error message:
    Export Error
    Error compiling movie.
    Unknown error.
    That's really helpful. Addtionally, when I tried to export out of Media Encoder, I was greeted by an extremely loud bleating goat noise when it failed. Nice. I had a room full of clients. Thanks Adobe.
    I'm seriously doubting the claim of "Pro" at this point.
    This was not beta tested with a ****.

  • Adobe Premiere and Media Encoder crash on Export

    Hi
    I Run Premiere CC and media encoder on a 2011 27in iMac with 12GB RAM. Until recently everything exported fine. But now when I either do an export from within Premiere or queue via Media Encoder it crashes halfway through. I've tried reinstalling both to no avail. Any idea to why this could be happening and how can I fix it? I'm running Yosemite.
    Cheers

    Hi
    I Run Premiere CC and media encoder on a 2011 27in iMac with 12GB RAM. Until recently everything exported fine. But now when I either do an export from within Premiere or queue via Media Encoder it crashes halfway through. I've tried reinstalling both to no avail. Any idea to why this could be happening and how can I fix it? I'm running Yosemite.
    Cheers

  • Adobe MEdia Encoder Crashes with big files inputed

    Hello,
    There isn't a forum for the Adobe Media Encoder, so I thought this would be a good spot. I am an after effects and Premiere user who likes the idea Adobe seems to have of using the media encoder to cover all my encoding needs.
    My typical workflow, especially since these days I'm doing more shorter form animations, is to render out to a Quicktime Animation codec file as my main archive file. From there, output all the various different web versions, flv, etc from that core archive file. Since my projects usually aren't running more than 5 minutes, this leaves me with a nice 3 - 7gig file.
    Problem: I'm running CS4 and the media encoder crashes when I input files that are in this file size range. The program locks up when I push start que, and then eventually crashes. Works fine with smaller size files that are about under a gig.
    I can run a render out of after effects, which seems to be more stable. But I'd love to be able to use this great new tool.
    Here's my machine specs if it helps:
    PC
    Intel Quad Core Q9550 @ 2.83 ghz
    4gB RAM
    Windows Vista 64 bit ultimate
    All updates current for CS4 apps as of 01/30/08
    Running Adobe Media Encoder V 4.01.078
    Hard drives are nothing special. 7200 rpm western digital internal and external. I've tried all sorts of hard drive configurations, where the input is coming from, where it's going, etc. No difference.
    I have been experimenting with using Lossless AVI's as my "uncompressed" archive file. Works well, but same crashing with the Media Encoder.
    Also tried experimenting with frame size alterations during encoding, no difference there. Also, whatever the output codec is, be it FLV, H264, etc. no difference.
    Anyone have any thoughts or have experienced similar issues? I hope all my MAC friends aren't right, seems like all my attempts to streamline my workflow with this CS4 and beefy PC combo are crashing and burning.
    Anyone else feeling this pain, or have recommendations?
    Thanks,

    Thomas, thanks for your suggestions on Vista optimization. That Sheer Codec looks nice, but hard justify the cost when I've been working for years with essentially uncompressed codecs that work well. Will play more though to see if the cost would actually pay off in the long run though.
    In general I made a decision that it was too early to throw in the towel on my old uncompressed codecs. The Quicktime animation codec has always been for me the safest, most universally accepted, and most reliable "uncompressed" codec. It's always worked in the past, not gonna give up just cuz media Encoder CS4 has troubles.
    Mylenium, thanks for the reminder about the silly platform wars. I've always felt the same as you, but when I'm stressing sometimes the silly propaganda can get to me. Makes me forget that no matter what system ya got, it never works perfect!
    Here's an update. I have trying my best to learn more about the bug and have come to some interesting realizations. The AME does work with larger files, just not the larger files that I had been using at the current moment. Older files of mine as big as 20GB can be inputed into AME with fine results.
    This being said, it scratches out most of the RAM overload thoughts with AME.
    The difference with my current files that were causing AME crashes: larger than a few GB, came from AE, had the 1.21 pixel aspect ratio metadata.
    When I re-interpreted the file in AE into a square pixel aspect ratio, exported it, it was then successfully inputed into AME.
    I have read just now that there were changes in After Effects widescreen pixel aspect ratio interpretation in CS4. Can this change be causing problems in my AME. Not positive, but I'm now thinking after many days of testing that the bug could have its roots somewhere in this ball park.
    If anyone from Adobe is reading this, I would love any ideas you might have on this issue. In general, there is really no support for the Adobe Media Encoder itself. This is not good, considering how it is so necessary for AE and Premiere users like myself.
    Thanks,

  • Best quality HDV to DVD using Premier Pro CC to Media Encoder CC and Encore

    I have been struggeling to create a decent looking DVD from my HD video.  I am a newbe.  And I have read many, many forum posts trying to learn the best practice and have come out even more confused.  Many posts are back in 2009 and I don't think they apply.  Some recommend dynamic link which does not appear to be an option for me.  So I am hoping to get a clear answer to my problems.  I am including alot of info because I don't know what is really important.
    I have 2 types of video that I am merging into my sequences.
    Sony:
    Format                                   : AVC
    Bit rate                                 : 11.5 Mbps
    Maximum bit rate                         : 16.0 Mbps
    Width                                    : 1 440 pixels
    Height                                   : 1 080 pixels
    Display aspect ratio                     : 16:9
    Frame rate                               : 29.970 fps
    Scan type                                : Interlaced
    Scan order                               : Top Field First
    JVC:
    Format                                   : AVC
    Bit rate                                 : 16.3 Mbps
    Maximum bit rate                         : 17.0 Mbps
    Width                                    : 1 920 pixels
    Height                                   : 1 080 pixels
    Display aspect ratio                     : 16:9
    Frame rate                               : 29.970 fps
    Scan type                                : Interlaced
    Scan order                               : Top Field First
    I set my sequence in Premier Pro CC to
    AVC-Intra 50 1080i
    29.97 fps
    1440 x 1080
    HD Anamorphic 1080 (1.3333)
    30fps Drop-Frame Timecode
    Hopefully I set up my sequence correctly???
    Dynamic Link is not available to me, so I export the sequence.  This is where i get confused.
    I export to MPEG2-DVD.  Preset NTSC DV Wide
    Some forum posts say to tweek the video setting for better quality, this is what I have read:
    quality to 100
    minimum bit rate  4
    target bitrate 6
    maximum bitrate 7
    click maximum render quality
    Since my source has upper field order but PP defaults to lower field order, should I switch to upper?
    I encode in Media Encoder. 
    In Encore, I have my dvd settings:
    MPEG-2
    720x480
    29.97 fps
    Lower fields first  (should this be upper??)
    I have an i5 processor, 8G ram, I am using Mecury GPU accelerator.
    I listed a lot of stuff and I appologize.  I just think the quallity I am getting isn't there.  With these setting and what I am doing, is this as good as the quality gets?
    Help

    Use a 1920 x 1080, 30i sequence for the editing, not 1440 x 1080.
    Start with the MPEG2-DVD option and the NTSC DV Widescreen preset.  Change the Quality to 100.  Change the Field Order from Lower to Upper.  Change the Min, Target and Max bitrates to 5, 7 and 9 respectively.  If you have hardware acceleration turned on, export away.  If you're running in Software Only mode, check the Maximum Render Quality box and then export.
    Bring the resulting video and audio files into Encore for authoring.

  • Premiere CC and Media Encoder crashing new Mac Pro

    Since installing CC on my new Mac Pro (Late 2013) Premiere and Adobe Media Encoder have been continually crashing my system.
    At first, my comp would freeze and I'd have to hard restart, then it switched to rebooting on in's own. This would happen 10-20 times a day while editing.
    This began shortly after I synced settings from a previous version of PP but since I've installed new RAM; reinstalled CC/PP; reformatted my HDD and reinstalled Mavericks, CC, PP; and have not synced my settings. I've also tried editing multiple projects of different sizes with different media types -- all are experiencing the same problems.
    When I edit the same projects on my MBP, everything works fine.
    Recently, I have disabled GPU acceleration in all of my PP projects and that seems to have solved the problem.
    My office received 3 Pros at the same time with the same hardware configurations and software -- I am the only one experiencing this problem.
    Here are some specs:
    Late 2013 Mac Pro
    2.7 Ghz 12-Core Intel Xeon E5
    64 GB 1867 MHz DDR3 ECC
    AMD FirePro D700 6144 MB
    All drivers, CC, and software is up to date.
    So what do I do now?
    Any help is much appreciated!

    I am on Windows, but have a few saved Mac discussions that may help (or, may not... but free to read)
    Mac and Root User http://forums.adobe.com/thread/879931
    -and http://forums.adobe.com/thread/940869?tstart=0
    Mac & nVidia Driver http://forums.adobe.com/thread/1075592
    -and http://www.nvidia.com/object/mac-driver-archive.html
    Mac Retina Bug http://forums.adobe.com/thread/1159632
    Troubleshooting guide for Mac freeze
    http://helpx.adobe.com/x-productkb/global/troubleshoot-system-errors-freezes-mac.html
    External speakers stop playback http://forums.adobe.com/thread/1370072?tstart=0
    OSX Crash http://helpx.adobe.com/creative-cloud/kb/ame-premiere-crash-launch-export.html

  • Premiere Pro CC 2014 & Media Encoder Crash when rendering

    Every time I try and render something out of Premiere Pro CC 2014 it will crash before it completes the render. I have no idea why. I am on a windows 8 machine running the latest version of Premiere Pro CC 2014.Any idea what is going on?
    Here is the log from Event Viewer:
    Faulting application name: Adobe Premiere Pro.exe, version: 8.0.1.21, time stamp: 0x53c7b17f
    Faulting module name: mc_enc_avc.dll, version: 9.8.11.6624, time stamp: 0x536af65d
    Exception code: 0xc0000005
    Fault offset: 0x00000000000e7f80
    Faulting process id: 0x650
    Faulting application start time: 0x01cfb99562fe469a
    Faulting application path: E:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
    Faulting module path: E:\Program Files\Adobe\Adobe Premiere Pro CC 2014\mc_enc_avc.dll
    Report Id: f30f38a1-2589-11e4-bf2c-bc5ff467c039
    Faulting package full name:
    Faulting package-relative application ID:
    Here is the Report.wer that windows automatically generates: http://pastebin.com/hriEegkJ
    I have also tried rendering out of media encoder and I get a crash also (Report.wer: http://pastebin.com/Dpvk6bDb):
    Faulting application name: Adobe Media Encoder.exe, version: 8.0.1.48, time stamp: 0x53c99d97
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x000000002c2cce3d
    Faulting process id: 0xcf8
    Faulting application start time: 0x01cfb9906060796e
    Faulting application path: E:\Program Files\Adobe\Adobe Media Encoder CC 2014\Adobe Media Encoder.exe
    Faulting module path: unknown
    Report Id: 07096c20-2584-11e4-bf29-a0f3c1153ce7
    Faulting package full name:
    Faulting package-relative application ID:

    More hardware information might help someone give you an idea
    -Premiere Pro Video Editing Information FAQ http://forums.adobe.com/message/4200840
    or
    http://blogs.adobe.com/kevinmonahan/2014/01/13/computer-shuts-down-with-premiere-pro-or-af ter-effects/

  • Premiere Pro CC and Media Encoder won't start

    Hey everyone,
    I have a huge problem: My Adobe Premiere CC won't start. I've tried all the solutions I've found in the internet, but nothing seems to work for me
    I am using OS X 10.9.3.
    Here is a part of my report:
    Process:         Adobe Premiere Pro CC 2014 [1153]
    Path:            /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
    Identifier:      com.adobe.AdobePremierePro
    Version:         8.1.0 (8.1.0)
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [235]
    Responsible:     Adobe Premiere Pro CC 2014 [1153]
    User ID:         501
    Date/Time:       2014-12-10 23:51:37.341 +0100
    OS Version:      Mac OS X 10.9.3 (13D65)
    Report Version:  11
    Anonymous UUID:  5BE9B722-1F73-691F-5EEF-9775088356E8
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000001650
    VM Regions Near 0x1650:
    -->
        __TEXT                 0000000100000000-0000000100003000 [   12K] r-x/rwx SM=COW  /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   libsystem_platform.dylib       0x00007fff9195abe6 OSAtomicAdd32Barrier$VARIANT$mp + 2
    1   libclh.dylib                   0x00007fff9076859f 0x7fff90765000 + 13727
    2   libclh.dylib                   0x00007fff90875305 clhCtxCreate + 101
    3   libGPUSupportMercury.dylib     0x00007fff94e2daab gldCreateQueue + 651
    4   com.apple.opencl               0x00007fff8f68e8ad 0x7fff8f688000 + 26797
    5   com.apple.opencl               0x00007fff8f68d32b 0x7fff8f688000 + 21291
    6   com.apple.opencl               0x00007fff8f68d211 0x7fff8f688000 + 21009
    7   com.apple.opencl               0x00007fff8f6a9fbe clCreateCommandQueue + 150
    8   com.adobe.GPUFoundation.framework 0x0000000109afbeb1 GF::CreateOpenCLCommandQueue(_cl_device_id*, _cl_context*, bool) + 65
    9   com.adobe.GPUFoundation.framework 0x0000000109ad521f GF::Device::InitializeContextImpl() + 2479
    10  com.adobe.GPUFoundation.framework 0x0000000109ad76ae GF::Device::InitializeContext(bool, void*, void*) + 622
    11  com.adobe.GPUFoundation.framework 0x0000000109af141a GF::Initialize(bool, bool, bool, void*, void*) + 2154
    12  com.adobe.DisplaySurface.framework 0x0000000111bb7f84 DS::Initialize() + 228
    13  com.adobe.Mezzanine.framework 0x000000010636c3cd MZ::(anonymous namespace)::FullInitializer::FullInitializer(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, bool, bool, bool) + 6173
    14  com.adobe.Mezzanine.framework 0x0000000106369874 MZ::Initializer::Initializer(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, bool, bool, bool) + 84
    15  com.adobe.Frontend.framework   0x00000001000abe97 FE::Initializer::PrivateImpl::PrivateImpl(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 1479
    16  com.adobe.Frontend.framework   0x00000001000aadc8 FE::Initializer::Initializer(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 40
    17  com.adobe.Frontend.framework   0x00000001000cdc32 FE::AppMain(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int, void*) + 226
    18  com.adobe.Frontend.framework   0x00000001000d4ea5 FE::Run(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int) + 581
    19  com.adobe.AdobePremierePro     0x00000001000018ac main + 508
    20  com.adobe.AdobePremierePro     0x00000001000016a4 start + 52

    AND Media Encoder won't start as well!!
    Process:         Adobe Media Encoder CC 2014 [1284]
    Path:            /Applications/Adobe Media Encoder CC 2014/Adobe Media Encoder CC 2014.app/Contents/MacOS/Adobe Media Encoder CC 2014
    Identifier:      com.adobe.ame.application
    Version:         8.1.0.122 (8.1.0)
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [235]
    Responsible:     Adobe Media Encoder CC 2014 [1284]
    User ID:         501
    Date/Time:       2014-12-10 23:59:55.226 +0100
    OS Version:      Mac OS X 10.9.3 (13D65)
    Report Version:  11
    Anonymous UUID:  5BE9B722-1F73-691F-5EEF-9775088356E8
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000001650
    VM Regions Near 0x1650:
    -->
        __TEXT                 0000000100000000-0000000100088000 [  544K] r-x/rwx SM=COW  /Applications/Adobe Media Encoder CC 2014/Adobe Media Encoder CC 2014.app/Contents/MacOS/Adobe Media Encoder CC 2014
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   libsystem_kernel.dylib         0x00007fff93a9a292 __kill + 10
    1   com.adobe.dvacore.framework   0x00000001003a28ea (anonymous namespace)::SignalHandler(int, __siginfo*, void*) + 410
    2   libsystem_platform.dylib       0x00007fff9195b5aa _sigtramp + 26
    3   libsystem_platform.dylib       0x00007fff9195abe6 OSAtomicAdd32Barrier$VARIANT$mp + 2
    4   libclh.dylib                   0x00007fff9076859f 0x7fff90765000 + 13727
    5   libclh.dylib                   0x00007fff90875305 clhCtxCreate + 101
    6   libGPUSupportMercury.dylib     0x00007fff94e2daab gldCreateQueue + 651
    7   com.apple.opencl               0x00007fff8f68e8ad 0x7fff8f688000 + 26797
    8   com.apple.opencl               0x00007fff8f68d32b 0x7fff8f688000 + 21291
    9   com.apple.opencl               0x00007fff8f68d211 0x7fff8f688000 + 21009
    10  com.apple.opencl               0x00007fff8f6a9fbe clCreateCommandQueue + 150
    11  com.adobe.GPUFoundation.framework 0x0000000109ef7b01 GF::CreateOpenCLCommandQueue(_cl_device_id*, _cl_context*, bool) + 65
    12  com.adobe.GPUFoundation.framework 0x0000000109ed0e6f GF::Device::InitializeContextImpl() + 2479
    13  com.adobe.GPUFoundation.framework 0x0000000109ed32fe GF::Device::InitializeContext(bool, void*, void*) + 622
    14  com.adobe.GPUFoundation.framework 0x0000000109eed06a GF::Initialize(bool, bool, bool, void*, void*) + 2154
    15  com.adobe.DisplaySurface.framework 0x0000000107845f74 DS::Initialize() + 228
    16  com.adobe.ame.application     0x00000001000376e7 AME::app::MCInitializer::MCInitializer() + 12039
    17  com.adobe.ame.application     0x000000010002323a AME::app::AMEAppInitializer::AMEAppInitializer(exo::app::AppInitArgs&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >&) + 250
    18  com.adobe.ame.application     0x000000010000d2ba AME::app::AMEApp::InitApplication(exo::app::AppInitArgs&) + 1802
    19  com.adobe.exo.framework       0x00000001057d2bd5 exo::app::AppBase::Initialize(exo::app::AppInitArgs&) + 1141
    20  com.adobe.ame.application     0x00000001000167e6 AME::RunTheApp(exo::app::AppInitArgs&, std::vector<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >, std::allocator<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > > >&) + 3270
    21  com.adobe.ame.application     0x0000000100047828 main + 440
    22  com.adobe.ame.application     0x00000001000032f4 start + 52

  • Problems exporting mpeg 2 videos using Premiere Pro CS6 and Media Encoder

    Using a Mac, I'm trying to exporting an mpeg 2 video from Premiere Pro CS6 using the queue process that opens the Media Encoder but when the process begins, it freezes and doesn't end.

    Using a Mac, I'm trying to exporting an mpeg 2 video from Premiere Pro CS6 using the queue process that opens the Media Encoder but when the process begins, it freezes and doesn't end.

  • Media Encoder/Premiere Export Crashing During long file exports

    I'm running Premiere Pro CC 2014 on a windows 7 computer--a Livestream Studio HD500. I use the computer to capture live video, which is saved as large AVI motion-jpeg files. I need to edit and export these files as compressed h.264 videos for upload to the web.
    I am able to import these files into premiere and work with them, but the program crashes to desktop during any long export. I am able to export very short (1 or 2 minute) videos just fine, but anything longer will crash to desktop after a few minutes of processing. Media encoder also crashes when attempting to compress the videos prior to processing.
    I have been able to circumvent this problem by compressing the files I'm working with in advance using virtualdub, but it adds an annoying step to the workflow that I'd like to eliminate. Shouldn't premiere be able to import, edit, and export compressed versions of these files without crashing?
    Note: I've tried turning off GPU rendering and clearing my cache several times.
    Thoughts? Much appreciated.

    Maybe this problem?
    http://blogs.adobe.com/kevinmonahan/2014/01/13/computer-shuts-down-with-premiere-pro-or-af ter-effects/

  • Updated to latest premier pro CC and lost render

    I updated to the latest virsion of premier pro CC and when I opened up my porject I lost my render previews. Now when I try and render it maxes out my ram and crashes. Running 32GB of ram on windows 8 system. Also seems to be having issues with lightroom now, it won't recognize some files it already impoorted, can't open up the folders

    Hi,
    Since a long time I did not encounter the crash of Media encoder with
    long file export.
    But I take care of a lot of details before the export :
    - clean up Media cache and Media Cache Files within PP CS6 and/or CC,
    - delete all render files with Preview Files,
    - rendering of sequences until the rendering is completed,
    - PP CS6 and/or Pp CC opened during export to AME and/or Encore CS6,
    I guessed to leave Adobe but this company remains the last with a
    serious authoring software (Encore CS 6).
    I tested :
    - Avid Media Composer, Final Cut Pro X, both are very good software but
    no really authoring software for these video editing softs.
    Th only way is to "flood" Adobe with "bug reports" and "wish forms"
    which are not very easy to use.
    And also to call the Adobe support day by day until they send they
    escalate the bug.
    Le 16/05/2014 16:51, alainmaiki a écrit :
    >
          Premier Pro CC and Media Encoder crashing on long file export.
    created by alainmaiki <https://forums.adobe.com/people/alainmaiki> in
    /Premiere Pro/ - View the full discussion
    <https://forums.adobe.com/message/6384665#6384665>

Maybe you are looking for

  • IPad (gen 1) keeps crashing

    Hi, Randomly, but more and more often my original 32 GB WiFi iPad crashes. Totally unforced. No matter what I do. I finally was able to catch it on cam today. On this clip it first crashes with multiple stripes on screen, which is most common, then l

  • Single Path Selection Lag Illustrator CS4

    Running OSX on a MacBook Pro Illustrator CS4 up to date 4gb Ram No significant performance issues anywhere else. Does this happen to anyone else? Draw a path.  Deselect the path.  Use a single click to select the path with the selection tool. For me

  • Customer Master in IS Retail

    Hi All 1.Will there be Customer Master data available in IS etail like SD? 2. Can anybody send me the link for IRT100 material Regards Kumar

  • Cannot Type Some Arabic  Characters

    Dear All, I am working in bilingual project English and Arabic. In 10gforms i can type arabic and save it properly but in 10g reports i cannot type some of the arabic characters in design view. but the same characters i can type in arabic using other

  • Blocking my name

    i want to sykpe with someone i do no know.  I do not want my name to appear on the page that they see.  how do i take my name off of outgoing skype? Is it possible to set up a new account using initials and a new skype name?   I tried this but when i