A low-level exeption occurred in: Adobe Player <Player:5) win10 - now no preview!5 votes
adobe player exception occured player 5 since the yesterday update. GPU acceleration CUDA is not working anymore
problem with GPU acceleration not accepted since the latesty upgrade3 votes
Metal support in Premiere Pro 2020 is currently very bad. On a Radeon VII under macOS Catalina, I'm seeing encode times from a ProRes 4444 timeline to ProRes HQ output taking 45-50 minutes for a 4-minute piece. That same piece encoded in under 10-minutes using OpenCL. Additionally, native Adobe plugins that work fine in OpenCL give a red banner CPU warning under Metal. There is no RED SDK support either. Clearly Metal render support needs work, especially if OpenCL is being deprecated. Please improve Metal support under macOS in Premiere Pro and across all professional media creation applications. Thanks.7 votes
Out of all the major video editors, Pr Pro has the poorest support for eGPUs on Mac. Please enable your users with support your competition has. It is almost as if there are no added bonuses.18 votes
When cutting videos in 4K, I can't watch the video smoothly because the CPU does all the rendering work and the GPU does nothing. And I want Adobe to improve that the GPU does more with rendering and cutting.4 votes
Hello, currently there is no hardware coding for video in format MXF.
Will such functionality implemented in the future and when?
Can you offer some alternative workflow for us?3 votes
When import any type of video files in the premier the video's colors turns contrasty and darker than the original video file.
so i can't color grade any video which is a big problem
it's a hardware compatibility problem as i understand from my search on the internet and as i understand from the adobe support team that adobe didn't solve this problem yet for the specific version of the i mac ritna 5k1 vote
When using OpenCL to help generate video in Premiere Pro and Encoder, jpg images with embedded ICC profiles display distorted, both in preview and in the final render. Generating the same jpg without the ICC profile with Photoshop ensures it's rendered correctly.
System: AMD Ryzen 3700X, RX 5700 XT (latest drivers as of 26.11.19)
OS: Windows 10 Pro, 10.0.18.362
Adobe software: Media Encoder 14.0, Premiere Pro 14.07 votes
With GPU acceleration turned on in project settings, transparent graphics appear about 40 percent more transparent than they should. When GPU acceleration is turned off the graphics display correctly. This happens with both image files, .PSD, PNG etc., video files, CineForm, ProRes, and dynamically linked AE compositions.
I am using Premiere 14.0.3, RTX 2070 driver version 442.50, Windows 10.
Attached is a image with side-by-side screen grabs of a black graphic with various amounts of opacity over a light paper texture. Left side is the timeline with GPU acceleration off, right with the GPU acceleration on.2 votes
I have the same bug with me ........ shame on you any ADOBE, I use Premiere pro since 1.5 and the legendary 2.0 (on 6 dvd's), never like this, new Pp and immediately bug, every time !!!
- See how DAVINCI works, how it uses GPU !!!
- See how it behaves on the timeline, 4K video in DAVINCI !!!
- IT'S NO WONDER THAT YOUR USERS ARE GOING ON DAVINCI ....
- More GPU integration, More GPU integration, More GPU integration...!!!
- THE PRICE ...
SHAME !2 votes
When using Metal as your renderer, when you stack the Transform effect BEFORE the Track Matte Key effect on a video clip, adjustments made to properties on the Transform effect (such as scale) will happen AFTER the matte has been set.
If you change your renderer to Software Only, the render order happens correctly and properties on the Transform effect occur BEFORE the matte has been set.
Not having the ability to transform a clip BEFORE the signal gets sent to your matte significantly reduces the usefulness of the Track Matte Key effect.
Use GPU when high Quality playback is on1 vote
Please bring back CUDA support in AE, Pr, and AME 2020 for users who still are running these apps in High Sierra with NVIDA hardware and web drivers.
It makes no sense to keep Open CL and remove CUDA. Both are deprecated but for many of us remaining on High Sierra until the new Mac Pro becomes available or AMD releases Big Navi, CUDA is still viable. Please return CUDA support for CC 2020 media apps during this interim period. Thanks!7 votes
This has been plaguing me for years in Premiere.
Enabling CUDA screws up various aspects of rendering.
Here, you can see how enabling CUDA dramatically changes how text fades in:10 votes
When using Metal on MacOS, Red IPP2 R3D footage is displayed with a strange border and exports this way as well. Only appears when playback resolution or paused resolution is set to "Full". Metal GPU is the only supported option moving forward, and Red footage is an industry standard- this must be fixed ASAP!
Mac Pro Late 2013
MacOS Catalina 10.15.3
Metal GPU1 vote
Premiere Pro 14.0.3 time remapping preview does not work if CUDA enabled and speed over 800%. In preview, the video play position jumps back and editing is practically impossible. If Video is exported, the problem does not exist. If CUDA turned off and software only used, the problem does not exist. If speed less than 800%, the problem does not exist. Using latest NVIDIA Studio Driver with GTX1080 and GTX1650. Please fix this problem.2 votes
Sequence panel goes completely unresponsive.
I also correctly select the right gpu and then everything goes to ****. Took 4 hours to export what usually take 40 minutes. Making my workspace nearly unusable with this program1 vote
Ever since updating to latest version of windows, Premiere Pro 2020 and latest stable nvidia drivers, mercury transmit is constantly crashing premiere pro. There is no warning... all of a sudden I get the windows spinning cursor and then Premiere shuts down. I am happy to discuss this problem with any tech or engineer at adobe. I have posted this several times in the user forums with no avail.3 votes
Unsupported video driver for NVIDIA K3100M1 vote
Premiere (14.1), of course, has the worst utilization of EGPUs. Sometimes it works, some times it doesn't, sometimes it uses 1/2 the power, sometimes it uses zero. Resolve works 100%, and maximizes usage always. Please update it so it utilizes hardware appropriately.
Currently using MBP 2018, 2.6, 32G, Radeon 580 + EGPU with RX Vega 56 8GB3 votes
- Don't see your idea?