Skip to main content
Participating Frequently
July 18, 2017
Question

Error Compiling Movie GPU/Lumetri - Turn off CUDA - Turn on Software Only

  • July 18, 2017
  • 4 replies
  • 2448 views

Turning CUDA off was also a solution for me, although I still have to purge cache often to avoid the render error.  Not using CUDA also results with bad transition renders.  For example, the awesome smooth transitions that are popular (http://www.chungdha.nl/?p=3997 , do not render correctly when CUDA is off.  Do you know why that may be?

 

Cheers

 

 

 

[Moderator note: branched to new discussion for clarity.]

This topic has been closed for replies.

4 replies

Participant
January 28, 2018
  • I have a few recommendations:

    • File > Project Settings > General
      • Change the renderer to "Software Only" (if you use Media Encoder, change it there too)
      • The drawback of "Software Only" that the export is much, much longer than it would with a sturdier GPU
    • Take advantage of the smart rendering process as much as possible, especially if you have a somewhat underpowered GPU.
      • Currently, you are not taking much advantage of that by encoding directly to H.264.
      • You might try mastering to DNxHD, Cineform, or ProRes instead
      • Create H.264 files from the master
      • Drawback: this is more a process you need to consider in the beginning of a project, not now.
    • Install a GPU with more VRAM.
      • If I were under the gun, and on a deadline, I'd run down to your local computer hardware and get a 4GB or more VRAM GPU.

     Good Luck

Participating Frequently
December 27, 2017

After one year or so in which I lived happily every after with Premiere and AME, I started getting these errors, either when rendering the timeline (pressing Enter) or when exporting via PP OR AME.

I have tried several workarounds, like deleting effects and filters. It's very hard to tell when these errors will happen, but then they seem to stick to a particular timeline like a disease. Sometimes the timeline renders Ok but the export doesn't work. So on...

On top of that, the workaround of using 'software only' rendering seems to screw up the position of some Essential Graphics elements, which is amazing and dissappointing. When changing a project setting to 'Software Only', the boxes and shapes I drew around my text elements are automatically misplaced.

I'm a big fan of Adobe, but they don't seem to be my fans in return.

trysteros
Participant
October 30, 2017

One of the thing that seemed to give me a solution ('after weeks of craziness) was messing with the "3D parameters" in Nvidial control panel

Go to program parameters >>> premiere pro >>>

CUDA >>>> Click on ALL, and go to "use this graphic processor" and select your card

(then I activated the triple buffer, dont know if it changed anything)

Since then, no crash at all

(sorry if labels are not the right one, I translate it from french)

Hope the solution is as simple as this one and that it will help you

Participant
November 11, 2017

For me that problem occured after updating the nvidia driver. Its obviously that there are some records in the cache files of your project which are connected to the GPU driver, in my case the nvidia gtx 970, since most of the lumetri effects are for GPU rendering.

Altough there is a message which adresses a certain frame within the timeline, this is a software bug by Adobe, but it has to do with the hardwaredriver. So dont change the effects color setting of the scene with the "cannot process frame error", or similar -  if you begin with that, the render error will be at another time code.

Just empty all the cache, best way is to create new or rename cache folder and start with brandnew. If you open older projects do the same. And hopefully will Adobe learn to tell us more helpfullier messages to solve the problem.

R Neil Haugen
Legend
July 18, 2017

If you could give a quick listing of the hardware involved ... OS/CPU/RAM/GPU/vRAM, the type of media used and how created, and the types of effects and other settings of your sequences, we could give a more useful answer.

Neil

Everyone's mileage always varies ...