Premiere now freezes on Media Encoder Queue

After updating to the Oct 2014 CC Update, upon exporting media using the Media Encoder queue, Premiere freezes on the "Preparing Data for Export" box.  It launches Media Composer, but it never makes it out of Premiere.
Just exporting from the application works, as well as importing sequences straight into Media Encoder.  But I need the queue to work.
On a Windows 8.1 PC
24b 1333 mhz ram
3.2 ghz Intel Processor
NVIDIA Quadro FX 3800
R

I am having the same problem (see Premiere now freezes on Media Encoder Queue)
I am on 2014.1 of both programs (8.1.0 on premiere, 8.1.0.122 of AME).  I know an update just came out today, but it seems to be just a RAW photo update.
Mine hangs when premiere is "Preparing Media for Export..."  It launches AME and AME boots up fine... so from where I sit, it looks like a Premiere problem as it's compiling the project file to export.
Neither "import natively / non natively" or GPU acceleration help.  However, I wouldn't expect them to, given this seems to be a premiere problem, not an AME problem.
That thread does not apply re: nView.
R

Similar Messages

  • Premiere freezes when sending to Media Encoder Queue

    Hey guys,
    This issue is on all of our computers (Mac Pros and 27" iMacs) and happens on 40% of attempted exports through Media Encoder.
    Here's our new workflow:
    - Export TImeline (Command + M)
    - Send to Media Encoder (Queue button)
    - Media Encoder Opens and Premiere gets hung on "Preparing Data for Export" dialogue
    - Force Quit Premiere and get a dialogue that "There has been a serious error and Premiere needs to close"
    - Reopen Premiere and try again – usually get a clean export (or two on a good day) before it craps out again
    We've sort of gotten used to it but I'm wondering – anyone else having this issue? It's getting annoying (and embarrassing when you're in a client session).
    Doesn't matter what timeline setting or what's on the timeline. Also doesn't matter what version of either program.

    I am having the same problem (see Premiere now freezes on Media Encoder Queue)
    I am on 2014.1 of both programs (8.1.0 on premiere, 8.1.0.122 of AME).  I know an update just came out today, but it seems to be just a RAW photo update.
    Mine hangs when premiere is "Preparing Media for Export..."  It launches AME and AME boots up fine... so from where I sit, it looks like a Premiere problem as it's compiling the project file to export.
    Neither "import natively / non natively" or GPU acceleration help.  However, I wouldn't expect them to, given this seems to be a premiere problem, not an AME problem.
    That thread does not apply re: nView.
    R

  • Premiere CC and/or Media Encoder audio bad renders

    Occasionally, but not always, when I export a timeline to Media Encoder queue, the video renders out with no audio.
    I have not found a repeatable way to replicate this, but when it happens, it really blows up my workflow.
    Typically I:
    Import a ProRes 1080 clip into a fresh timeline, and only trim down the ends. Audio and Video playback great in premiere. I then, without changing anything, export to media encoder queue in h.264 1080p OR 720p (vimeo preset).
    The queue runs and bang, video file with no audio.
    My extended workflow is as such - once the h.264 file has arrived in the folder (it is a watchfolder), there are presets set to create OTHER Files - wav for CD, mp3 for podcast, DVD for distro, mp4 for podcast. So, as you can see, it snowballs into a trainwreck. I would also automate/schedule the podcast postings, but obviously I can't rely on media encoder/premiere to do it's job.
    Has anyone experienced any lack of audio render issues? Is it tied to hardware at all, or is it just freak randomness? I even got to point to where I reboot the machine right before each original capture begins, but the error is always in the first render out of premiere.
    I have checked for any muted tracks and such, and there are none. As I said, it is VERY random. For instance, this week, I dropped the capture into a timeline, exported as usual, and got a bad render. Did it again, this time moving the audio down a track. Still a bad render. Rebooted the Mac, tried it all again, and finally got a working render. This is the first time it has happened TWICE in a row, and I'm getting tired of it, as these renders are fairly long.
    Any help would be much appreciated.
    - Ben

    Ben, I'm having the same issue.  Never had it before yesterday. 
    I'm editing on CC with R3D's.  I have 8 tracks of audio.  When I'm exporting (either through Encoder or through Premier) I'm getting a final product that has no audio, and in its place a loud clicking sound.  I performed a number of reboots and got it to export once.  But I've tried dozen's of times now and can't get audio to export through this sequence. 
    When I go to render the project I'm getting an "Error Compiling Movie.  Unknown Error" message.   I suspect that's related.  Not sure what's happening.  I'm going to keep testing.  I'll let you know if I discover anything.  But it is VERY FRUSTRATING:(  Deadlines are looming. 
    -Brian

  • Premiere, After Effects, Speedgrade, Media Encoder and... the dynamic link

    My feeback after working with the dynamic link these days. Basic project. Editing, color correction, animated titles.
    I'm using a 3.5Ghz iMac 24GB Ram and a GTX 780 4GB. (2014 versions & last updates).
    Rendering the timeline in Premiere is sometimes extremly slow (with AE comps). Need to quit and reload the project to get a good speed.
    Too long delay of refresh for the AE compositions inside Premiere (with the dynamic link). Need to go in AE then back to Premiere to get the refresh.
    When i export to media encoder i need sometimes to save then send it 2 or 3 times to get the last edits in the export.
    Even worse with the AE compositions. If i change something in AE then export from Premiere i need to quit and reload Media Encoder to get the last changes.
    Really fast export from Premiere to Speedgrade and from Speedgrade to Premiere.
    But !!! Lumetri fx is not compatible with AE.  And Speedgrade doesn't support BlackMagic but only this nVidia Sdi thing.
    And why we could not export h264 from AE anymore ???
    Quiet disappointing :-(

    Using Premiere Pro CC 2014.0.1 (build 21) and Media Encoder 2014.0.1 (build 8.0.1.48) on OS X 10.8.5
    If I Export a video from Premiere, I can continue using Premiere, but if I Queue an export, returning to Premiere produces the beach ball of death. If I give it time, the beach ball goes away and the arrow returns, but trying to click anywhere in Premiere simply returns the beach ball. There is nothing to be done but Force Quit Premiere. I can leave Premiere and run any other application, but if I leave to execute the Media Encoder queue, I cannot return to Premiere and use Premiere. I can visit Media Encoder (call it to the foreground) and return to Premiere after the queue is done.
    My current workaround is to use Export from Premiere and not use Queue from Premiere.

  • 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.

  • Premiere Pro and Adobe Media Encoder running slow

    Hello everyone,
    I'm having trouble with CS4, which is running significantly slower than CS3 did on a older machine. The CS4 suite is installed on a Dell Precision M6400:
    Windows Vista 64-Bit
    Intel Core 2 Duo CPU T9400 @ 2.53 GHz
    8 GB RAM
    NVIDIA Quadro FX 2700M Graphics with 512MB dedicated memory
    The OS is running on a 57.5 GB HD (C:) and the Adobe suite is installed on a 298 GB Solid State HD (D:), except for Adobe Media Encoder, which is installed on the C: drive.
    My project has 4 15-16 minute sequences. The sequences are in DV NTSC, 29.97 fps,  My scratch disks are set to a folder on the C: drive. Media Cache Files and the Media Cache Database points to a folder on the D: drive.
    These are some of the problems I'm having:
    - Premiere Pro CS4 generates peak files every time I open a project
    - It then takes 3-5 minutes to render before I can preview a 16-minute sequence
    - Adobe Media Encoder takes 5 hours to render a 16-minute sequence (as flv) that has been previously rendered
    - AME takes 1 hour to render every 15 minute sequence that has never been rendered before
    Are my settings affecting their performance? Is there any way to improve it? Thanks.
    (Premiere Pro is the only app that is slow)

    The data rate for replay is one thing, the data rate from disk to memory then from memory to CPU and back the other way are different matters and ought not to be confused. It is well-established that for a computer to edit AVCHD you need top end components, and note that I said there were three tasks to distinquish with increasing hardware requirements, namely merely replaying the video, specifying edits in the editor and then the rendering. It is commonly accepted by all the industry vendors that to do remotely commercial AVCHD rendering you need a minimum Quadcore CPU then that eats data fast, in order to not let it go to waste you need a fast motherboard bus fast memory and in order for none of those to go to waste you need the fastest disk set-up you can manage. I in fact have a 4-disk RAID0 volume using SATA (I think the disk model is SATAII but I have to await return from the repair center before I can confirm). For this RAID0 volume I have run speed test software from BlackMagic because I have one of their HDTV capture cards. It recorded that this volume which remember is doing parallelised IO is just fast enough to receive a encoded HDTV stream from the BlackMagic card but too slow to receive an uncompressed HDTV stream, indeed when I tried both I found the volume did keep up with compressed but fell behind with uncompressed. Remember that with a RAID0 volume of 4 SATAII disks a given file gets spread over the four disks and hence IO is spread over those 4 3G/s data lanes. Also remember with these disks 3G/s is just a burst speed, for AVCHD we are interested in sustained serial IO which is much less.
    Before my machine broke down, I found that it took 5 hours to render 33 minutes of HDTV albeit as it went along it transcoded from AVCHD to a Microsoft HD format for Vista-only. Another interesting thing is that I found that the longer this render ran the slower it became, the estimated time started at 3 hours but the actual was five and the last one third took maybe 3 hours. Because the machine broke after that run I couldn't figure the bottleneck. For my machine bear in mind that at the repair shop we found that the Quadcore had only half the necessary electrical power plugged in, the monitor software showed however that it constantly ran around 90% of whatever capacity that reduced power supply permitted. Now then we can puzzle over why it got slower and slower and yet CPU consumption remained consistent and near to full capacity, memory was not the bottleneck because that was constant at 6.4G. But you can say that this was maybe performing like a Dualcore and was hitting some sort of wall, if you had a 1 hour render with that rate of degeneration of performance factored in what would happen to the render time, and for 3 hours you could be running indefinitely. I hope when the machine comes back the correct power supply will make it behave like a Quadcore should for this type of application. Anyway I have two theories for the degradation. First is just that PrProCS4 was getting its knickers in a twist and thereby just doing more computation per minute of video to be rendered as time went by, maybe internal resource management related to OO-type programming maybe, or related to disk IO falling behind, both these theories have problems, for the latter the CPU usage should then have dropped also.
    Anyways, you need really a Quadcore system and blazing fast disk to work fully with AVCHD commercially, we found an external SATAII disk so if I were you I would just go get one and move on with your life.
    Message du 03/06/09 16:08
    De : "Jim Simon"
    A : "JONES Peter"
    Copie à :
    Objet : Premiere Pro and Adobe Media Encoder running slow
    For AVCHD you MUST have FAST disks.
    AVCHD actually has a lower data date than DV. You need lots of CPU muscle, but disk speed is really not a factor specific to AVCHD. Anything that works for DV will work just as well for AVCHD (and HDV as well).
    >

  • "Add to Adobe Media Encoder queue" option very slow

    Hello,
    The new "add to Adobe Media Encoder queue" directly from After Effects is great, but it is sooooo much slower than encoding directly from Adobe Media Encoder.
    My comp is very simple : it's a 90 min. length video that I'm trying to convert from 24 to 25 frames. I need a MPEG2 export for DVD, so I can't use AE because there're no option to export to MPEG2 files in AE.
    AME announced 10 hours of encoding, but after 5 hours it was only at a third of completion. So I rendered the movie in DNxHD, then encoded in AME : 1 hour for the DNxHD file, and 4 hours for the MPEG2. Much faster!
    I run After Effects CC (12.1.0.168) and AME CC (7.1.0.74) on a windows 7 system with i5 processor and 8go of RAM.
    Anybody else encoutered this issue?

    Tento wrote:
    As for the higher encoding time of exporting to AME frome AE, do you have any clue ?
    Have you applied any effects to the footage in your After Effects comp? Are you using time remapping or the Time Warp effect? That will slow down the encode significantly. Also, what is the format of your source footage?
    Mind that, depending on what you're asking After Effects to render, encoding a comp via AME may not be as fast as using the Render Queue in After Effects. Feeding frames to AME via Dynamic Link incurs some memory overhead and limitations; for example After Effects can not render multiple frames simultaneously on different processors for Dynamic Link encodes.
    If I were you, I would try to solve the problems with AME transcoding your footage. You should bring the issue to the AME forum.  If you're fully committed to not using AME, I recommend using Premiere Pro, not After Effects, for this type of job.
    Regardless of all the above, I agree with Rick: you shouldn't need to transcode 24fps footage to 25fps for playback from DVD. DVD players will do that frame rate translation for you at playback time. But if your footage is not PAL dimensions (720x576), a DVD player won't necessarily convert the frame size, so transcoding at least the frame size is recommended. Bottom line: I would let your DVD authoring software (Encore?) handle the original file; it should do any conversions necessary when you set the DVD format to PAL.

  • Cannot find "Add To Adobe Media Encoder Queue"

    I just started in AE, and I've got a pretty good grasp on it from all the tutorials out there.
    But I hate the native rendering system in AE, I'd rather use Media Encoder like I have been for Premiere Pro.
    In the Adobe Tutorials, it says Comp > Add To Adobe Media...  but I don't have that option even available. I'm using Adobe After Affects CS6. This wasn't removed in CS6 Was it?

    In After Effects CS6, even though the Add To Adobe Media Encoder Queue command isn't present, you can add your composition to AME by other methods. Either use the File > Add command inside AME, or drag and drop your composition from After Effects to AME. Make sure to save your project first.

  • I cannot import .mov files to Premiere Pro or Adobe Media Encoder.

    I cannot import .mov files to Premiere Pro or Adobe Media Encoder.
    How do I around this problem?

    We need to know a lot more if we're going to help you.
    What happens when you try? Do you get an error message? If so, exactly what does it say?
    What version of Premiere Pro? Have you installed the recent updates? What operating system?
    Does this happen for all .mov files or just some? Has this ever worked before? What version of QuickTime do you have installed?
    Here's a page written for After Effects, but the information is relevant to Premiere Pro and AME, too:
    http://blogs.adobe.com/toddkopriva/2011/02/troubleshooting-quicktime-errors-with-after-eff ects.html

  • Media Encoder Queue Processing

    It takes much longer to export a Pr sequence as an MP4 fiel when I put it in the Media Encoder queue than it does if I Export it directly. I assume this is because once the sequence in in the queue the GPU acceleration does not engage. Is it pssible to put sequences in the queue and force GPU acceleration to engage?

    My observation is that a Pr sequence Exported then put into the Queue takes 3 times longer to complete than if I use the Export option (instead of Queue).

  • "Add to Adobe Media Encoder Queue" Missing

    Anyone know why my version of AE CS6 doesn't have the option "Add to Adobe Media Encoder Queue" ? http://t.co/UFTfFXN8VL

    The Add To Adobe Media Encoder Queue command is new in After Effects CC; it does not exist in After Effects CS6 or earlier versions. The command is available under both the File > Export and Composition menus. The keyboard shortcut is CTRL+Alt+M (Windows) or CMD+Opt+M (Mac).
    To add an AE comp to the AME Queue in CS6, you can do any of the following (which also work in AE and AME CC):
    Drag one or more comps from the AE Project panel to the AME Queue panel. (Save your project first.)
    Drag the AE project file from the desktop into the AME Queue panel. Choose a single comp and click OK.
    In AME, open the Add Source dialog: choose File > Add Source OR click the Add Source (plus sign) button in the Queue panel OR double-click in the empty area of the AME Queue panel. Choose the AE project file, click Open, then choose a single comp and click OK.
    In AME, choose File > Add After Effects Composition. Choose the AE project file on the left side of the dialog, then choose one or more comps on the right side.

  • Queuing from Premiere Pro to Adobe Media Encoder no longer working? CS6

    Hi there,
    Just very recently adobe media encoder has stopped accepting que's from premiere. I choose export in premiere, setup the export details and hit que, adobe media encoder launches, but then it flashes once (like disappears reappears, very quickly) and then it just simply does nothing. No item appears in the que. I have tried opening the premiere sequence directly from adobe media encoder but it does nothing either. If I drag the premiere project directly onto a preset in adobe media encoder, it crashes every time. (though not sure if it would of done this previous to my problem arising)
    Anyway, very frustrating as I usually work on a different project whilst media encoder is rendering something out. Now i'm stuck with huge down times as I wait till the render is finished.
    Recently updated to Mac OSX 10.8.3 - I think this is when the problem began.
    Just updated the CUDA driver to 5.0.45 but this has not changed anything.
    Working on a Mac Pro 5,1, 2x2.4Ghz 24GB RAM, EVGA GTX 660 FTW,

    Some suggestions and answer at least the 16 questions at the end of the Wiki article.

  • 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.

  • Premiere Pro error saying Media Encoder is not installed (it is)

    I'm trying to export a sequence from Premiere Pro CC 2014 to Media Encoder CC. After changing all the export settings to what I want in Premiere, I go to select the Queue button and receive the message "Adobe Media Encoder is not installed. Please download and install it to use this feature. Go to https://creative.adobe.com/apps". I have Media Encoder open right now. Any idea why they aren't communicating? I'm using a Macbook Pro btw.

    You need AME 8.0.1 to match that version of Premiere. The most up to date for both is 8.2.0. Try clicking on help-updates in each program rather that using CC updater.

  • 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

Maybe you are looking for