R Neil Haugen wrote:
Well ... if I'd heard about the use of the Canon 7D SL Profile Look, at the beginning, I'd a said remove it. That Look preset IS your issue.
There was a whole group of camera-specific "Looks" created for PrPro that were in the 2014 releases. The reason those are all in a 'Legacy' folder in the 10.x builds of 2015.3/4 is because there were a LOT of users that had issues like this with them. So they removed them from the easily-findable ones that people 'browse' though they're still loaded with the program IF ... you insist on using them anyway.
Yea, with a bit of practice, you can make better ones for yourself anyways.
Neil
Well... there's more info... there's so much info that I had difficulty getting that last post out so forgive if I'm trickling things out but I'm trying to keep things simple while providing good contextual info, not always easy...
For clarity... since talking about this issue in the last month or so, I've been working on two separate Premiere projects. Both use footage from the same DSLRs but the first one only used Lumetri effects without LUTs... no LUTs used with those, and I experienced the same old "AE.ADBE Lumetri...GPUVideoFilter" error we've been primarily discussing here. The main point here is that my instances of this "AE.ADBE Lumetri...GPUVideoFilter" error have been largely associated with a project not using any LUTs. In fact, the first time this newer project failed with this error was this particular failure I outlined today... I've not been working on this project much though, just a little bit here/there, whereas the other non-LUT project was worked on quite a bit, with lots and lots of exporting/rendering, and experiencing quite a large number of "AE.ADBE Lumetri...GPUVideoFilter" failures.
Also, I want to make sure we're talking about the same thing here... see the following Effects panel with expanded Lumetri Presets...
![]()
The location of "SL Neutral Start (Canon 7D)" does not seem hidden or legacy, yet it will turn into "CANON 7D - SL - PROFILE"... let me explain...
I thought I had dragged something from the above because I recall looking at the "Canon 7D" node under SpeedLooks... but I couldn't explain why it said "CANON 7D - SL - PROFILE" because I could not find that anywhere. Since it's relatively Neutral footage, I thought it might have been the "SL Neutral Start (Canon 7D)" Preset... I remember trying a bunch of those to see the results. Long story really much shorter believe or not... I did a test today with "SL Neutral Start (Canon 7D)" and found out it says "[Custom]" for the LUT immediately upon placing the effect, but after closing the project and reopening it, the LUT will no longer be set to "[Custom]" but rather it will be set to the unexpected "CANON 7D - SL - PROFILE". This seems like a bug because something which has one setting before saving a project shouldn't change after reopening it. I mean, the preset has one name, the LUT initially shows [Custom] but then changes to "CANON 7D - SL - PROFILE" ...
I assume you mean to indicate the above Presets are OK to use, not legacy, but that using the hidden "CANON 7D - SL - PROFILE" file (in the legacy folder) directly is bad... or are you saying all are bad and lead to these failures?
The above panel doesn't seem like a place for legacy presets... they seem very much as though presented for happy use... The preset in question is in clear view, but if you use it, it will textually turn into "CANON 7D - SL - PROFILE" after you reopen the project, and you say that LUT is legacy and should be avoided. Confused here.
If I create a Lumetri effect using the "SL Neutral Start (Canon 7D)" preset (as show in the above Panel), and then save that as my own Preset, then export that preset, internally in the preset xml file I can see it referencing the legacy the path "...\Adobe Premiere Pro CC 2015.3\Lumetri\LUTs\Legacy\CANON 7D - SL - PROFILE.itx " ... are you saying using those presets under SpeedLooks, in plain site, are all the same thing as using undesired legacy LUTs? I ask because you could mean simply using the legacy LUT directly is bad, and not the above indirect presets because they do things "right" or some such.
A side note... I don't have to use these presets or LUTs... I just experimented with my relatively so-called neutral footage and liked what I saw so said what the heck. I can remove and simply adjust things I guess... but I want to ensure I get your meaning on using the above presets first.
Regardless... it's clear that this same single "AE.ADBE Lumetri...GPUVideoFilter" error occurs for reasons that can have nothing at all to do with the GPU in a functional sense as well as in the sense of what initiates the problem. I mean, if a system can render most of the time, but then fails due to a configuration change, it's hard for me to see that as an "old" GPU issue... not that you don't know this already but since there's apparently a whole slew of complexities in discussing this type of failure, it seems good to clarify this in closing.
