• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
1

GPU Acceleration no longer working

Participant ,
Jul 25, 2024 Jul 25, 2024

Copy link to clipboard

Copied

PP 2024 24.4.1 Build 2

Ryzen 9 5950x 

RTX 3090Ti

128GB DDR4

8TB Crucial NVME Hard Drive

 

For the last few days this project has been giving me some grief. Here's the issue. 

 

3840 x 2160 Timeline, Hardware Encoding to H.264. No problem. I add in a few transitions that are using the following effects: 

- Transform

- Replicate

- Mirror

These transitions mimic the effect of "swiping" which is useful for my project.

 

Now, every time I turn on Hardware encoding, the entire project will not display ANY preview files or ANY video in any of the windows, the Source Panel nor the Program Window, neither playing nor paused. 

When paused, the video will briefly display on my third monitor (using fullscreen playback). This is the only way I can see the project with CUDA enabled.

 

Originally when I was exporting the file, with Hardware Encoding on -- it would give me the error: h.264 error rendering video:

 

Export Error
Error completing render.

Writing with exporter: H.264
Writing to file: xx
Writing file type: H264
Around timecode: 00:00:26:12
Component: H.264 of type Exporter
Selector: 9
Error code: 3

 

I could at least SEE the video then. Today, no luck. Completely black. 

 

I can see the video and choppily play it back when I have CUDA off, but my exports (for a 30s video) takes 2 hours instead of 30 seconds. 

 

Am I doomed here? Why is Hardware enabled acceleration broken for me at this moment?

 

I've tried importing the project into a new project, clearing the cache completely, updating drivers, exporting to new locations -- nothing is working. 

 

Please help. 

Bug Needs More Info
TOPICS
Editing and playback , Export , Performance or Stability

Views

338

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Pinned Reply

Adobe Employee , Jul 26, 2024 Jul 26, 2024

Hello CJ,

I'm Kevin from Support, one of the moderators here. Thanks for filing this bug report. When did this issue start to appear? Have you tried any troubleshooting steps like deleting the media cache or resetting preferences? I hope the advice helps you.

 

The team might ask for more info, and I hope they will respond shortly. Sorry for the frustration.

 

Thanks,
Kevin

Votes

Translate

Translate
7 Comments
Participant ,
Jul 25, 2024 Jul 25, 2024

Copy link to clipboard

Copied

I would also like to mention that exporting in AME has generated nothing but "failed" video encodes with Hardware acceleration, and 4+ hours with software acceleration. I simply cannot operate with these kinds of setbacks. Exporting directly from Premiere seems only to take about an hour, while AME is about 4+ hours for a 30s video. 

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jul 26, 2024 Jul 26, 2024

Copy link to clipboard

Copied

Hello CJ,

I'm Kevin from Support, one of the moderators here. Thanks for filing this bug report. When did this issue start to appear? Have you tried any troubleshooting steps like deleting the media cache or resetting preferences? I hope the advice helps you.

 

The team might ask for more info, and I hope they will respond shortly. Sorry for the frustration.

 

Thanks,
Kevin

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jul 26, 2024 Jul 26, 2024

Copy link to clipboard

Copied

CJ,

Would you like me to move this post to the Media Encoder Bugs forum? Let me know.

 

Thanks,

Kevin

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jul 26, 2024 Jul 26, 2024

Copy link to clipboard

Copied

The status of this bug report has been updated.

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio
Status Needs More Info

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jul 26, 2024 Jul 26, 2024

Copy link to clipboard

Copied

Hi CJCARNAHAN

Sorry to hear about your troubles in exporting with the transitions applied. It does sound like it is taking way to long for what you are trying to accomplish. You have already supplied us with some of he Bug report details we would need to help out on this matter. Can you also tell me what version of Nvidia  RTX drivers you are running? And if these effects you are using use any third party plugins? Once we have that info and or files you may provide we can start to Repo the error on our end. 

  • Issue - A short description of the problem. 
  • Adobe Premiere Pro version number: 
  • Operating system - Windows or macOS, and which version of those operating systems?
  • System Info: CPU, GPU, RAM, HD:
    • CPU

    • GPU and Driver Version

    • RAM

    • Hard Drive (and, if external, how the drive is connected: USB 3, Thunderbolt, etc.).

  • Video format: Provide information about the type of video you're using. For example, XAVC-I 4:2:2 10-bit. If you're not sure, let us know what settings you selected on the camera. If you don't have access to the camera, sharing a sample file is useful
  • Workflow details: Tell us any specific info about the project or sequence. For example, is it a multicam sequence?
  • Steps to reproduce - (Very important!) Exact steps, in a numbered list, that are needed to reproduce the problem. 
  • Expected result - What should have happened after the last step?
  • Actual result -  What did happen after the previous step? 

 

Optional but helpful: upload media, project files, screenshots, or screen recordings demonstrating the issue. 

Thank you,

Ian

 

Votes

Translate

Translate

Report

Report
Community Expert ,
Jul 26, 2024 Jul 26, 2024

Copy link to clipboard

Copied

Dont think anyone can help you here but

Reset preferences, trash media cash or upgrade to more current version of Premiere

Votes

Translate

Translate

Report

Report
Participant ,
Jul 27, 2024 Jul 27, 2024

Copy link to clipboard

Copied

LATEST

Hi Kevin, 

 

The issue lies with both Media Encoder and Premiere, as certain exports within both programs will issue the error code and black frames. 

 

I reset the media cache and preferences as well, to no avail. 

 

 

Hard Drives I'm editing off of: 

RAID10:  SynologyDiskStation DS1621+ 6-Bay NAS Enclosure 
with 6x WD 12TB Ultrastar 7200 rpm SATA 3.5" Internal Data Center HDD 

it's a network drive directly connected to my PC through a 10GB ethernet port. 

 

  • Issue - See above
  • Adobe Premiere Pro version number: PP 2024 24.4.1 Build 2
  • Operating system - Win10 Version 10.0.19045 Build 19045
  • System Info: CPU, GPU, RAM, HD:
    • PP 2024 24.4.1 Build 2

      AMD Ryzen 9 5950X 16-Core Processor 3.70 GHz

      MoBo: ROG CROSSHAIR VIII HERO (WI-FI)

      RAM: G.Skill 128GB DDR4 3600

      RTX 3090Ti Studio Driver 560.70

      8TB Crucial NVME Hard Drive

      Win10 Version 10.0.19045 Build 19045

  • Video format: Shot in: BRAW 12:1 6k 23.98 fps
  • Workflow details: 3840x2160 sequence. The issue occurs specificly when I apply a transition -- and HOW I apply the transition is such: -- I have opened in my template (which I always use) a transition pack that uses adjustment layers. I drag and drop the adjustment layers on top of the footage (highlighted here on V4).
  • CJCARNAHAN_0-1722033236637.png

     

  • Steps to reproduce - (Very important!) See above. In this screenshot, the Program monitor IS displaying the footage, where as yesterday it was not at all. 
  • Expected result - Footage to be displayed in the program monitor with CUDA enables. 
  • Actual result -  Black video in Program monitor and Source window. Not able to view footage at all in either program monitor or source window. NOTE: When I EXPORTED the 30s video (took an hour and a half without CUDA enabled), I exported the file as a .mov, then re-imported that into premiere, and THAT is how I was at least able to cut the render time down from 1.5 hours to 10 minutes (only the last part of the export time had to chug). 

 

Votes

Translate

Translate

Report

Report