Lumteri error... Gpu video filter get frame dependencies.

[Eduard Pitka]

Hi there, i have been experimenting with luts for past few days and what really drives me crazy, that after about 5-10 minutes of color grading in lumetri, there is ALWAYS an error that completely stops Premiere. I can not do a thing when this error happens, i always have to restart premiere and open the project again, so you can imagine how this is driving me crazy.

My PC specs:

i9-9900K

RTX 2080

32 GB DDR4 3200 MHz

MSI Z390 Gaming Pro Carbon

Thanks for any kind of response.

And sorry for my english, it is not my primary language.

[R Neil Haugen]

What sort of media are you using? Other effects besides Lumetri?

What sort of disc setup do you have feeding that rig?

And ... are you making your own LUTs, or did you acquire them somewhere? And if your own or vendor LUTs, where are you parking them in your machine?

Neil

[Eduard Pitka]

H264 video 4K 25p 100 Mbps. Nope.
Samsung EVO Plus 500 GB.
I do download them from the internet. Assuming that by parking you mean where are those files, LUTs are in C:\Program Files\Adobe\Adobe Premiere Pro CC 2019\Lumetri\LUTs\Creative.

[R Neil Haugen]

BAD place to put them.

Premiere uses LUTs from it's own program files in RELATIVE order, not by name. So essentially "6th LUT in folder". Add or delete files in that folder, you've just changed which LUT is applied when.

And the LUT you use will NOT be used by either MediaEncoder or AfterEffects as they will do a relative search in their own program folders.

They publish the location for User LUTs, it's something like Users/<name>/Library/Adobe/Common but I can't paste it in on my phone sadly. Check the Overview page of the forum FAQ list.

As to those LUTs, many people make LUTs that do not always work very well. Who is the supplier for the ones that go wrong?

Neil

[BestWishesAndy]

Exact same problem here and I'm using LUTs I'm creating myself with Resolve.  Saving them in a REF folder in my project folder.  Similar build PC.

I have tried:

-Deleting Render Cache

-Removing all Lumetri attributes and fresh application

-Copying only export-ready sequences to a new project

-Media managing export-ready sequences to a new project

-Linking LUTs to a separate drive than the media/project file

-Changing edit systems to a faster/newer mobo/cpu/gpu system

-Trying on a pre-configurred Dell PC not assembled by me

Same result every time.  I can close and reopen premiere, get about 5-10 minutes of playback, then the red box pops up, playhead keeps going for a few seconds on it's own, then no active playback or render is possible.

Intel 4770k

Gigabyte z97-something

GTX 1060 6GB

32gb RAM

Samsung 860EVO 2TB

[R Neil Haugen]

Which form of LUT are you making? Could you share one of those for me and others to test on our rigs? I can't repro any of this with LUTs either from Premiere or Resolve on my system.

Oh ... could you create a LUT in Lumetri, and see if that has the same issue?

Neil

[BestWishesAndy]

https://www.dropbox.com/sh/0jcnxt9cwi3ybdi/AAC9eQFnleJUp2QjcWHebs14a?dl=0 

Uploaded here for ref

[BestWishesAndy]

Sure Neil!  It was a 1:30 video, so pretty short.  Some of these were applied to multiple shots, but each shot had a LUT.  Took about 5-10 minutes of playback for it to jam up.

Thanks for checking it out!

[R Neil Haugen]

I'll check this out at the shop in a bit.

Neil

[R Neil Haugen]

I've spent 15 minutes playing the first LUT, the "cole slaw side ... chicken" one, without any problems. i-6800k @3.2Ghz, 32GB of RAM, GTX1600 for the GPU.

Interesting ... most of my .cubes are between 100 and 900 KB, this one is 6,724KB.

Neil

[ExoJordy]

regarding the kb size of that .cube file, it could signify that the lut is a 65 point cube lut, rather than a 33 point cube lut, could this be the problem? I am unsure wether or not Lumetri can really support 65 point cube luts

[R Neil Haugen]

That is a very large LUT, and could be a problem point. Especially that might be more difficult on some gear than others.

Neil

[ExoJordy]

I have had the same problem when using 65 point cube luts in feature length projects, i'm assuming that is the main reason for this issue