Premiere Pro CC 2014 and Media Encoder CC 2014 Crashing constantly

Running out of options and ideas...
Symptom: Every time I work on any project in Premiere Pro CC 2014 or try to render out in Premiere Pro CC 2014 or Media Encoder CC 2014, the software crashes after 2-3 minutes of use/rendering when the GPU is enabled in Premiere/Media Encoder, or after 5-10 minutes of use/rendering in software only mode. The crash is a software crash, Windows continues to run fine.
I have tried all the standard list of steps that adobe reps post on threads like these - clearing media cache, software only on render, new project, etc. https://helpx.adobe.com/x-productkb/global/troubleshoot-system-errors-freezes-windows.html
Windows event is not that helpful to me:
Faulting application name: Adobe Premiere Pro.exe, version: 8.2.0.65, time stamp: 0x5486db4a
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007ff5ecb4de40
Faulting process id: 0x1dc8
Faulting application start time: 0x01d04a503cd82df2
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
Faulting module path: unknown
Report Id: cacdfbab-b717-11e4-826d-8863dfc268bc
Faulting package full name:
Faulting package-relative application ID:
I have wiped adobe off the machine and reinstalled - same problem. I have tried projects that crash the machine on other machines and it works fine.
The machine is new, clean install and runs everything else great - 3ds max, high res games, scientific computing - max memory use, etc.
Spec:
5K iMac running bootcamp and Windows 8.1
Intel Core i7-4790K @ 4.0 GHz
32 GB ram
1TB SSD
AMD Radeon R9 M295X 4GB GDDR5
I have used this bootcamp/imac configuration for 5+ years on 3-4 machines and everything has always just worked great. Guess it was my time for a problem, but I'm open to new ideas to try...
Finally - I hope someone from Adobe reads this. I have spent 2 nights on the phone with support. The first night I got an over confident answer that it's a gpu driver issue, just go with software only (no luck - same crashes and different drivers aren't solving the problem). Tonight I was hung up on "by accident" as the agent looked up my video card after waiting 15 minutes to talk to someone, only to be hung up on a second time while on hold after calling back and waiting 20 minutes (because I assume the Adobe call center closed). No message to say so, just hung up on. An overall very disappointing experience.
Thanks in advance to anyone with ideas on things to try,
Cheers!

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.

Similar Messages

Premiere Pro CC 2014 and Media Encoder CC 2014 not completing encode.

This is a project that I have been successfully encoding in short segments until now. Now when encoding, session runs about 10-15 minutes and then ends without error messages.
Removing effects and changing to Mercury PB Engine SW did not help.
Also tried disabling metadata as suggested in another forum.
When CUDA used, logged as "Encoding failed." When Mercury SW used, logged as "File Successfully Encoded" even though video file is only 6 KB with no content.
Premiere Pro Build 8.1.0 (81)
Media Encoder Build 8.1.0.122
Windows 7 Professional
Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
8 GB RAM
NVIDIA GeForce GT 610 (9.18.13.3788)

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.

Upgraded to CC 2014 and Media Encoder doesn't work now.

Using a mac with mavericks, all updated. Upgraded to Premiere Pro CC 2014 and Media Encoder CC 2014. But when I want to launch it... it won't open.
Help?

JUST FOR MAC USERS - Some 10.9.3 links
-next link says After Effects, but check YOUR permissions !!!
-http://blogs.adobe.com/aftereffects/2014/06/permissions-mac-os-start-adobe-applications.ht ml
-Mac 10.9.3 workaround https://forums.adobe.com/thread/1489922
-more Mac 10.9.3 https://forums.adobe.com/thread/1491469
-Enable Mac Root User https://forums.adobe.com/thread/1156604
-more Root User http://forums.adobe.com/thread/879931
-and more root user http://forums.adobe.com/thread/940869?tstart=0
-Mac 10.9.3 and CS6 https://forums.adobe.com/thread/1480238

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.

Premiere Pro CC 2014 and Medie Encoder CC 2014 problem

Hello there,
Every time that I am willing to export my project my Premiere Pro CC 2014 stop responding all together. I tried the short cut (Commend+M) or going through the Manu bar. the result is the same, Premiere Pro CC 2014 just freezes and does not respond to anything till I force quit it and restart it allover again. I tried exporting from Premiere Pro it self, without using Media Encoder, but the problem remains the same.
I am using the new Mac Pro. I heard Adobe Premiere Pro is experiencing problems with the New Mac Pro. Is that true? Or is there other issue?
Thank you and looking forward to hear back,
Maruf

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.

Use Premiere pro cs5.0 with media encoder cs5.5

Is it possible to use media encoder cs5.5 together with premiere pro cs5.0?

I have read that each version of Premiere Pro is a distince install, into a separate folder
So, you may have CS5 and CS5.5 installed at the same time, and neither one gets in the way of the other
As far as I know, that means that CS5 will ONLY look for and use the products installed in the CS5 area
So, no, I do not think any part of CS5 will work with any part of CS5.5

Premiere Pro not understood by Media Encoder properly

When I am in premiere pro I have a PSD layered file that is animated on the time line as a lower third. Everything in the timeline is fine. If I export and encode from premiere pro it encodes fine. However, if I send to queue and encode in adobe media encoder it encodes changing the scale of the psd layers from the image back to the original position of the psd. This seems like the encoder does not understand the latest update in Premiere properly. Anyone have any ideas or a way to resolve this on this end? (Below are two images one is showing the lower third PSD from within premeire, the other is showing what the media encoder is doing to the PSD lower third)
Thank you for any sugestions.

Hi MRJay,
I had a similar issue only when using 3rd party plugin (Creative Impatience) that would go all catywhumpus on Encoder Queue outputs...it would mess with certain images or text that were not necessarily matching the project proportions (e.g. crop them, or ignore 1/2 of my Feathered Crop, etc.)
The solution was bizarre, and likely source-code default setting based...
After going to Media-->Export and when in the Encoder interface--before Queueing-- find a section on your timline with the scroll controls where the graphic is, make sure you are in Source Tab (top left), goto Crop Proportions; Use the drop down tab to actually set the Output dimension to what your sequence is (you won't have to actually export with this setting) and then switch to the Output tab. Does it now appear correct? That's it...undo the Crop Prop. and output normally. Hope this helps...

Does Premiere Pro subscription come with Media Encoder?

It's amazing how there is no means to get a hold of Adobe to ask a simple sales question. It looks like the only option is for their customers to provide the answers. Not promising for long-term support...
Does anyone know if a single product subscription to Premiere Pro CC also provides Adobe Media Encoder as part of that $20 monthly price or is AME considered a second app, thus a $40 price tag? Secondly, is AME available as a single app purchase apart from Premiere Pro or AE? Just trying to figure out what my options are. Thanks in advance.

It doesn't come as a separate app. It's part of the Premiere Pro app.

Err A12E5 when trying to download Premiere Pro - really just need Media Encoder

I've tried different methods of downloading AME, both as a stand-alone and as part of Premiere Pro (which I don't need.) I get the error A12E5. Please advise.

Hi,
Please try this
http://helpx.adobe.com/creative-cloud/kb/troubleshoot-cc-installation- download.html
Under downloads and updates you will see the steps to resolve the error A12E5.
Thanks
Kapil

Premiere Pro CC 2014 update and Media Encoder update fail to install

Hi -
I've been updating my CC applications. But PP CC 2014 and media Encoder say: "UPDATE FAILED". Naturally I cannot get through to Abobe. Does anyone have a suggestion?
Harry

Hi Harry,
Sorry, chat and phone support are closed on weekends for the video queue. We only have general support open on weekends. It's been this way for years. Sorry if that caused some inconvenience.
I hope you have solved your issue. If on Mac, you can update NVIDIA drivers in the NVIDIA control panel in System Preferences. AMD GPUs are merely updated when you update OS X.
Also, please check out the doc that was recommended: Installation failed. Error U44M1P7 | Updates
If you are still having trouble, contact us Monday through Friday 7AM-7PM PST here: Contact Customer Care
If you can't get your issue solved, send me a PM and I'll try and help.
BTW, I am not sure why your post is marked as correct. I do have that ability but did not do that. Sorry for that.
Thanks,
Kevin

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

Premiere CC 2014 hangs when sending sequences to Media Encoder CC 2014

Whenever I try to send a sequence from Premiere Pro CC 2014 to Media Encoder CC 2014, Premiere immediately freezes and becomes unresponsive. AME seems to still be running just fine.
I've tried the following troubleshooting steps:
– Clearing the media cache.
– Clearing and moving the scratch disks.
– Deleting all render previews and re-building them.
– Completely re-installing all of Adobe's Creative Cloud suite.
– Importing the at-question PPCC14 project file into a fresh PPCC14 project and importing only the sequence I need to export.
– Dragging and dropping the at-question Premiere sequence into AME.
– Opening only AME and trying to drag the entire Premiere project file from Finder.app into AME's render queue. (This happens to work, as a matter of fact, however something strange happens once the sequence is in the AME queue. It pops up just fine, I can change the render settings and file export location, but when I click the green play button at the top right, nothing happens. AME doesn't hang or freeze up or anything, it's just that nothing happens. No prep, no nothing – very strange.)
– Uninstalling CUDA completely and tried using only OpenCL and software-only rendering engines.
– Opening the same at-question project on an entirely different computer.
– Trying to export from PPCC14 itself.
– Tried opening up an entirely different PPCC14 project and exporting – worked perfectly. So it must be something with this specific project file.
I eventually got it working (honestly, I'm not even sure what I did – at that point it felt like I was in a zombie state after four hours of troubleshooting and was just repeating troubleshooting steps because I was trying to hit a deadline with this export.) I was able to export it directly from PPCC14 – I was never able to get it to work with AMECC14, however.
Other miscellaneous noteworthy things: This project I'm trying to export is massive – it's a feature documentary that's about 2 hours in length. It's very complex in its edits, has a mixture of ProRes 422 files and .MTS files, and the entire project is reading media from three separate USB 3.0 hard drives. I know that's not the ideal workflow, but it's been doing just fine until this last time I tried to render out the latest export for our client.
Thanks in advance for anyone's help.

I've tried importing into a new blank project, but that did not seem to work. I then tried selecting the sequence in the bin and exporting that as a "Simplified Project" via the File menu. That still does not work when sending the sequence to AMECC14, but it does work when I render straight from PPCC14.
I have also found that as long as I give it enough time to load up and all that, I seem to be able to export just fine from PPCC14 itself – I'm still getting the freezing/hanging when trying to send to AMECC14 however.
Thanks for the help so far Cgunningham – I really appreciate it. I'll keep following up here if I find anything else new out.

Adobe Media Encoder CC 2014 has NEVER opened on my computer.

Can somebody please help with this?
Process:         Adobe Media Encoder CC 2014 [468]
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:         ???
Code Type:       X86-64 (Native)
Parent Process: launchd [174]
Responsible:     Adobe Media Encoder CC 2014 [468]
User ID:         501
Date/Time:       2014-08-28 07:43:01.054 +0100
OS Version:      Mac OS X 10.9.4 (13E28)
Report Version: 11
Anonymous UUID: 50100364-D4BE-B73C-C1BB-D5ADEEFB650C
Crashed Thread: 0
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Application Specific Information:
dyld: launch, loading dependent libraries
Dyld Error Message:
Library not loaded: @executable_path/../Frameworks/AdobeACE.framework/Versions/A/AdobeACE
Referenced from: /Applications/Adobe Media Encoder CC 2014/Adobe Media Encoder CC 2014.app/Contents/MacOS/Adobe Media Encoder CC 2014
Reason: no suitable image found. Did find:
/Applications/Adobe Media Encoder CC 2014/Adobe Media Encoder CC 2014.app/Contents/MacOS/../Frameworks/AdobeACE.framework/Versions/A/AdobeACE: truncated mach-o error: segment __LINKEDIT extends to 1416784 which is past end of file 1416782
/Applications/Adobe Media Encoder CC 2014/Adobe Media Encoder CC 2014.app/Contents/MacOS/../Frameworks/AdobeACE.framework/Versions/A/AdobeACE: truncated mach-o error: segment __LINKEDIT extends to 1416784 which is past end of file 1416782
Binary Images:
    0x7fff6f3ef000 -     0x7fff6f422817 dyld (239.4) <042C4CED-6FB2-3B1C-948B-CAF2EE3B9F7A> /usr/lib/dyld
    0x7fff8ff53000 -     0x7fff8ff53fff com.apple.Carbon (154 - 157) <45A9A40A-78FF-3EA0-8FAB-A4F81052FA55> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
    0x7fff92ed5000 -     0x7fff92ed5fff com.apple.Cocoa (6.8 - 20) <E90E99D7-A425-3301-A025-D9E0CD11918E> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
    0x7fff92faf000 -     0x7fff92faffff com.apple.CoreServices (59 - 59) <7A697B5E-F179-30DF-93F2-8B503CEEEFD5> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
    0x7fff92fc7000 -     0x7fff932c5fff com.apple.Foundation (6.9 - 1056.13) <2EE9AB07-3EA0-37D3-B407-4A520F2CB497> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x7fff96923000 -     0x7fff9698ffff com.apple.framework.IOKit (2.0.1 - 907.100.13) <057FDBA3-56D6-3903-8C0B-849214BF1985> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
    0x7fff97732000 -     0x7fff9798cff9 com.apple.security (7.0 - 55471.14.8) <EA03E140-2509-3A07-8440-2DC97C0D478B> /System/Library/Frameworks/Security.framework/Versions/A/Security
    0x7fff9951c000 -     0x7fff9951cfff com.apple.ApplicationServices (48 - 48) <3E3F01A8-314D-378F-835E-9CC4F8820031> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
Model: MacBookPro8,3, BootROM MBP81.0047.B27, 4 processors, Intel Core i7, 2.2 GHz, 16 GB, SMC 1.70f6
Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 512 MB
Graphics: AMD Radeon HD 6750M, AMD Radeon HD 6750M, PCIe, 1024 MB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1333 MHz, 0x859B, 0x43543130323436344246313333392E4D3136
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1333 MHz, 0x859B, 0x43543130323436344246313333392E4D3136
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 (5.106.98.100.22)
Bluetooth: Version 4.2.6f1 14216, 3 services, 23 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: M4-CT512M4SSD2, 512.11 GB
Serial ATA Device: MATSHITADVD-R   UJ-898
USB Device: FaceTime HD Camera (Built-in)
USB Device: Hub
USB Device: BRCM2070 Hub
USB Device: Bluetooth USB Host Controller
USB Device: Apple Internal Keyboard / Trackpad
USB Device: Hub
USB Device: IR Receiver
Thunderbolt Bus: MacBook Pro, Apple Inc., 22.1
I, of course, have no idea what any of the above means. Please help.

Looks like one component in Media Encoder is either missing or corrupted somehow.
Could you uninstall Adobe Media Encoder CC 2014 and please make sure all files are deleted after uninstall? Then, please try re-installing it.

Media Encoder CC (2014) Update Error (U44M1P34)

Just did a batch of CC updates and Media Encoder CC (2014) failed with error U44M1P34. Any suggestions on how to fix this?

U44.. update error http://forums.adobe.com/thread/1289956 may help
-more U44.. discussion http://forums.adobe.com/thread/1275963
-http://helpx.adobe.com/creative-suite/kb/error-u44m1p7-installing-updates-ccm.html
-http://helpx.adobe.com/creative-suite/kb/error-u44m1i210-installing-updates-ccm.html
or
A chat session where an agent may remotely look inside your computer may help
Creative Cloud chat support (all Creative Cloud customer service issues)
http://helpx.adobe.com/x-productkb/global/service-ccm.html

Premiere Pro CC 2014 and Media Encoder CC 2014 Crashing constantly

Similar Messages

Maybe you are looking for