Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Exporting to Media Encoder crashes Premiere Pro CC 2014

Explorer ,
Sep 03, 2014 Sep 03, 2014

Greetings,

I am experiencing a problem with premiere off and on. Right now it is an on problem. When I am exporting from Premiere Pro CC (and CC 2014) it will intermittently crash Premiere. I have tried this with several different audio and video formats (AVI [Lagarith and uncompressed], WAV, H.264, MPG2, AAC, etc). At the moment, every time I go to export to queue it locks up and hangs on the "Preparing data for export..." Media Encoder Launches and then it just freezes. I get "Problem Even Name: AppHangB1" over and over. Sometimes a full restart will fix this temporarily and sometimes it goes away for a long while. I managed to get a few sequences exported and then it just kept freezing on every PP CC restart.

Here are my system specs:

Premiere Pro CC (up to date)

Win 7 64bit (up to date)

i7 970

24GB Ram

NVIDIA 470GTX (driver up to date)

3 x 1.5TB internal

4TB internal

3TB internal

12TB RAID 5 via USB 3.0

USB 2.0 and 3.0 drives

FireWire audio device (M-AUDIO FireWire1814)... although, I am not using it for playback. It is connected.

Footage is from C100 H.264 .MTS, H.264.mov from 7D, and H.264 .MOV from iPhone.

All stock video plugins with a few third party audio plugs.

This problem happens with and without third party plugs, but it happens that this project uses them.

I have chatted with Adobe help twice about the matter and nothing has come of it. Log out, log in = same. Restart = same (sometimes), create new user account = same, and so on. The only thing I haven't done is completely re-install premiere, which seems a bit overkill. One of the reps said he would get back to me in a few days after he watched the issue via screen share. Never heard back.


I get the sense that this has something to do with PProHeadless.exe not launching or not running properly. When the crash happens on a fresh restart of PP CC 2014 PProHeadless is not running. I can start PProHeadless and it will send sequence to media encoder. When I try to export another sequence from the same project it crashes and I see another instance of PProHeadless launched.

Also, once the projects are exported to Media Encoder, I can encode them to any format with no problem. The problem is getting the sequences there!

Is there anything that I am overlooking here?

Thanks for the help!

14.3K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Oct 15, 2014 Oct 15, 2014

I can also confirm that this problem, which has caused me no end of grief over the last few months, is successfully resolved by removing any audio track effects. Instantaneously.

I'm using Mac OSX 10.9.5 - Macbook Pro Retina 2014, 2.6ghz i7, 16gb Ram - Premiere Pro CC 8.1.0

The most frustrating thing is, I only started using the audio track effects panel because the "denoiser" effect was making abnormal noises when applied directly to clips/layers. It seems like one stupid workaround after another...

I must say I do love the CC but sometimes it's just so annoying and saps so much of my time/energy trying to fix basic problems! *sigh*

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Oct 15, 2014 Oct 15, 2014

Shade, does the crash still happen if you apply the same audio effects to clips? I just tried it myself and the same crash happens whether the effect is applied to tracks or clips.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Nov 21, 2014 Nov 21, 2014

This issue is STILL NOT FIXED???? It's really a pretty major bug, and dragging sequences into AME is NOT a great workaround!! If I don't save the project before dragging the sequences, AME apparently still uses the last saved version. Besides, it's just annoying to manage the screen space so I can even do the dragging.

Adobe CC started out as a great idea, but between a confusing "upgrade" to CC 2014 (which installed totally new apps and left the old apps untouched, thus requiring a bunch of manual housecleaning), required conversions of PPro project files (TWICE), an uglier and more limited UI color scheme, and now this major exporting bug still unfixed after almost three months - It has been a huge source of frustration. I hope Adobe is not thinking that they've gotten all of us "on the hook" with the CC model, and therefore can afford to care less about our user experiences...

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Dec 05, 2014 Dec 05, 2014

I also have been having this issue. Seems like it could be due to audio effects, since I am using a waves L2 as a master limiter. But, I've never had this issue in past versions of Premiere where I'm using the same plugin.

A WORKAROUND I've found that's not too painful, is just using the 'export' feature instead of 'queue'. Seems to always work on projects that crash sending to media encoder. As someone noted, I've had to get used to pressing save before I try to export anything because if it crashes you lose all your unsaved changes.

Hopefully this will get solved quickly.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Dec 10, 2014 Dec 10, 2014

I'm getting the same error and using the same workaround. Seems to be the multiband compressor izotope plugin causing it for me.

Win 8

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 12, 2014 Dec 12, 2014

I have experienced the same issue with 1 particular project, where all others seem to happily queue. After going through this and other related posts, decided not to try to go out of Premiere with my sequences, but instead to import the sequences from AME instead. Has so far worked a treat!

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jan 19, 2015 Jan 19, 2015

I had three different sequence in three different projects.  Two of the sequences would queue up and export to AME just fine ... the third project, locked up Premiere everytime I tried to queue the sequence to AME.   I traced the problem to having the "Loudness Radar" set as an effect on one of the audio tracks.   I removed the effect, queued the sequence and VOILA, the sequence exported to AME without issue or locking up Premiere.   It would seems that certain audio plugins are causing issues with the communication between Premiere and the AME

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
Jan 26, 2015 Jan 26, 2015

Want to say I'm experiencing this nonsense also in cc 2014 with the latest updates. I get the white "export media" box when queueing to AME. I am only exporting a work area of not even 30 seconds from my sequence, and none of the audio clips have any effects on them.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jan 30, 2015 Jan 30, 2015

Same here! Experiencing this problem since the latest Updates.

File -> Export -> Media -> add to Queue

AME opens and Premiere crashes at "Preparing data for export..."

Adobe CC 2014.2

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Feb 18, 2015 Feb 18, 2015

Have the same problem on some projects.  I have 5 new loaded windows 7 machines with up to date software on an ISIS system. This problem is repeatable on all machines.

I found it was some effects. The effects that I found so far that will not allow queue to work are the audio single and multi band compressors. The multiband(legacy) worked. clean sequences work.

I made a clean project  with 3 1 minute clips and a 15 sec No Effects  queued OK.  Added the single band compressor on the 15 sec clip. Export>Media>Queue Premiere Pro locked up white screen. Force close. Added multiband compressor to the 15 sec clip. Export>Media>Queue Premiere Pro locked up white screen. Force Close. Added the multiband compressor(legacy) Queued OK. Made a copy of one of the projects that would not queue. Removed all the effects It worked. Queued OK.

Haven't had time to try more to see which others have problems. found this thread  iZotope Audio Effects Crash Premiere (2014.1) The single and multiband compressor effects are breaking the queue function

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Feb 19, 2015 Feb 19, 2015

I'm having exactly the same problem. I also played with the multuband compressor and audio level radar. However, none of these effects were used so far.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Feb 19, 2015 Feb 19, 2015

To be a bit more constructive: if I start the AME and then just do "Add source" it works fine. That's actually much quicker than waiting for 3000 clips to load first in Premiere and then doing export.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Mar 19, 2015 Mar 19, 2015

Yep, been dealing with this all day yesterday and I've been on the phone with tech support 3 times now about this issue. It's funny, while on the phone with them things seemingly get resolved, and then after hanging up (88 minutes the last time and that was the second call of the day), the problem returns, like it's a ghost in the system playing tricks on me.

Thing is, I only really have this problem with one project (so far). When I open others, it seems fine. I only have three projects I've done so far, but this one...this one is a big one - and I can't understand what makes Premiere crash. Frustrating to say the least. I've given up, I guess I'll just continue to export sequences one at a time like a barbarian.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Mar 23, 2015 Mar 23, 2015

This issue went away for me a while ago, but today it was back! PPro was totally frozen on "preparing data for export" and I had to eventually force-quit. It was very frustrating because I didn't save the project before trying to export, and of course there was no auto-save that captured what I had just done, so I had to redo about 10 minutes worth of work.

I restarted the machine and tried again, and it froze again. So it's back to drag-and-drop into AME, for now.

WHY IS SUCH A HUGE BUG STILL NOT FIXED AFTER SEVEN MONTHS?????????????????????????????????

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
Mar 23, 2015 Mar 23, 2015

I think i personally narrowed it down to something to do with audio files. Seems this only hangs when sending to Encore when if I also try it out exporting right from Premiere, that I get a box saying that its rendering audio files before it starts the actual render. Any project where that is the case, it's guaranteed to crash if you don't export right from Premiere. I'm not sure what happens though if you render the timeline preview before queueing to Encoder.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Mar 23, 2015 Mar 23, 2015

I've been working on this project for a while, and didn't so anything too special today such as adding new types of effects. One thing that might have made a difference was that I was queueing two sequences to AME instead of one. Hmmm...

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
May 30, 2015 May 30, 2015

I'm experiencing these issues using AME when exporting from Premiere Pro CC 2014 as well.  Only certain sequences/media crash Premiere though. I have a particular timeline with video and Photoshop elements that make Premiere unresponsive. All others seem to work fine.  Which makes me think this is not a hardware issue which is why I didn't waste my time posting my computer specs.   I did some experimenting and found when I exported just the Photoshop elements in a sequence Premiere sent it over to AME just fine. Once I added the video (.MTS) and tried to export it crashed it. So.. It seems there is an issue when exporting the .MTS video file.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Engaged ,
Jun 02, 2015 Jun 02, 2015

UNBELIEVABLE, ABODE... UNBELIEVEBLE...

I find myself typing that same sentence in CAPS almost every week now for a different bug... ADOBE CC is now officially the biggest joke in the industry.

When I removed the audio effect it resolved the problem. This bug JUST started for me and I have not done any updates on either PP or AME.

To say that I'm over PP would be an understatement. I can't wait to see it as a legacy application soon because that's exactly what PP's future looks like if the next update does not fix EVERYTHING. Adobe really needs a miracle this time... 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jun 20, 2015 Jun 20, 2015
LATEST

[moderated] Did you ever thought about this could be an issue caught by the PLUGIN and not just by Premiere?

Stop flaming!

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jun 04, 2015 Jun 04, 2015

I think I found a work around for me.

I used "add source" via Adobe Media Encoder to get my sequence rendering.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines