Inspiring

Question

AME error involving Lumetri

Forum|Forum|7 years ago
August 6, 2018
4 replies
1970 views

Although the processor isn't the newest (i7-4770) and the memory (32GB) is DDR3 not 4, I consider that my Win10 machine is a relative powerhouse. It has a GeForce 1050Ti with 4GB. It's a custom unit I built myself and includes a 500GB SSD and a 30TB RAID to process 4K files.

My PPro and AME are apparently up to date (v12.1.2) and the Nvidia driver is the latest, 398.92.

SO...why do I have CONSTANT failures in AME exhorting 4K files with Lumetri? Here's the latest (after more than an hour of encoding):

Export Error
Error compiling movie.

GPU Render Error

Unable to process frame.

Writing with exporter: H.264
Writing to file: \\?\N:\Premiere projects\Bronx Opera\Freischutz\0513 FREISCHUTZ COMPLETE.mp4
Writing file type: H264
Around timecode: 01;11;25;17 - 01;11;25;26
Rendering effect: AE.ADBE Lumetri
Rendering at offset: 1674.206 seconds
Component: EffectFilter of type GPUVideoFilter
Selector: 9
Error code: -1609629695

I've even exported this file before successfully; I had to change a title graphic at the very beginning and suddenly something in the Lumetri commands causes a problem. I WISH Adobe could fix this so that when we choose a valid command in the program, it won't make a problem. I have these CONSTANTLY and it's always about applying Lumetri. Does ANYONE have an idea that might help make it stop, other than not using Lumetri (which seems wrong since I pay for it as well as the rest of the suite...)? Thanks; I don't mean to sound like a grouch here since you're all here to help. It's just that this was the THIRD time today for this. Thanks for understanding.

Jay

This topic has been closed for replies.

A

Anonymous

Did you try my suggestion?

E

ElJayBronxAuthor

Inspiring

Hi, Explorographer...

Ironically, the section I started with was very simple and straightforward and didn't use any Lumetri.

Since i know that opacity keyframing is on by default, I will certainly try turning it off where I use Lumetri and see if it corrects the issue.

Any thoughts why that might work?

Jay

A

Anonymous

Hey @ElJayBronx I have no idea. I think maybe these Cali folks have it out for us NY boys. It is really frustrating though. Every update that comes out...is it going to work, is it not going to work. And these failures for me at least do not happen until the end of the render. I am rendering 4k and UWHD stuff at 60fps so my render times are 2-3 hours sometimes longer.. That is a significant junk of my time lost to have to just re-render. I have started just auto-offing the opacity's keyframing now.. since doing so, I have no issues. I always use the Lumetri Cinema 25 preset for game footage as it restores the contrast to the footage nicely. Good luck. Let me know how it goes.

Kevin-Monahan

Community Manager

Jay,

The issue is related to the following, I believe:

GPU not powerful enough for the amount of GPU accelerated effects (Lumetri, etc.), given the length of your program
GPU is not powerful enough for other GPU related processing: scaling, frame rate conversion, colorspace conversion, given the length of your program
GPU is not powerful enough considering the frame size you are exporting to, given the length of your program

We will soon be recommending that 4GB VRAM is a minimum amount you should be working with. It sounds like you are operating with 4 GB VRAM.

What can fix your workflow: offload GPU centric processes to preview files which you will subsequently leverage for your export: How?

Smart Rendering: For simple smart rendering, do the following prior to export.
- Render all your timeline footage (preview files) to ProRes 422 (Mac) or GoPro Cineform (PC).
  - Note: you may need to do this in several sections as to avoid over-saturating the bandwidth of your GPU.
  - Change your codec for rendering previews in Sequence Settings. Make sure that you are set to the "Custom" editing mode to do so. All settings for previews need to match sequence settings.
- Export (using previews) with the same codec and sequence settings.
  - Call the file your "master."
  - Exports will be lightning fast since you are merely copying data, not creating wholly new processed files.
    - This faster exporting time has a lot of advantages.
    - It's faster
    - It's more stable and never fails on "Error Compiling Movie"
    - It's faster and easier to make fixes (see "tip" below)
- If you need H.264, create a copy from the resulting master via AME. Often, you can just upload the ProRes or Cineform master to YouTube, if that's your destination. The file will encode much cleaner, however, takes longer to process.
- Tip: If you see an error on playout, merely fix that section, rerender it, then export once more. Again, your exports are now very fast so fixing issues is a lot faster and easier.

More info on smart rendering.

With this workflow, I can export 4K programming at ProRes 422 with an underpowered Mac with only 1 GB VRAM.

Thanks,
Kevin

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

E

ElJayBronxAuthor

Inspiring

Kevin, many thanks for this.

I'll give it a try!

It does appear that it will take a lot more storage space, at least until I do my final export to standard mp4 which I DO need to do.

Thanks....

Jay

A

Anonymous

Try turning off Opacity Keyframing on the tracks using Lumetri... This is just infuriating. Premium money for beta products! Also, as far as the weak video card theory...maybe..but I have dual 1080ti cards...no lack of horses here...and I am getting this problem. Make sure NOTHING else is using your GPU...like...I don't know CHROME...Discord, Photoshop....etc.

A

Anonymous

Premiere is broken, it's that simple.

I've had the same thing happen... they offer these features, you spend tons of time trying to use them, then in the end they don't even work.

R Neil Haugen

Legend

For the vast majority of users PrPro is working fine.

Which is not to say that it is for everyone. So, at that point the thing to work on seems to get at what's causing issues for those who have them. Some will be because of small-width bugs, dependent on having X gear doing Y media and A, B, or C effects.

And many of what people think are bugs are actually an installation problem, corruption in a project file, driver troubles, setting of options in PrPro, all of that kind of thing.

Neil

Everyone's mileage always varies ...

R Neil Haugen

Legend

It's giving you a timecode where it failed. What's happening there?

Also, in Me, go to the preferences and de-select "import sequences natively". Unchecking that solves an array of problems.

Just for information, long-GOP media (H.264) is by nature some of the nastiest media out there for a CPU, and really rags out cores/threads and RAM. A general suggestion is 8-10 cores running as close to or above 4Ghz as possible and with as close as possible to 10GB RAM per core as possible when editing 4k LONG-GOP.

It isn't as nasty to export but still a bit of work. And if you're editing 4k long-GOP and exporting it as same, that does work your gear some.

Neil

Everyone's mileage always varies ...

E

ElJayBronxAuthor

Inspiring

Neil, I reset the project to run with the deselection you recommended.

I got another fail, although it happened 11 minutes later into the file. Both points were camera switches with Lumetri effects.

This project is multi-camera (using a Sony FDR-AX100 and a HXF-NX80; there's a strategy to the camera selection). I do the video controlling the AX100 (which I've owned for 4 years) by hand and manipulating the focus, iris and zoom (rarely this) of the NX80 (recently purchased) with an iPad. The results are amazing! No one's seen small-company opera done like this. I also take full advantage of the 4K footage and make sub-images set up as separate cameras cropped so there appear to be six cameras where there are two. I've done single-operator two and three-camera theatrical setups before (always using proxies - thanks, Adobe, for making that so easy for the last few iterations!!) but not being able to change particularly the iris makes the results problematic. The ability that Sony built in to the NX80 and its bigger cousins to spot-focus and MOST IMPORTANTLY set the iris remotely via iPad/Smartphone is a major step forward for me.

The scene in the opera where the error is appearing, the Wolf's Glen Scene (DER FREISCHUTZ), is lit dimly, in a way I need to correct with Lumetri.

Latest update: I WAS able to get the project to render correctly. As soon as I TURNED OFF CUDA, it worked fine. This limits the issue to:

a) my particular graphics card (doubt it)

b) the 1050Ti in general and its processing of AME's commands

c) The command being sent to the GPU by AME being inimical to the GPU (but NOT the CPU when GPU is removed from the equation).

Did I miss anything?

Out of caution, I logged this as a bug with both Adobe and Nvidia. I SUSPECT Adobe but can't prove it right now...we'll see what happens.

Again, thanks for your help...

Jay

R Neil Haugen

Legend

Opera ... ahh... oh my, I love that.

Let's see ... in Me you've gone to the preferences and un-checked import sequences natively, and in the export dialog have left Max Render Q and Render Max Depth un-checked also, I hope?

Neil

Everyone's mileage always varies ...

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded