Skip to main content
Participating Frequently
May 14, 2021
Answered

Infamous Lumetri error (AEVideofilter: 11)

  • May 14, 2021
  • 4 replies
  • 6772 views

Hello!
I have installed custom LUT's inside Premiere. 

(/Users/<user_name>/Library/Application Support/Adobe/Common/LUTs/Creative)
Whenever I want to browse the luts inside the creative tab, it lets me browse about 5 LUTs before the whole program freezes due to the "AEvideofilter 11" error. 


It would be really nice to be able to use Lumetri without the fear of crashing the whole program and having to save my project every 2 minutes. 

I also think that an editing software should be able to let me color grade my footage with custom LUTs. It's one of the key features in my opinion.

I know the solution is that I should never add custom LUTs to Premiere, and even if I really wanted to do so, I should use the "browse..." drop-down menu to browse looks one at a time.

To be honest, I really think the Lumetri LUT preview panel is much more convenient as it let's me browse different looks faster and shows a preview of the look before applying it.

 

Here is a quick video showing the problem, I also noticed that the selection resets after picking a LUT and I have to start browsing from the start. 

https://www.dropbox.com/s/92ypf1pnhik497p/AeVideoFilter11.mp4?dl=0 

 

This error has persisted for about 4 years, regardless of the computer I am working with. Maybe it would be time to upgrade the whole Lumetri panel? I know it would have been already fixed if it were easy, there must be a good reason why the whole color grading/correcting process is unreliable till this day.

 

Is it really so that the only way to prevent Lumetri from crashing is to use the default LUTs? 

 

I am really looking forward to the day Adobe upgrades the Lumetri plugin, it would be one of the best days of my short miserable life.


Here are my specs if it helps!

Macbook Pro 16" 2019

2,4 GHz 8-Core Intel Core i9

32 GB 2667 MHz DDR4

AMD Radeon Pro 5500M 8gb

1tb SSD

 

This topic has been closed for replies.
Correct answer Kevin-Monahan

Hi Tuomas,

We have a bug filed for this specific issue. I'll add this post to the report. I hope we can get this fixed in short order. Sorry for the inconvenience.

 

Regards,
Kevin

4 replies

Participant
June 17, 2021

I have been suffering from the exact same problem, in fact, my computer specs are the exact same besides an extra tb SSD. It's comforting to see this problem get attention and be properly written up as a bug. Let's hope it gets fixed and Lumetri gets upgraded soon!

Participant
July 28, 2021

This is the bane of my existence right now. I use a windows pc and premiere 15.4.0. 

 

R Neil Haugen
Legend
July 28, 2021

Are you using custom LUTs and getting that error code?

 

Neil

Everyone's mileage always varies ...
Kevin-Monahan
Community Manager
Community Manager
May 14, 2021

Hey Tuomas,

Sorry, man. I'm not a dev, I'm in support, but I do edit in my spare time and used to be a freelancer before Adobe.

 

My experience is that certain of LUTs don't work well with Lumetri. I can't recall if it's the format or the complexity of the LUT, but I think that they just "didn't work." They didn't throw a warning to my recollection, though. Let me try to reproduce this. 

 

Thank You,

Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
R Neil Haugen
Legend
May 14, 2021

I've seen other users post about this, and it would be frustrating. You're not alone, but then, there's not a huge amount of users (relative numbers) with the problem.

 

For me, running on my Win10 desktops and laptop, I only had this in one build around a year ago, in the 14.x build series. I can't replicate now, as I can scroll through and try any number without any issues. And I tend to hammer Lumetri pretty hard.

 

So ... why on some machines and not others? Wish I knew the answer.

 

Neil

Everyone's mileage always varies ...
Kevin-Monahan
Community Manager
Community Manager
May 14, 2021

This issue doesn't occur with any of the LUTs you use, Neil? 

 

Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
R Neil Haugen
Legend
May 15, 2021

No, I'm all 'clean', Kevin.

 

And I've got LUTs from I made in SpeedGrade, that I've made in Lumetri, that I've made in Resolve, and a few I've copied out of Resolve.

 

Neil

Everyone's mileage always varies ...
Kevin-Monahan
Community Manager
Community Manager
May 14, 2021

Hi,

Which company made the LUTs, Tuomas?? 

 

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
Participating Frequently
May 14, 2021

Hello,
It really doesn't matter where the LUTs are from, its just generally all 3rd party looks that cause the error.
I don't remember where I bought these luts shown in the video, but most of my looks are from here:
https://luts.iwltbap.com/

PosadaPhotography
Inspiring
October 20, 2021

Hi Tuomas,

We have a bug filed for this specific issue. I'll add this post to the report. I hope we can get this fixed in short order. Sorry for the inconvenience.

 

Regards,
Kevin


Using PP2021, I just experienced the exception: Lumetri Color (AEVideoFilter: 11) and I'm NOT using any custom LUTS. It happened toward the end of a long video; 1hr47m, Multicam 4Ks shot with GoPro 9s and audio recorded with a Tascam 4track audio recorder.

 

PP Version: 15.4.1 Build 6

Machine Specs

i9-32GB RAM, 31.7 Usable

Video card: Nvidia Quadro RTX 4000

8TB hard disk with about 6.5TB free.

 

I've got about 4 days of work into this video...please tell me I'm not going to loose it.