Skip to main content
M
mikek25490304
Participating Frequently
April 1, 2018
Question

Low level exception occurred: Scaling, Lumetri, & RED 5K

  • April 1, 2018
  • 8 replies
  • 16557 views

I have been having significant issues with Premiere Pro. I saw someone in another discussion post their question in this format so I'll give it a shot to see if there is enough info here for someone to help me out

PROBLEM

The issues I get are very inconsistent and confusing. And they all usually ramp up drastically whenever I am using Lumetri to grade. To clarify, I have been having these issues across 20 or so different projects over the past 6 months.

I've gotten these issues (in order of most common and frustrating):

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

  • This happens ALL the time.
  • have to restart premiere thru Task Manager
  • Happens when I'm using LUTS installed into my creative folder, or LUTs that I browse for that stay at the same spot on my computer and don't move.

-A low level exception occurred in: RED Source Settings(AEVideoFilter:29)

  • This frequently occurs as well

-Exporting errors that stop an entire export

  • I forgot what its called but its something like "A low level exception occurred. Unable to Process Frame. Lumetri error..."
  • I have to restart premiere several times and every now and then I'll get lucky and my project will actually export all the way thru

-A low level exception occurred in: Mask (AEVideoFilter:15)

-Error Compiling Movie: Unknown Error (when rendering)

-Premiere Pro encountered an error: [D:\Haberdasher\releases\2017.08\PremierePro\UIFramework\Src\EditControl

  • I've seen this just twice


I don't usually change anything to fix these issues. I just re-start Premiere. But its getting to the point where I have to do this VERY frequently. 6-8 times an hour when I'm grading. Sometimes I can ignore the errors and continue editing but then premiere will just crash anyways. Then I have to close it from Task ManagerScrolling through the Creative luts that i've installed into my system will cause the Lumetri issue after a couple minutes of scrolling.
COMPUTER INFO

  • OS: Windows 10
  • Processor: AMD Ryzen 7 1700 Eight-Core Processor 3.00 GHZ
  • Installed memory: 32.0 GB
  • System type: 64-bit Operating System, x64-based processor
  • Motherboard: ASUS Prime 5350-Plus
  • Graphics Card: EVGA GeForce GTX 1060 GAMING, ACX 2.0 (Single Fan), 6GB GDDR5

HARD DRIVE INFO

G-Technology G-RAID 16TB, USB 3.0. 7200 RPM drives

PROJECT INFO

  • Premiere Version: Premiere Pro CC (2017) 12.0.0
    • updating premiere doesn't fix my issue. I was having same issues on older builds.
  • Footage: R3D, 5120x2160, 23.976fps, REDcode 8:1, to 11:1,  REDLogFilm, About 2.5 TB of footage)

Sony FS700 2K ProRes 422

FAILED FIX ATTEMPTS

  • Switched from GPU Mercury playback to CPU
  • Switched RAM from Performance to Memory
  • Updated graphics card driver
  • Uninstalled Premiere and reinstalled
  • Cleared the media cache folders

Could I be having a hardware issue? Why am I constantly unable to edit smoothly? The Lumetri issue is a big deal but the random RED Source Settings errors are super annoying and time-killers as well.

Moderator Note: Customer has AMD processors, which is a common link on the major threads in this post.

This topic has been closed for replies.

8 replies

R Neil Haugen
R Neil Haugen
Legend
May 5, 2020

rayovacson,

 

What is your hardware and media? The type of thing that causes the issues noted in the original post is actually several different and unrelated things. So when someone is having this, solving for that is necessary. OS, Gear, media, and effects used are all important. Note, on the original post of this thread from two years ago, the Moderator note that (at that time) the issues were most commonly raised with AMD GPUs.

 

But ... the majority of AMD GPUs being used with Premiere currently are newer with vastly different architecture than those GPUs. And may or may not have any problems with RED media, which is the primary media this thread was about.

 

For example, on my Win10 rig, 6-core/32GB RAM 1060/6GB, I'm not having any issues with RED media. Other than it can at times slow the rig down a lot, as I need get a newer more robust system. But I can edit and export without issue as can most users.

 

Even my Acer Predator Triton 500 laptop can work with and export RED media. Again ... by the time I'm trying 6k RED, my playback is pretty poor. Yea, I proxy a lot. But again, I can work with the media without issue.

 

Give us some data ... so we can try to puzzle out what the issue/s is/are.

 

Neil

Everyone's mileage always varies ...
carlosa18006132
carlosa18006132
Participating Frequently
July 14, 2021

Has this issue been resolved? 

 

I just added an 18 luts package to Premiere Pro to the creative folder I created, this is the path:

 

 

But I'm getting the low-level exemption error when I scroll down the list of luts under the creative tab in lumetri and the application crashes. What should I do in order to see a preview of my footage with the lut applied and not getting the error?

 

Is it possible that the error has to do with the fact that there are two locations for the luts? The one I showed and the application package (I added them to the first folder):

 



Thise are the specs of my computer:

 

 

 

thanks

 

Kevin-Monahan
Community Manager
Kevin-MonahanCommunity Manager
Community Manager
July 14, 2021

Hi Carlos,

Those look like Input LUTs not Creative ones. Can you place them in the proper folder and then see what occurs? Let me know.

 

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
R
rayovacson
Participant
May 5, 2020

Hello there,

 

Did you ever get a solution from Adobe?  This error is on so many websites/youtube pages its insane.  They are obviously aware of the lumetri crashing/error is there a definate solution?

P
parjanyaholtz
Participant
September 12, 2019

Posted about this yesterday, but my post got deleted?! Have a very similar issue on a 2019 15 inch MBP with RED raw files. Getting no issues while editing, but I can't export with a LUT adjustment layer for some reason. Crashes PP with a critical error, or freezes Media Encoder (also had the low level exception error pop up at least once on ME). Doesn't seem to matter which LUT I use. Tried all the regular fixes (emptying cache, copying sequence to a new project file, etc.). This is very very frustrating.

J
jvonmutius
Participating Frequently
May 17, 2019

I'll chime in here that I'm having the same trouble as the original poster, but I am NOT using any LUTs. So while LUTs may trigger this problem, they are NOT going to fix the issue. I am working in a project with about 10,000 R3D clips of various sizes from different RED cameras. I was running into the low-level exception errors primarily when making ripple edits in a 40-minute sequence, but also when doing match frame and moving R3D clips to a different track. Ever since updating to the latest version yesterday, the errors seem to be more frequent, and I now cannot change the R3D settings in Premiere without getting errors. If I go to the Effect Controls for the master clip and hide the R3D settings, the clip will show up fine in my Program Monitor. But if I show the R3D settings, my Program Monitor just shows a black screen.

COMPUTER INFO

  • OS: Windows 10
  • Processor: AMD Ryzen 7 1700X Eight-Core Processor 3.40 GHZ
  • Installed memory: 32.0 GB
  • System type: 64-bit Operating System, x64-based processor
  • Motherboard: ASRock x370 Taichi
  • Graphics Card: EVGA GeForce GTX 1070 Ti

Moderator Note: Customer has AMD processors, which is a common link on the major threads in this post.

R Neil Haugen
R Neil Haugen
Legend
May 17, 2019

Did you update Premiere versions?

If so, from what to what?

Neil

Everyone's mileage always varies ...
J
jvonmutius
Participating Frequently
May 17, 2019

I updated to 13.1.2 (Build 9). I can't tell you exactly what version I updated from but it was CC 2019, so some flavor of 13. If there is a way to find out what version I was previously on, I'll look it up, but now that I've updated, I don't think I can find out.

Kevin-Monahan
Community Manager
Kevin-MonahanCommunity Manager
Community Manager
May 11, 2018

Hi MikeK,

Are you still having this trouble? Let us know.

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
D
danielr18964632
Participant
April 11, 2019

I'm having this same exact problem.

R Neil Haugen
R Neil Haugen
Legend
April 11, 2019

So you're having the same error messages as the OP with similar media?

Or with Film Riot LUTs?

No way to know from your post. Details not only help, they are often crucial.

And also exactly where the LUTs are stored on your machine is important.

Neil

Everyone's mileage always varies ...
benjamina84899357
benjamina84899357
Participant
April 5, 2018

I Had the same problem with R3D files on 12.1, went back to adobe CC 12. 0, works fine now..

R Neil Haugen
R Neil Haugen
Legend
April 5, 2018

Strange ... apparently it works for some of us but not all. I do know of others working in r3d without issue, as I can. So, please do report this!

Are y'all Mac or PC?

Neil

Everyone's mileage always varies ...
E
excited_Genie16B8
Legend
April 1, 2018

I don't use or have any RED footage for testing.  The two most prominent ideas I have are Steps 2M and 4A below.

Unofficial Premiere Pro Troubleshooting Guide

    M
    mikek25490304Author
    Participating Frequently
    April 2, 2018

    Thanks for the tips.

    Regarding Step 2M:

    Wouldn't turning off CUDA drastically slow everything else down?

    Regarding 4A:

    I have media caches and render files each going to separate internal drives. and original media+exports on the external 16tb drive. I have my project file on the same external drive as the media. Also I'm using a 24" 4k monitor.

    The only thing I'm not doing in tip 4A is using only intel/nVidia hardware. You think that could be the culprit? My computer specs listed above.

    I really want to find a way to smoothly work on a windows machine before I decide to switch back to Mac, where I never had these issues and not nearly as many issues in general.

    I've seen similar problems on my business partner's HP workstation, when I took a project that I graded on my machine and opened it on his. There were similar lumetri issues, but I was using his machine for way less time so I couldn't tell how frequently they would occur.

    E
    excited_Genie16B8
    Legend
    April 2, 2018

    Turning off CUDA can slow things down dramatically, but it is occasionally the only thing that helps with these errors.

    There's no way to know if the Ryzen is at fault here.  You could switch and still have this problem.  It's general advice I offer because there have been issues in the past when using AMD hardware.  Often, the CPUs don't have the full instruction set that PP is capable of using.

    Warren Heaton
    Community Expert
    Warren HeatonCommunity Expert
    Community Expert
    April 1, 2018

    I've been getting the "A low level exception occurred in: Lumetri Color (AEVideoFilter:11)" after running the most recent update from 12.0.0 to 12.0.1.  I don't have any details about it, though.  And, it's macOS High Sierra 10.13.2.

    One of the more interesting crashes left the audio playing in the Timeline while I was able to interact with Premiere, but neither the Program Panel nor Source Panel would refresh.  It's one of the more bizarre crashed I've ever had in PR.  I screen recorded it.  If I can get the client to approve showing the footage, I'll post it at some point.

      benjamina84899357
      benjamina84899357
      Participant
      April 5, 2018

      Same problem, wirh Red Footages .r3d files.

      Tried to open a project in Premiere pro CC12.1 today, and I have Low level execption warning " too.

      Project used to work fine on older vesions....

      now it doesn't

      Did you find a solution ?

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices