I'm trying to export a 1080p (24 fps) 90 second video in h264. I've done this hundreds of times before but for some reason the encoding window gets stuck on 0%. This is the first time I've tried to export with the latest update of Premiere Pro 2020 (14.0.1). Here are some quick notes:
(running on Mojave OS)
Any suggestions are appreciated. Thank you!
I'm having the same problem. I spent a number of hours on tech support. The solution for me was to downgrade to Premiere Pro v14.0.0
Copy link to clipboard
Hello, apparently you has tried many things before; What I suggest seriously do the following: Open your project; Now create a new project and copy and paste the timeline on the new project (there may be some error in the project you are currently working on) close the preview project and try to export.
Thank you! That was the solution! Worked like a charm!
Same issue after patching to 14.0.1. Clearing the chapter markers from the sequence allowed me to render as normal.
For both Hampus and Silver ... were the sequences originally created in the 2019 13.x versions of Premiere?
I have seen a user elsewhere report that some sequences created in the 13.x/2019 builds won't export in 14.0.1. His workaround was to create a new sequence in 14.0.1, copy/paste the contents of the old sequence into the new one created in 14.0.1
You may find it faster to do this by setting up a "pancake" editing screen with two timelines vertically stacked.
Thank you! It worked wonders!
Thank you Sumeet -- the recommendation in the article around deleteing the marker_GUID info worked for me. https://community.adobe.com/t5/premiere-pro/how-to-solve-encoding-export-stuck-at-0-with-premiere-pr...
Did not need to do the new sequence / copy paste approach.
This also worked for me. There were multiple marker_GUID 's in my Sequences so just make sure to look for more than 1
Thank you SO much. Your advice just saved my life on a. crazy deadline. Clearing all markers on my existing sequence did the trick! I'm ever so grateful 🙂
I have been getting this issue as well,
The easiest fix that worked for me is to create a new sequence and copy everything into it.
What causes this issue though?
None of us "here" are staffers or engineers ... so we don't know "why". We've just figured out how to get around it when that specific thing happens.
Same issue here. Along with the time remapping issues, nesting issues, lumetri issues, etc, I have to wonder why you (adobe) keep pumping out new versions when they're completely rife with bugs, along with old ones that still haven't been fixed.
It's fascinating to see people complaining about the devs pushing new versions/features rather than going after bugs/stability.
Most users clearly didn't actually look at the information for the 2020 version. The "new" features were ... auto-reframe. That's about it. Oh, and finally adding the full keyboard shortcuts from the old Titler to available with the EGP. That wasn't a lot of engineering time on new stuff.
So ... what was it? As noted in quite a few places ... the main purpose of the 14.x/2020 series was to go after stability and bugs. And in that process, announced they were limiting the older gear that they were coding for to simplify and update the code base, had fixed (for most scenarios at least) the largest batch of bugs/stability issues they've ever hit, and would be going after more as their main effort.
At Adobe MAX, the project sub-manager brought in to lead the rebuilding of the Pr engineering team to make bugs/stability a more native part of their entire process talked with a meeting of the ACPs. Ivo Manolov said that 1) they'd hit a ton of bugs which was the good news but 2) that backlog was massive and will take some time to work through ... as the bad news.
And for current users, also good news/bad news: as a percentage of the user base, more users are stable with the 14.x series than any previous series was the good news. The bad news ... the majority of the remaining bugs and stability issues were things they couldn't replicate with the in-house mix of Mac/PC gear and media. So getting at the remaining issues, which were HUGE for say some users with RED and Sony media types, some other things ... is darn difficult. What the engineers can't replicate, they can't fix.
Understand, Premeire runs on the widest range of gear/media/workflows of any major NLE. For years at NAB, aisle-talk has wondered if Premiere shouldn't back off on the gear/media it worked with in order to get wider stability. So I asked him about that, and he said that is why they cut back on some of the older gear and media types. Purely to simplify coding.
And further ... they made it clear they NEED the users with issues to file detailed reports on the UserVoice system. One of the engineers who read every report filed was there, and his chief complaint was that for so many reports, all he got was "X ain't working on my rig" ... and as he doesn't even know then what version they have or what gear they're running on, it's a useless report.
If you're having troubles, please go to the UserVoice system and search for similar reports, add on a comment with detailed information on your gear/media and what happens when you do whatever is leading to the problem. That way they can see better what is happening, start narrowing down on what gear/media, and contact those that give enough details so the engineers get a better look at the factors involved.
Also ... besides the engineers, all reports filed on the UserVoice system get collated and sent up to the upper managers who determine budgets ... Adobe lives by metrics, so ... let's give them metrics.
Oh ... and post back here a link to any UserVoice thread you create or vote on, so the rest of us can pop over there and upvote. Let's get some of these things fixed.
why TF does Adobe make updates that make it HARDER to use the product. i legit can't think of one time i've upgraded an OS and a new version of Premiere and the sh*t just worked. never.
I just had this problem - got stuck on 0% while encoding/exporting. The fix for me was just deleting any markers on the timeline.
Which version of Premiere are you using? 14.0, 14.0.1, or 14.0.3?
This issue has been solved in 14.0.3.
It worked for me! thanks a lot
Thank you for your advice.
How do you do that? Can you please elaborate
Can someone explain how to copy paste a timeline? I see how to Import a project or a sequence? Is that what is meant by copy / paste a timeline? I tried creating a new project and importing the old project that won't currently render. Same issue, still won't render. I tried importing a sequence but that did not import all of the information (camera shots, effects, etc). This is quite the bug in this program
Open a timeline. Open a second project file, and open the timeline panel.
In the first program, Ctrl/Cmd-A to select all, then copy. Either right-click/copy or on Windows, Ctrl-V does fine.
Click on the other timeline. Right-click, paste.