Participant

Answered

Premiere Pro CC (2017) crashes at export

Forum|Forum|9 years ago
November 10, 2016
20 replies
48990 views

Hello

I've just started a Premiere Pro trial a few days ago and edited a video which I'm unable to export.

The export fails over and over again for the most part at the same point (34%..) The error code is 1609629690.

I'm using a Surface Pro 3 Core i5 running Windows 10. I tried to export at least 30 times with no success while changing parameters etc. As part of the mitigation I tried the following steps: Restarted my Surface Pro, rendered smaller segments in order to identify segments that may be causing this issue, removed suspicious still photos, tried different output types and tried to export based on previews.

I've worked with other editing software before and never had these problems.

Would appreciate any advice.

This topic has been closed for replies.

Correct answer Kevin J. Monahan Jr.

Goju has not returned since 2016, so this thread has become a proverbial dumping ground for all people having trouble exporting video from Premiere Pro.

A good number of solutions are given to this issue, so unfortunately, there is no one "magic bullet" to solve all export issues. Sorry.

Some things to try if you get an "Error Compiling Movie" error dialog box.

Delete Media Cache
Export to an intermediate codec like Cineform or ProRes instead of H.264
- Create H.264 files from this master
- Use smart rendering to make this process go much faster
Choose Project Settings > General > Renderer and choose "Software Only" — slower but bypasses the GPU which could be the source of your issue.
Remove GPU accelerated effects, like Lumetri Color effects.
If you have lots of large still images or 4K video in a HD timeline, consider
- resizing photos in Photoshop to a smaller size
- resize 4K video to HD in Media Encoder
Remove odd characters or punctuation marks in the naming of the file.
Make sure there is enough drive space available on the target hard drive for the export.
Copy/Paste clips from the problem sequence to a brand new sequence.
Delete any preview files.
Replace clips that seemed to have caused problems at the timecode indicated in the warning. It's possible that the clip is corrupt.

Hope these tips will help those finding this "dead thread" in search of a solution for exporting problems.

Thanks,
Kevin

Show previous replies

mikemcrocken

Participant

Had a project due tomorrow and then this "serious problem" with crashing during output crap started. It's a two hour video and a LOT of work went into it. I don't have time to try all the fancy stuff here so what I did is output a Quicktime movie of JUST the audio - I used the Queue and did it in the encoder. Got the audio out. Then I tried the same with "video only" output. Crashed again. Then I saved the project as (whatever name you want to give it). Then I deleted the audio on this timeline and only had video left... I output that in 30 minute chunks to Quicktime and damned if that didn't work. I put 3/4 of the timeline, the part I wasn't outputting, on my clipboard by cutting it or using command X. Then when the first 1/4 was successfully output as a Quicktime, I pasted the rest of the timeline back in after deleting what I had already output... did this several times till I had the whole video output to Quicktime clips then put it back together on a new timeline. Hope this makes sense - just do it anyway you can, (you even can dupe the file four times and delete all but a different 1/4 section of the project) I now have to put all these back together and it's a pain in the butt... but I'll make my deadline. For all you folks who are sweating blood right now... this takes time but works. Still don't know why it did this in the first place!

onujpt

Participant

Hi All-

I figured I'd post my update with the same? issue... I experienced the "Adobe CC 2018 encountered an error and needs to shutdown" at the same spot of exporting the same sequence. 91% no matter if I brought it into a new project or not. I tracked to 91% of my project and found that to be the start of a new clip with Alpha. Tried removing it. No luck. No matter what it would shutdown at 91% of my project exported. No matter if I exported straight from Premiere, or used Adobe Media Encoder. My struggle is ... I exported this exact same sequence previously, I just made a few changes toward the BEGINNING of the sequence. So I don't understand why it was having an issue now.

However, I disabled the OpenCL GPU acceleration like noted above and it seemed to then export my project just fine. Definitely a little more time consuming. I'm exporting a 30 minute wedding video and "aint nobody got time for that." I should note that I'm exporting in H.264 using the YouTube 1080p HD preset.

I'm using a 2015 iMac. 3.4 GHz Intel Core i7 with 32GB of 1600DDR3 Ram. I mean... this machine should have no excuse for not exporting ANYTHING. Let alone some silly wedding video shot on a Mark III. Does anyone have any other updates to this or thoughts as to why this is happening? Especially when my sequence exported just fine yesterday?

productionmandan

Participant

SO, I've had similar problems using Premiere and am doing a job now that kept crashing. My 23 years of using digital editors and dealing with these kinds of issues in the past, its always the same kind of issue. Its the clip its crashing on. Its either bad format, corrupt, or needs adjusting. I was able to fix it and its probably a similar problem that you are having. Watch your export and see exactly where it is crashing. More than likely its not the system its the exact clip that is making it crash. In my case it was crashing on a still image that was 250dpi and 5,000 pixels that had key framing. So it was a big picture file. I reduced the picture file size in Photoshop to 72dpi and 2,000 pixels and deleted the key framing and the export went right over it. IF its a video clip, change the format or encode it to a new master clip .mov or .mp4 and insert that into your timeline. Also, when systems are exporting it may be the clip before or after the one its crashing on. The system might be encoding the clip ahead of what you are seeing. If it keeps crashing change all the clips right around that section. Usually around 3 clips. If you have a certain filter on that clip, delete the filters and try. Re-encode the video clips or make sure the still images are JPEGs, not some weird file format. Make sure the files aren't to big and not high bitrate (32 bit in photoshop) etc.

GUARANTEE, this will fix your problem and you will be able to export. Its not the system its the files its trying to export!

E

edithouse

Participating Frequently

I found a WORKAROUND, but not a true solution. Got my project out though. Will explain, but first--Robin, like you I have 23 years of NLE experience. Bought my 1st Avid in Nov 1994. In the Avid days there were truly sometimes corrupt frames, which would appear as green or half-green in pause. FCPs1-7 sometimes also did this. This is different! It crashes on export at different times. And I have found no visible bad frame. So anyway, my somewhat laborious workaround is: If I export my approx 18-min project in QUARTERS, so 0:00-4:30:00 and then 4:30:01 to 9:00:00 and so on, each of the shorter files EXPORTS FINE. So clearly there is NO single bad frame. I then needed to import the 4 exports back into Premiere and reconstruct the 4 pieces into one complete sequence. I had an audio pop at each of the 3 new edit points, so I cut one frame at each and added a 1-frame dissolve, which helped. And I needed to render the sequence. Anyway, I got it exported for real then--took longer of course, but worked. But ADOBE--this is NOT a tenable solution....What's up?

E

edithouse

Participating Frequently

OK, using that system I wrote above today it DID crash once, on my last of 4 files, but the second time NO. There was though an "!" on the green check mark in Media Encode, which had the warning I have copied below. But first, could it be that this "legacy" warning is actually interfering with the export? When the message is triggered by the soon-to-be-antiquated (i.e., NON-legacy supported) footage, perhaps the EXPORT crashes? Here is the error message that was found in the "!" on the green check mark after the export completed:

11/17/2017 04:04:10 PM : Queue Started

- Source File: /var/folders/10/jb1wq68x7694y82swbp7wjc

00000gn/T/Mark-Nov17-v12_3.prproj

- Output File: /Volumes/Cinc/Mk-Nov2017-Cinc/XPs-Mk-v5c-EXPORT4of4.mp4

- Preset Used: Custom

- Video: 1920x1080 (1.0), 29.97 fps, Progressive, 00;04;15;01

- Audio: AAC, 320 kbps, 48 kHz, Stereo

- Bitrate: VBR, 1 pass, Target 14.00 Mbps, Max 20.00 Mbps

- Encoding Time: 00:07:47

11/17/2017 04:12:42 PM : File Encoded with warning

------------------------------------------------------------

32-bit QuickTime support ending

Support for import/export of legacy 32-bit QuickTime media will be discontinued in a future version of Premiere Pro. Transcode to a non-legacy format to continue using the media in Premiere Pro after legacy support has ended.

------------------------------------------------------------

11/17/2017 04:12:42 PM : Queue Stopped

Note the: "File Encoded with warning" (emphasis mine) SO ALSO IT LOOKS LIKE WE WILL need to RE-ENCODE THE OLD FOOTAGE going into future versions.

E

Edward Scissors

Participating Frequently

Send the export to AME.

AME has a useful function where if the export fails it tells you why and gives you a timecode. Just click on the 'Failed' icon/text.

I had the same problem and found it was because the graphics card couldn't process a blur filter on some text

zacd

Inspiring

This is probably due to the computer hardware, and what your trying to render the video at. Seems obvious, but if you have poor hardware, your computer could crash and the graphics card could get overloaded.

L

lloyd_ril

Participating Frequently

Regarding the hardware blame suggestion,

I'm seeing this on 3 computers.

32GB RAM, 16GB RAM, 16GB RAM (respectively)
GTX 1070 8GB, GTX 1060 8GB, AMD R9 380 4GB (respectively)
FX9370 (8 Core, 4.4Ghz), i7 Mobile, i7 desktop (respectively)
All 3 operate off of SSDs

Considering there is no apple product on the market that can meet any of those 3 for specifications, and each setup has a completely different specification with heavy use in digital design --- I'd argue we can put blaming the hardware to rest. Adobe software is "thick" but hardly something requiring major specifications.

I'd like to hear someone from Adobe who can can give us hints or tips or figure out why their software is crashing.

F

frigidshutter

Participant

Had the same issue this week switching between Premiere Pro CC v9.2 & v10.4 on Mac os x 10.9.5

if you can switch your GPU acceleration from OpenCL to CUDA if u have a cudacore nvidia graphics card it will solve the issue

Update the video card driver make sure the Cuda appears in your system preferences

change GPU in project settings to cuda from openCL

RotoPawn

Participating Frequently

I've occasionally had problems exporting directly through Premiere for inexplicable reasons, and learned to choose 'Queue' instead of 'Export' at the bottom of the Export window. That sends the export job out to Adobe Media Encoder, which seems to be more reliable - if not with it's own occasional hiccups. Plus, you can still use Premiere while Media Encoder handles the render. Although, that will either slow the render to a crawl or make Premiere drag. But it's still nice having that option.

It's something to try, if you can and you haven't already.

Michael Linder

Inspiring

I'm still at a loss. Even with minimal settings (medium bit rate, 1-pass, medium audio) Media Encoder still crashes. This happens while CPU usage is in the mid-70 percentile, processor temp at 63 degrees centigrade. But analyzing what was encoded in PotPlayer, I came across something strange. Here's the readout. Note the boldface entry...

General

Complete name: C:\Users\ML\Desktop\TEST 10.9772.121921.m4v
Format: AVC
Format/Info: Advanced Video Codec
File size: 30.3 MiB
FileExtension_Invalid: avc h264 264

Video

Format: AVC
Format/Info: Advanced Video Codec
Format profile: Main@L4.1
Format settings, CABAC : Yes
Format settings, ReFrames : 3 frames
Width: 1 920 pixels
Height: 1 080 pixels
Display aspect ratio: 16:9
Frame rate: 29.970 (30000/1001) FPS
Standard: NTSC
Color space: YUV
Chroma subsampling: 4:2:0
Bit depth: 8 bits
Scan type: Progressive
Color range: Limited
Color primaries: BT.709
Transfer characteristics: BT.709
Matrix coefficients: BT.709

Is it normal for mp4 source material to be showing up as AVC in the General notes? Does Premiere Pro CC 2017 convert it to MPEG-4 on completion? Is the invalid H.264 extension corrected on completion, or is it possibly an incorrect association setting on my PC? I'm grabbing at straws, I know, but hoping for a solution.

RotoPawn

Participating Frequently

Hopefully someone else can speak to the file analysis. It's over my head. But what I find curious from what you report is that your CPU usage isn't pegged at 100% during encode. The only time Premiere or Encoder lingered around 70% during any export on my machine turned out to be a glitch that seemed linked to the Mercury Playback Engine crashing GPU acceleration. Maybe that's something to look at.

In any case, I've been to war with Premiere a lot in five years and I've developed a throw-the-kitchen-sink-at-it method for when nothing makes sense anymore.

Ctrl+C your entire project to the clipboard, close premiere, rename (or if you're sure what you're doing - manually delete) Premiere's 'media cache' and 'media cache files' folders, re-open premiere, create a new project WITHOUT OPENING the original, instantiate the timeline with a clip of the correct resolution and frame rate, then CTRL+P everything back onto the timeline from the clipboard...

Then open Media Encoder and change preferences to "import sequences natively," before going back to premiere to queue for export. If the export fails while using GPU acceleration, try CPU only.

And if all of that doesn't shake something loose, you have to wonder if Premiere just doesn't like a certain clip that's being used in the project -- for whatever reason. And if that's the rub -- then it's down to the much maligned: re-encode source material through Handbrake, "method."

(Note: Premiere hates rendering from giant, high-res images, if anything like that is in use.)

I hope something in there helps, if you can be bothered to run the gambit of it.

thevjguy

Participant

I am having the same problem. I'm on a midnight deadline. Going to re-do this on my Mac. Premiere Pro 2017 on Windows 10 keeps crashing on export aprox 1 or so minutes in to it. The file is only 15 minutes.

So irritating.

O

olutunmbi1

Participating Frequently

Yeah I didn't make a ton of deadlines because of this issue. For now it seems stable, is your system still crashing? Also are you on a new Macbook Pro or are you running on a PC?

Michael Linder

Inspiring

I'm on a PC. Adobe Premiere Pro 2017 used to crash at the 16%-point of a 4-minute video. I uninstalled and reinstalled both Premiere and Media Exporter and now the crash occurs as soon as an export format is chosen.

You folks are discussing issues that began in December. It's now mid-March and Adobe has done absolutely nothing to rectify a problem that renders their software unusable. Sums up my level of confidence in the alleged Wizards of San Jose. Can I get a partial refund on my Creative Cloud subscription, Adobe?

(I think we all know what Adobe's mercenary-yet-failed programmers will say, should they reply at all.)

H

Highly Achievable

Participant

Has anyone found a solution to this problem yet? It seems to be a prevalent one when I google but I am not seeing solutions.

O

olutunmbi1

Participating Frequently

I was told by Apple to turn off the OpenCL GPU acceleration, It can be found in Premiere. Go to File-Project settings-General- Video rendering and playback.

H

HeartNation

Inspiring

Whenever I turn off OpenCL GPU acceleration and do "Mercury Playback Engine Software Only" the render time is horrendously slow. This suggestion by Apple is not a fix. Weekly deadlines requires the speed.

O

olutunmbi1

Participating Frequently

Same issue goju. I'm running macbook pro 15in 2016. During export the computer crashes, no error message, just pure crash. I'm on a deadline and can't find a solution.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded