Encoding Adobe Premiere Pro

[Colby DuLin]

Whileexporting a Video in Adobe Premiere Pro, there is the option to export a Video with Software or Hardware Accelerated encoder. After i searched a bit about this topic i found that it is pretty unclear if the Hardware Encoding will result in lower quality of the video, also the official site of adobe itself won't give any information on this. My question is, will hardware encoding in premiere pro result in a lower quality as trade for rendering time.

This is because a software-based encoder can use many more algorithms that are "simulated" on the CPU, the hardware encoder may be much faster because the algorithms are physical circuits on a chip. But having algorithms on a chip with limited space means there's only so many options a hardware encoder can use, whereas the software encoder can use as many options as it wants.

Different software encoders all following the same standard can be better or worse than each other because the algorithms they use to compress are different. For example, libaom-av1 and svt-av1 both encode to av1, but differ greatly in speed, quality and size.

For example, software encoding is like using an ever-improving piece of software, which is slow because it's simulated but high quality because it's complex, versus hardware encoding, which is a physical chip that can't change but is fast and lower quality because it's simpler.

If you don't care about file size, I suggest bumping up the bitrate a lot and just hardware encoding. But if it's for web content, which is gonna get re-encoded again and again, you might not wanna make the first encode in that chain a hardware encode.

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:

It's not about getting scrappy. It's about Adobe making Premiere function. We do not have time to spend hours, as all of us here have done, with tech support. Eveytime there is an update I cringe as I am doing now because of all the new glitches. I really am ready to drop the program all together and migrate over to Resolve.

You now have a "clean" new version project file with less potential issues than having Pr 'convert'. And .... the original project file and it's version of Premiere are both still fully ready to work.

Hi there I had the same issue, and your solution worked for me! For anybody else: Just make sure to create a completely new sequence and don't duplicate the one that you are having troubles exporting. Its a weird bug

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.

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

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.

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.

Hi could someone help me with this issue I have.. I have been using this app for the past 6 months on my laptop and it has worked perfectly fine... no issues but now it won't finish encoding as it is stuck at 0%

I normally render My videos by exporting on premiere pro or sending it to media encoder.. it used to work fine but not neither one of them export properly .. I use Mercury playback engine hardware accelerated (CUDA) but now that option is missing so I use (OpenCL) then it stopped working? Usually I render the vid on H.264 on medium or high bitrate at 60fps and 48Hz audio stereo channel.

Sorry, you are having the same issue. The suggestion was to try reinstalling the GPU drivers and get your CUDA acceleration going again. After reinstalling the drivers, go to Project Settings > General and change the renderer to Mercury Playback Engine GPU Acceleration (CUDA). See if that works for you. If you need more detailed steps, let us know.

3a8082e126