Participant

Answered

Premiere Pro CC Encoding Failed A low-level exception occurred in: Lumetri Color (AEVideoFilter)

Forum|Forum|10 years ago
June 26, 2015
47 replies
92487 views

Trying to export video to DVD format (MPEG2-DVD).. It starts to render video "normally" up to 10-50 minutes.. Tried multiple times, changed video quality and changed output drive, always interrupting with same error code..

Is there something to do..?

- Encoding Time: 02:22:33

06/26/2015 09:40:48 PM : Encoding Failed

------------------------------------------------------------

A low-level exception occurred in: Lumetri Color (AEVideoFilter)

Export Error

Error compiling movie.

Unknown error.

This topic has been closed for replies.

Correct answer Kevin J. Monahan Jr.

Hello,

If you have a solution that you found, please return to the thread and let us know. We can only assume that you solved your issue. Typically, one will get these kinds of errors when you've exhausted system resources like VRAM, system RAM, or both.

The solution or workaround is to use Software Only mode for the Mercury Playback Engine. You can also purchase additional hardware which may assist the job.

Thanks,

Kevin

Show previous replies

mishab38348624

Participant

I have just purchased a new set of LUTs and it is now causing a Low Level Exception error. Can you tell me if I need to change something in my settings to allow these LUTs to work? We did not have this issue before we installed the new LUTs.

jumpman6323

Participant

im having a similar problem, I am importing my own LUT's and i keep getting this:

C

christiangoehler

Participant

Hey there,

i've got the same problem in Premiere CC. I use a MacPro 5.1, macOS Sierra (10.12.5 (16F73)) with 48GB DDR Ram and NVIDIA GeForce GTX 980 (newest driver & CUDA version). The error always appears when I click through the Lumetri color view ("creative - look"). After a short warning ("a low-level exception occurred in: Lumetri-Farbe (AEVideoFilter:11)") Premiere (2017.1.1) always crashes. I've tried to change the mercury playback engine from CUDA to "software only" and the other options - but this doesn't solve the problem. Unfortunately the program is not usable in this way. Please repair as soon as possible.

E

extrabyte101

Participant

I'm sorry Kevin, [abuse removed by moderator]

[be civil or risk being banned from the forums]

Kevin J. Monahan Jr.

Community Manager

Hello extrabyte101,

I'm sorry Kevin, but you really are an idiot. All you do is give useless workaround suggestions and no actual reasons why this is happening and without admitting that these are serious issues that Adobe never acknowledges(you know, because they're perfect . . .) that need to be fixed once and for all.

I am not an engineer. I am not a product designer. I am in support and doing my job the best I can. Kindly refrain from name calling as that is not tolerated on these forums.

I ask questions so that I can provide information and feedback to engineering so we can get a solution to some of these problems. I ask others to file bugs so that we can work on fixing the issues that face customers. I am well aware that these are serious issues for everyone that experiences them. I was an editor for many years before coming to Adobe, so I know the pain.

Why are these issues happening? For a variety of reasons, I imagine; mostly related to working with large format Long GOP footage on underpowered systems, working without media drives, adequate GPUs or RAM, or some system anomaly related to media. There are a large variety of factors in play, each case is seemingly unique. The suggestions (workarounds) I have made so far have worked for me on my own projects, even on a somewhat underpowered system. Sorry, if you don't find them useful.

Every year (after the brutal slap in the face when you blindsided everyone with the new subscription model) and with every "so called update" things get worse and worse.

Let the product team know how you feel here.

Please stop giving useless advice and put someone on here that can actually say something helpful.

Sorry if you aren't fond of the info here, but most of it is advice I get is directly from engineering. So feel free to let them know that you'd like to have more engineers in the forum here—perhaps that can assist the situation.

Regards,
Kevin

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

filmkeith

Participant

I've had a similar issue. My Adobe Premiere Pro CC 2017 is acting very sensitive. It keeps giving me "low-level exception errors" and locking up while I am creating mattes, using soften more than a small amount in the key effects, and making certain color adjustments. I tried to find the folder you indicated in your solution to this issue, but I don't have the folder path. I am using a Dell Precision T3610, with an Intel Xeon 3.7GHz Processor, 32.0 GB RAM. I have Windows 10 Pro and Mercury Playback Engine GPU Acceleration (CUDA) (I tried turning this off, as suggested). My system only started doing this recently. I would greatly appreciate any help you can give me. It sucks to have to keep closing and reopening the program.

Kevin J. Monahan Jr.

Community Manager

Hi filmkeith,

Sorry for your performance issues. I appreciate the notes you gave. I would want to know more details about your Timeline, effects, source media, info about your hardware (your GPU/CPU info) and anything else you can tell us to help you move forward. Can you give us more info, please?

Thanks,
Kevin

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

L

LineP

Known Participant

Also appears in 2017.1......

No LUT's applied

Tried two different computers. One with a FirePro W8100, the other with a GTX 1070.....

Kevin J. Monahan Jr.

Community Manager

Hi,

Some users report that the following things may assist your exporting issue and prevent this error:

If you are exporting directly to H.264
- Export to a mezzanine codec, like ProRes, DNxHD, or Cineform, to create a "video master" instead
- Create H.264 clips from this master
If you are not exporting to a separate hard drive
- Encode to a different hard drive than your OS and programs are installed on
- Ensure that it high-speed drive and connected via a fast port for reliable performance
Reduce or remove GPU accelerated effects
Do not use Lumetri effects from previous installations of Premiere Pro
Do not use or move Lumetri effects or presets from other versions of Premiere Pro
Do not update the project from one version to another without swapping out Lumetri effects
Update hardware
Transcode to a smaller frame size on ingest
Add LUTs on ingest
Scale down on ingest
Reduce the length of your Timeline

Thanks,
Kevin

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

J

jho678

Participating Frequently

How about Adobe providing a program that actually allows the unproblematic use of basic functions like color correction and rendering to h.264, instead of forcing users to fall back on ridiculous "workarounds" that might or might not solve the problem?

For the record, I'm having the same low level error with lumetri on a regular basis, but fortunately it is not so frequent that it keeps me from getting work done.

My system:

Windows 10

32 GB RAM

Quadro M4000

Premiere 2017.0.2

Also im getting constant "low system memory" warnings while editing and/or rendering, although I dedicated 16-18gb Ram to the system. This looks very similar to the memory leak problem as with early CC 2015.

Adobe should really get a grip on this problem!

Kevin J. Monahan Jr.

Community Manager

Hi Jho,

How about Adobe providing a program that actually allows the unproblematic use of basic functions like color correction and rendering to h.264, instead of forcing users to fall back on ridiculous "workarounds" that might or might not solve the problem?

If you have a system capable of what you are attempting, then you should have little or no trouble with standard workflows. The trouble is that I don't know anything about the length of your Timeline, the number, and intensity of effects you are carrying, how you are exporting or which camera is providing the source media; the "what you are attempting" part, that is.

It may be that you still need to transcode on ingest or do some other such workflow to get reliable results. I would suspect that you might get better performance with a GPU with newer architecture and more CUDA cores. Again, it depends on what you are doing.

Also im getting constant "low system memory" warnings while editing and/or rendering, although I dedicated 16-18gb Ram to the system. This looks very similar to the memory leak problem as with early CC 2015.

Sorry about this. If you have updated a large and complex project, I have seen this happen to people with corrupt projects. I have not been able to reproduce this error on my test machines, however. Can you try a test with a new project to see if this might be the case? Or does the issue appear on your system with brand new projects, as well?

Thanks,
Kevin

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

R

RubberDucky20

Participant

Having the same issue except I can't even edit footage to render it because the error comes up the second I add Cosmo from Red Giant during editing. I've used this filter sparingly before and never had this happen. I get the error cosmo:aevideofilter:11 and then it pops up saying there are 30 low lever exceptions. I've tried using different clips and have even tried using the same effect in After Effects but I get the same thing. I tried clearing out the media cache (not sure if it helps but hey worth a try), and even reverting to older versions of PP. I found it odd that I hadn't changed any setting, my drivers are up to date and no real changes have been made and this issue suddenly occurred =/

Hope we can all find a solution

B

brady19755161

Participant

I keep getting this error when I use titles on a stills slideshow;

low-level exception occurred in: Lumetri Color (AEVideoFilter):11

Any solutions?

gtx 1060

16gb ddr4

windows 10

G

Griff2wenty3

Participant

Adding my name to the list in hopes there is someday a solution. I too am experiencing this problem when applying LUT's through the Lumetri panel.

PPCC 17.02

4K/23.97 and 1080/120 Footage

System:

27" iMac Retina 5K

i7 4.0 GHz

24gb RAM

AMD R9 M395 2048 MB

OS 10.12.3

S

ScubaBadger

Inspiring

Same here (A low-level exception occurred in: Lumetri Color (AEVideoFilter:14)

PPCC 15.4

4K footage

Log applied

Lumetri applied to all clips

C

CamElkins

Participant

I found a fix to this: Remove any colour grade from the morphcut clips. Then NEST the morphcut clips and then apply our colour grade/Lumetri/Lut to the nested clip.

Worked first time for me after many failed renderings.

Show more replies

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