We have a brand new look! Take a tour with us and explore the latest updates on Adobe Support Community.
Okay. I have researched every post I could find about this issue and I am creating this post because I need a better solution than the ones I have found.
Whenever I select CUDA in the project settings aa opposed to Software, I get a black screen on my source files and playback. I have already went into my preferences and adjusted all the settings to enable GPU acceleration. I have tried both the most up-to-date Gaming/Studio drivers since the timing of this post.
I cannot see my 5K R3DCODE footage unless I use software only. I, like many others do not want to use software encoding. I want to use my hardware. I input my source files into NLEs like After Effects, DaVinci Resolve, REDCINE PRO and can access and enable GPU acceleration and encoding without black screen or playback issues. This problem is specifically isolated on Premiere Pro and I am having little to no luck finding the proper solution.
WINDOWS 10 HOME
AMD THREADRIPPER 3960X
MSI VENTUS 3X 3080
64GB GSKILL DDR4 3200
2TB VIPER GEN 4
I'm having the same issue. When I have the Renderer set to CUDA setting or the "Enable Hardware Accelerated encoding and decoding (requires restart) selected, the .R3D files don't display in my program window.
I have the new RTX 3080 video card btw.
Are you on the latest drivers? I know Nvidia recently fixed some of the bugs with the 3080.
Could try a clean install of the drivers as well
I have the same issue with the 3090. Latest november studio drivers did not fix it.
I've recently also been having the same issue for a few months now and still have not found a fix for it and I'm rocking a 2070 Super so its definitely not an issue specifcally with the 30 series gpus.
Same issue with 1070Ti, already did clean install with most updated drivers...
Might finally push me to move to FCX...
has anyone found a fix for this? 2k on a 3090 and its pretty much worthless at this point.
Hi, hopefully you found a fix, if not, what worked for my was underclocking it below the factory overclock on msi afterburner, seems to have worked on my 1660
Hello, same problem with 2070 Super and all the latest drivers and software. I will formatted my PC hoping that this will fix the problem because I have tried everything ...
Have you overclocked your graphics card at all?
I underclocked my factory OC GPU to solve the problem
Anybody have a fix on this? I've also got this issue
Any fixes yet? Having the same problem with my 2060s and it's been driving me mad. Tried the latest drivers and every other driver back a year+. Makes me completely useless as an editor. Stumbling to the finish line on my current projects then going to give Resolve a try.
I do have the same problem with RTX 2060. Better use DRP rather than PP, waste of money.
Same issue here with the 3080.
No overclocks and latest drivers
Same problem here with RTX2080. Newest Premiere Version 15.2; Nvidea Studio Driver without Geforce Experience;
I am getting randomly Black Screen during editing with H264 Clips.
There are a lot of threads on this issue (since years!) Seems to be a major problem with CUDA and Premiere. Is there any official answer from Adobe?
Are there any AMD users here having the same problem with OpenCl? I am thinking of a switch to AMD 6900, but it is very expensive and I don`t wan't to waste the money for just a test. Maybe Adobe and Nvidea should just "do their homework" and getting this fixed.
Wanted to chime in this is an ongoing issue for me as well.
RTX 3070, latest drivers, latest version on Premiere. It's driving me crazy.
This issue is still happening to this date.
GTX 1050 Ti, using ultra key on h264 video files.
I've found this black-screen issue comes up when another process is also using GPU acceleration, that doesn't play well with Premiere. Surprisingly, Chrome, Brave or any Chromium-based browser is one of them. If you have this browser up, go into settings and disable
"Use hardware acceleration when available"
and restart the browser. This has fixed the issue several times for me.