Latest version of Premiere crashes when exporting media to Queue

BUG REPORT TO ADOBE
Select sequence
Export Media
Export QUEUE
Export dialogue appears, but progress frozen
AME starts up
Premiere has crashed and required forced restart
PP 8.2.0 (65)
AME Build 8.2.0.54
The above are latest versions as of this morning. When will this be fixed? I cannot rely on this feature

Thanks for the suggestion - I will give that a try. This is on Mac OS X Yosemite BTW. I am now exporting via PP which always seems reliable but takes PP out of action for several hours while it exports, which is the main motivation to get it working properly with AME.

Similar Messages

Premeire Pro 7.1 crashes when using Media Encoder queue.

After I updated to the latest version of Premiere Pro (October Release 7.1), every time I export a project from premiere pro timeline and use Aodobe media encoder it crashes every time. This happens on both my MacPro and MacBookPro with two different projects, so I know its not anything on my system. I was on the phone with a Adobe tech support rep and he did a remote screen access to see first hand that it was crashing. He confirmed that there is a bug with the new update. He even installed the earlier version of PP CC and Media Encoder and it did not crash once. He told me he was going to send the issue up the chain and hopefully get a patch update soon. Has anyone else experienced this with the PP CC 7.1 update?

Heres the full report, im not sure what section you need:
Process: Adobe Premiere Pro CC [597]
Path: /Applications/Adobe Premiere Pro CC/Adobe Premiere Pro
CC.app/Contents/MacOS/Adobe Premiere Pro CC
Identifier: com.adobe.AdobePremierePro
Version: 7.2.0 (7.2.0)
Code Type: X86-64 (Native)
Parent Process: launchd [144]
Responsible: Adobe Premiere Pro CC [597]
User ID: 501
Date/Time: 2013-12-16 19:30:46.616 -0500
OS Version: Mac OS X 10.9.1 (13B42)
Report Version: 11
Anonymous UUID: A8549166-9EEE-D2C9-2FE1-5270831659F1
Crashed Thread: 5 Dispatch queue: com.apple.root.low-priority
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
VM Regions Near 0:
-->
__TEXT 0000000100000000-0000000100003000 [ 12K] r-x/rwx SM=COW
/Applications/Adobe Premiere Pro CC/Adobe Premiere Pro
CC.app/Contents/MacOS/Adobe Premiere Pro CC
Thread 5 Crashed:: Dispatch queue: com.apple.root.low-priority
0 com.adobe.Mezzanine.framework 0x0000000105d5a46e
MZ::EncoderManager::RenderMedia(dvacore::filesupport::File, dvacore::utility::Guid,
dvacore::filesupport::File, std::basic_string<unsigned short,
std::char_traits<unsigned short>,
dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, bool,
bool, ASL::InterfaceRef<BE::ISequence, BE::ISequence> const&,
std::basic_string<unsigned short, std::char_traits<unsigned short>,
dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&,
std::basic_string<unsigned short, std::char_traits<unsigned short>,
dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&,
ASL::InterfaceRef<BE::IProject, BE::IProject> const&, MZ::ExportMediaEncodeType,
MZ::EncodeSettings const&, EncoderHost::AMEWorkAreaType, dvamediatypes::TickTime,
dvamediatypes::TickTime, unsigned int) + 878
1 com.adobe.Mezzanine.framework 0x0000000105d5c469
MZ::EncoderManager::StartSequenceRender(std::basic_string<unsigned short,
std::char_traits<unsigned short>,
dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&,
std::basic_string<unsigned short, std::char_traits<unsigned short>,
dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&,
ASL::InterfaceRef<BE::IProject, BE::IProject> const&,
ASL::InterfaceRef<BE::ISequence, BE::ISequence> const&, MZ::EncodeSettings const&,
EncoderHost::AMEWorkAreaType, dvamediatypes::TickTime, dvamediatypes::TickTime,
std::basic_string<unsigned short, std::char_traits<unsigned short>,
dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&,
std::basic_string<unsigned short, std::char_traits<unsigned short>,
dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&,
std::basic_string<unsigned short, std::char_traits<unsigned short>,
dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, bool,
bool, MZ::ExportMediaEncodeType, unsigned int) + 393
2 com.adobe.Mezzanine.framework 0x0000000105d5fa39 MZ::(anonymous
namespace)::SequenceRenderRequest::ProcessSelf() + 169
3 com.adobe.Mezzanine.framework 0x0000000105d5ef60 MZ::(anonymous
namespace)::EncoderManagerThreadedQueueRequest::Process() + 64
4 com.adobe.dvacore.framework 0x0000000100370682 dvacore::threads::(anonymous
namespace)::SubExecutorImpl::CallFunctionWithExceptionHandler(boost::function<void
()> const&) + 34
5 com.adobe.dvacore.framework 0x000000010036f578 dvacore::threads::(anonymous
namespace)::SubExecutorImpl::OnThreadExecute(boost::shared_ptr<dvacore::threads::(anonymou s
namespace)::SubExecutorImpl> const&) + 184
6 com.adobe.dvacore.framework 0x0000000100385d9f
dvacore::threads::ExecuteTopLevelFunction(dvacore::threads::AllocatedFunctionT<boost::func tion<void
()> > const&) + 31
7 com.adobe.dvacore.framework 0x0000000100385a9f
dvacore::threads::WrapExecuteTopLevelFunction(void*) + 15
8 libdispatch.dylib 0x00007fff8edc02ad _dispatch_client_callout + 8
9 libdispatch.dylib 0x00007fff8edc209e _dispatch_root_queue_drain + 326
10 libdispatch.dylib 0x00007fff8edc3193 _dispatch_worker_thread2 + 40
11 libsystem_pthread.dylib 0x00007fff8974aef8 _pthread_wqthread + 314
12 libsystem_pthread.dylib 0x00007fff8974dfb9 start_wqthread + 13
Thread 5 crashed with X86 Thread State (64-bit):
rax: 0x000000003f3f3f3f rbx: 0x000000004d6f6f56 rcx: 0xffffffff00000000 rdx:
0x0000000000002265
rdi: 0x0000608000174e88 rsi: 0x0000600000170820 rbp: 0x0000000119388a70 rsp:
0x0000000119388250
r8: 0xd749167f92392da6 r9: 0x0000000119387c00 r10: 0x000000000397423e r11:
0x000000000134ccf9
r12: 0x000000003f3f3f3f r13: 0x0000000000000000 r14: 0x000000011233e270 r15:
0x00000001282e3660
rip: 0x0000000105d5a46e rfl: 0x0000000000010206 cr2: 0x0000000000000000
Logical CPU: 1
Error Code: 0x00000004
Trap Number: 14
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 1
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 861
thread_create: 1
thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=509.1M resident=245.1M(48%)
swapped_out_or_unallocated=264.0M(52%)
Writable regions: Total=1.7G written=1.2G(68%) resident=1.2G(71%) swapped_out=0K(0%)
unallocated=494.2M(29%)
REGION TYPE VIRTUAL
=========== =======
ATS (font support) 31.9M
ATS (font support) (reserved) 8K reserved VM address space (unallocated)
CG backing stores 10.7M
CG image 40K
CG raster data 48K
CG shared images 180K
CoreGraphics 8K
CoreImage 4K
IOKit 5680K
IOKit (reserved) 128K reserved VM address space (unallocated)
Image IO 408K
Kernel Alloc Once 8K
MALLOC 299.3M
MALLOC (admin) 48K
MALLOC_LARGE (reserved) 8100K reserved VM address space (unallocated)
Memory Tag 242 12K
Memory Tag 249 156K
Memory Tag 251 8K
OpenCL 8K
OpenGL GLSL 1664K
STACK GUARD 56.1M
Stack 22.8M
VM_ALLOCATE 1.3G
VM_ALLOCATE (reserved) 47.1M reserved VM address space (unallocated)
__DATA 37.8M
__IMAGE 528K
__LINKEDIT 209.9M
__TEXT 299.2M
__UNICODE 544K
mapped file 68.2M
shared memory 4K
=========== =======
TOTAL 2.3G
TOTAL, minus reserved VM space 2.3G
Message was edited by Mark Mapes to remove extraneous crash report content.

Premiere Pro CC crashes when exporting media

Rendering from a multicam sequence with in/out points set. Media consists of RED Epic 5K, Canon 7D, GoPro, and BWF sound. Output is for Vimeo 1080p 23.976. All cams and sound are set to 23.976.   Can anyone help me?
Problem signature:
Problem Event Name:          APPCRASH
Application Name:          Adobe Premiere Pro.exe
Application Version:          7.2.1.4
Application Timestamp:          52aed7f3
Fault Module Name:          mc_enc_avc.dll
Fault Module Version:          9.6.10.5101
Fault Module Timestamp:          528edcc2
Exception Code:          c0000005
Exception Offset:          00000000000e333c
OS Version:          6.1.7601.2.1.0.256.1
Locale ID:          1033
Additional Information 1:          ab6d
Additional Information 2:          ab6d8f3bdd4c5b9ba8f11cac7aa08978
Additional Information 3:          6904
Additional Information 4:          69042974d8876da55a506b3d59ff6217
[Thread title updated.]
Message was edited by: Jim Simon

Hi Jim,
I'm exporting Media into a file format suitable for Vimeo. The interesting thing is that when exporting directly from Premiere Pro CC v7.2.1, I experienced the crash, but when I queued the job in AME, it ran to completion. Trying to export directly from within PPro again causes it to crash, this time flagging ImporterREDServer.exe as the abending application.
Thanks.

Premiere crashes when linking media

Hi there,
Premiere crashes almost every time I try to link media. The project file is on the computer's C drive, which has 1TB spare, the graphics card is using its latest driver and the machine is almost brand new. The media is 4K RED files on 2TB USB 3 drives. The project also has some old incarnations of the project subsumed in it via imports.
Please find the PC specs here:
Windows 7 Pro 64 bit
16GB RAM
i7 4790 processor
NVIDIA GTX 760
If I can provide any additional information please let me know.
Any thoughts are hugely appreciated.
Thanks....

The newest versions of PrPro come with some apparently major code changes, especially how they apply some of the effects. In other words, the "apparent" effect is just the same, but the code to create that (and what it's **** behind the curtain) is apparently different, some things like that (much surmise here). The result is not all steps of all previous projects come "forward" properly. The footage, yes; the project's settings and effects, maybe, maybe not so well.
Kevin Monahan, staffer that frequents this forum and is EXCEPTIONALLY helpful here ... is a man of many years experience in pro video. He was a certified expert and trainer on FCP I believe years ago, actually on the design team for a version or so, and has done a lot of major editing work. He notes that no matter what anyone says about it, he ALWAYS taught the Bible of Pro Editing ... no project ever got updated software while in process. For the exceptions, a new project file would be created in the newer software version, then each asset or group of similar assets got brought "forward" individually and tested for proper operations. After everything was working, THEN the project could officially take off in new software versions.
With so many continual projects these days, and with continual "upgrades" of software, this is a right b*tch to follow. But still wise. Especially as a project nears completion, it's wise to leave it in whatever version it's in. For someone like me who's got one machine for all editing purposes, going back and forth between software versions is a much bigger pain than say if I had a pair of editing machines, one running newest, one just back a bit, and then leap-frog them as things move forward. There's also cloning and swapping discs as a way to change software ... and of course CS6 and any one of the CC versions can co-exist on the same machine "live" at any time. Multiple CC versions ... no. Only one CC version at a time.
USB3 may not be the reason for your crashes, but it could be part of the chain of events. The newest versions of PrPro as noted are heavier apps than before, demanding more resources ... and for that demand, capable of new tricks. Some of the Old Things they actually do differently, so what was once able to run the older versions has nothing to do with being able to run here & now. It's an unfortunate part of modern life with these blamed computer tools. One that someone like me operating on a rather smaller hardware budget than many of the folks who post here do finds ... difficult, rather challenging ... but there it is.
One suggestion ... when migrating a project or it's assorted bits & pieces "forward" ... I do suggest copying any assets no matter what they are (sequences, stills/graphics, footage, sub-clips, anything) into new folders created for that new project, then importing them into the project as you copy them forward. Check out say, the footage scrubbed in the source monitor or what not ... the sequences individually scrubbed on the timeline, that sort of thing. If you hit a glitch it's easy to know what that glitch is related to rather than hunting through gigs of project stuff to find one dang frame or subclip or effect that's killing the whole thing.
Neil

Premiere CC 2014 crashes when exporting via the Queue

Having issues exporting from Premiere CC 2014 via the "Queue".
My system:
Dell Precision T5600 Workstation
Windows 7 Pro 64 bit
Xeon E5-2680 @ 2.7 GHz processor
Nvidia Quadro 4000 graphics card, driver ver 347.25
32 GB RAM
Creative Cloud 2014
Premiere Pro CC (2014) Up to date
Media Encoder CC (2014) Up to date
Exporting via the Queue has work just fine in the past. Had this issue awhile back and cleared some cashed files which fixed the problem but don't remember what I did. I have uninstalled and re-installed Premiere. This took care of the problem for awhile, but now the same issue has cropped up again.
Symptoms: When exporting a sequence from Premiere, clicking "Queue" launches Media Encoder but it doesn't completely hand off the sequence to Media Encoder. Premiere locks up, leaving a small blank window open named "Export Media (Not Responding)". It never completes the hand over to the Media Encoder queue. If I reverse the process by launching Media Encoder and import the same Premiere timeline directly into the Media Encoder queue, it loads and renders just fine. If I do an "Export" from Premiere, it works just fine. This seems to indicate something is going on with the exchange between Premiere and Media Encoder. I have this issues on multiple projects.
Any help would be greatly appreciated.
Thanks, Dave

I'm not clear why you couldn't run it in Administrator mode ... right-click the program icon, Properties -> Compatibility, near the bottom, run in administrator mode ...
Neil

Premiere crashes when exporting to Soundbooth

I've searched everywhere for an answer but can't find anything. When I try to export an audio file from Premiere to Soundbooth, Premiere hangs.
The only change to my system recently was I downloaded some Matrox codecs. Anyone have any ideas or solutions? I'm using Win 7. Thanks

Thanks, I appreciate the quick response. I don't have a Matrox card but I was working on a project that the client used a 1920 x 1080 Matrox codec. It was version 10. My Premiere is version 5.03. The audio file is just an HDV file that I was trying to correct audio on. I thought it might have something to do with Dynamic link but I was able to import AE comps.

Media Encoder crashes when exporting from Premiere Pro

Media Encoder crashes when exporting from Premiere Pro. I am queueing multiple files for export and Media Encoder will crash. The computer system has 32GB of RAM and the videos export fine in Premiere, but that requires exporting each one individually. Each video file is being down converted and some can be quite long (upwards of 3-5 hours). Nothing else is running on the computer that would take up memory.
Any idea why Media Encoder will crash?

Try turning off GPU acceleration.

Premiere Pro CC 2014.2 crashes when "locating media"

The problem;
Premiere Pro CC 2014.2 crashes when "locating media". I am working on a project that has not given me any problems for the last 200 hours. About a week ago I notice that the .proj file size was 276mb and found this odd because my largest project to date was never larger than 80mbs. I thought that the premiere was running slow because of the project size. As luck would have, when my client made their their final changes 2 days ago, I opened the project and premiere would hang on the locating media window and then would crash. I called Adobe and spent an hour on the phone with them to no avail.
Project workflow
- 700gb of 5d footage
- 20 sequences under 5 minutes
- Dynamically linked files with AE
- Warp Stabilized about a dozen clips of under 5 sec
- On every sequence color correction adjustment layer with RGB Curves, Three way color corrector and sharpen filter
- I kept old versions of the sequences (I was in version 5 before the crash)
What I have tried;
- Unsuccessfully tried to open auto-save files for this project.
- Successfully opened other older non relevant project
- Removed Mercury playback engine in the project settings
- Cleaned out media cache database through pp in media Preferences
- Manually deleted cache files in /Common/Media Cache Files and /Common/Media Cache
- Tried importing sequences into new .proj file; it would crash as a result.
What "worked".
I was able to open it on another computer. save it under another file name. bring it back to my original computer and open it without problem. I lost about 3 days working through this problem, I missed my deadline. and angered the client. I was able to use a friends IMAC to "fix" the problem, however I can't always count on him being there if it happens again.
Questions.
- What the hell happened? Why could I open it on one computer and not on the other?
- Is there a way to fix a corrupted .proj files on a PC?
- What should the average file size be, before it becomes unstable? (I'm pretty that my file size was bloated by all the previous versions of the sequences)
Windows 8.1 64bit
Premiere 2014.2
Intel Quadcore i7-4770 3.40GHz
16gb Ram

Hi,
I would suggest the following steps:
http://blogs.adobe.com/kevinmonahan/2014/09/10/premiere-pro-cc-freezing-on-startup-or-cras hing-while-working-mac-os-x-10-9-and-later/
Run a disk permission repair on your boot drive, and
Reset Home Folder permissions and ACLs Error | Apple Support Communities
Thanks,
Rameez

What can I do to stop Adobe Premiere Pro CS6 from crashing when exporting?

Regardless of whether I have a new project file or an existing one, edits or no edits, whenever I click export, Premiere Pro simply crashes. Same for Media Encoder - can't even open that one. I have all of the latest CS6 updates installed, the computer is brand new as of two weeks ago - OSX 10.9.1, NVIDIA GeForce GT 650M 1024 MB. The only way I've been able to export is through a backdoor: I use the dynamic link in After Effects, then render out my sequences there. Help?

OSX Crash http://helpx.adobe.com/creative-cloud/kb/ame-premiere-crash-launch-export.html

Is ILife 11 the current version today? Will its purchase upgrade my Iphoto 8.2.1 to Iphoto 11? I have a Macbook, Maverick and Iphoto is crashing when exporting photos. I understand ILife is the way to fix it.

Is ILife 11 the current version today? (May 2014). ILife 11 on Amazon appears to be 3+ yrs old?
When searching for ILife 11 on the Apple Store, I am directed to a separate purchase of Iphoto version 9.
Somewhat confusing, Apple is always so clear with these things.
The goal is to upgrade my Iphoto 8.2.1 to Iphoto 11.
I have a Macbook Pro, Maverick 10.9.2 and Iphoto is crashing when exporting photos.
I understand ILife is the way to fix it.
Thanks!

The current version of iPhoto is iPhoto 9.5.1., and it is the latest version of iPhoto '11.
If you are running Mavericks 10.9.2, you can buy iPhoto 9.5.1 from the AppStore - it is the currently sold version.
The iLife bundle is called iLife '11, and the iPhot version in iLife '11 is iPhoto 9.x.x. - that is confusing allright
I have a Macbook Pro, Maverick 10.9.2 and Iphoto is crashing when exporting photos.
While it is certainly useful to upgrade to the current iPhoto version to be fully compatible with MacOs X 10.9.2, there may be a differnet reason for the crashes. Is there an error message with the crashes? When did these start? Did you import new photos or videos? Install other software?

Any idea when GTX 970's will be added to the supported list in the latest version of premiere? id like my cuda.

Any idea when GTX 970's will be added to the supported list in the latest version of premiere? id like my cuda.

I Too would like to know. I've finally finished upgrading my rig with a 970, and as far as I know, there's been some good things and not so good things. (I'm on CC 2014.1 with Windows 8.1 Pro) I'll post screenshots when I get back to my computer.
FIrst things first: Make sure to install the CUDA specific to the 970/980. They have their own toolkit, that I believe people miss. I installed this, and then manually added my card to te supported cards file in the Premiere, AE, and Speedgrade files. When I opened Premiere, it's automatically set to use CUDA acceleration, so I believe it's supported there. I wasn't able to test this, unfortunately. I will confirm this soon.
Second, when I open After Effects, the Previews preference pane states my card is supported, and all the info below it seems correct, like the shader model. The only thing that seems off is the OpenGL, which is set to 2.1.2 NVIDIA or something of the like instead of 4.x, but I believe its an NVIDIA optimized driver, so I'm not too concerned. The big thing for me is the error message that I recieve when I try to enable Ray-traced 3D. I recieve a compilation error, followed by another message, and I have no clue what to do with them.
I'm really hoping Adobe releases an updates that bring full native support for these cards, as I'm running an class at my high school where I need to build three machines, all of which will have a 970 inside, and if Adbe doesn't support these cards, I'm kind of screwed as the pipeline is based completely in Adobe with its Dynamic Link and CUDA acceleration. Come on Todd, we believe in you!
TL;DR Yes, CUDA acceleration should work within Premiere Pro CC 2014.1, but make sure to install the correct CUDA drivers from NVIDIA (they should be in the yellow boxed text on the downloads page)

Premiere Pro CC crashes when importing media.

Premiere Pro CC crashes when importing media. Every time. Driving me crazy.
It crashes as soon as the Windows dialogue box comes up.
Does it in new projects and in a project I created and imported into just fine 2 days ago.
Have rebooted.
Running Windows 8.1 on Samsung Series 5 ultrabook Intel i5 - not too sure what else to say about other settings:
I did have a problem the other day when Windows was crashing when browing a large folder of largish images and video clips but it went away when I put images and videos in separate folders.

Thanks for reply.
Point taken but I've been using it for over a year for simple edits (5 min films) in PPCC just fine. Can't even do what I could do the other night now.
Simple folder with a few jpegs and movies in it. In fact it just crashes before I even got to another folder.

Crystal Crashes when exporting to PDF

Hi Experts,
Crystal reports crashes when exporting a report to PDF. I am using Crystal Reports for SAP Business One, what could be causing this..is it a patch level problem ?

Hi,
Please check this thread http://scn.sap.com/thread/3303863.
What is your B1 version and PL?
Thanks & Regards,
Nagarajan

Why can't I download latest version of premiere through the creative cloud app?

I just purchased a new computer and synced my creative cloud account. It didn't download the latest version of premiere and says that I am up to date (which I am not.) Anyone know why this is? and how to access the update for version 6.0.2?

CC desktop lists applications as "Up to Date" when they are not
-http://helpx.adobe.com/creative-cloud/kb/aam-lists-removed-apps-date.html
-and added step https://forums.adobe.com/thread/1529654
But... since CS6 is not part of the Cloud, unless you installed it using the "previous" process, the above may not apply
-Previous via Cloud http://helpx.adobe.com/creative-cloud/help/install-apps.html#previous

I have project that I created in Macromedia Dir 7 I have purchased the latest version of Premiere

I have project that I created in Macromedia Dir 7 I have purchased the latest version of Premiere Pro, from the advice of the Adobe sales team. Now I need to bring the project in. I am both interested in the process as well as looking for some one to work with me $ on this project

I agree with Ann, but what does PPro say when you try to open or import your "foreign" project file?

Latest version of Premiere crashes when exporting media to Queue

Similar Messages

Maybe you are looking for