Anything nvidia can do to stick it to intel or AMD, they will. I never found anything wrong with just using CUDA acceleration, which was a simple text edit to the 'gpusniffer' file in the directory of Adobe, by adding my graphics card. For those that may or may not remember, nvidia used to lock-out GPU acceleration to their Quadro range, just to get mo' money, and it was always a joke amongst editors as they would just edit the text file, and shazzam! Prem Pro would use the CUDA cores on a cheapo Geforce card, saving thousands... Interesting that nvidia have not mentioned Cinema DNG (the format co-developed by Adobe) encoding, even though PremPro has had that for like' 6 years now. I think (although cannot remember exactly) nvidia and Adobe were talking about AV1 more than Apple's 'lossy' compression, and I find it very strange they talk about PC owners as an almost excl.usive, but it is Apple users who surely are the only ones interested in ProRes. PC editors do not use prores, unless their client specifically asks for it. AV1 all the way, or even, RAW output in AVI. Lossy is not RAW, Apple. Get the hint.

Loobyluggs:

I never found anything wrong with just using CUDA acceleration, which was a simple text edit to the 'gpusniffer' file in the directory of Adobe, by adding my graphics card. For those that may or may not remember, nvidia used to lock-out GPU acceleration to their Quadro range, just to get mo' money, and it was always a joke amongst editors as they would just edit the text file, and shazzam! Prem Pro would use the CUDA cores on a cheapo Geforce card, saving thousands...

that had nothing to do with nvidia, it was all Adobe's doing.

last time I tried encoding a really large video 4K HDR the lot to H.265 3960x alone took 8hrs 3960x+1080Ti 4hrs I have no idea about premiere unlike loobyluggs above (hobby for me) but that gives an idea to people who didn't know how powerful GPU encoding is I was shocked to see the fps double H.264 I didn't even bother to check the fps it was fast enough... I really want to see what the Nvidia 3xxx will do if they improve that

Astyanax:

that had nothing to do with nvidia, it was all Adobe's doing.

I'm gonna need a citation on that, because Cui bono? -Mercury Engine ran on CUDA -Adobe built Mercury -Nvidia built CUDA to push C++ code onto nvidia cards -Adobe built Mercury to take advantage of CUDA The only people this benefited, from locking out CUDA; was nvidia. In other words, the EULA for CUDA development was written by nvidia - so there was no logical reason for the code to not recognise a graphics card that clearly had CUDA cores in it. This is also why (I'm sure) Adobe made the 'hack' so easy to manipulate, in a frickin' txt file!

I'm not engaging in your conspiracy theories, Adobe are responsible for Adobe software, adobe chose not to use NVEnc till now, Adobe chose to qualify Quadro's for mercury.

I've tried nVidia's H.265 in Handbrake and did not like the results. Sure, its much faster, but the quality is still way better on CPU.

Any time a hack is that easy to get around (the CUDA acceleration, which was a simple text edit to the 'gpusniffer' file in the directory of Adobe)... .. it means it was the marketing or legal department and NOT the technical / devs who forced it. The devs then make it easy to workaround for themselves to use at home.

geogan:

Any time a hack is that easy to get around (the CUDA acceleration, which was a simple text edit to the 'gpusniffer' file in the directory of Adobe)... .. it means it was the marketing or legal department and NOT the technical / devs who forced it. The devs then make it easy to workaround for themselves to use at home.

You may be right - I think I'm talking about the original CUDA acceleration for Quadro cards. I must link this though, from the nvidia website, and I quote

"Adobe and NVIDIA co-developed the Mercury Playback Engine"

Which probably means a few phone calls at the low end, and a dedicated team on-site at Adobe at the other end. Somewhere in between the two is more likely...but there is no doubt they had a hand in forcing their agenda to editors and creative types in the early days of GPU acceleration and CUDA to push Quadro cards. Now, the Mercury engine was really just something that made Premiere Pro (and other tools) run zippier in the early days. What this new thing is more on encoding, to bring this all BoT.