Welcome to the Premiere Pro Forum community. Thank you for taking the time to file a bug report. The team needs a little more information to begin troubleshooting. The link here How do I write a bug report has steps to provide more information about your bug that can help us identify the issue. Here to help.
Welcome to the Premiere Pro Forum community. Thank you for taking the time to file a bug report. The team needs a little more information to begin troubleshooting. The link here How do I write a bug report has steps to provide more information about your bug that can help us identify the issue. Here to help.
I am scratching my head here, I restarted Premiere to make reproducible steps. The layer/effect I created in the video still had the exact same problem, but any new adjustment layer or effect in any new project was fine.
I could copy the problematic adjustment layer OR effect onto a new adjustment layer. The issue was still there.
I could reset that effect completely, and then set a LUT and change the wheel, the issue would still be there. Even in different projects.
I have no idea why this one specific instance of lumentri is bugged.
Ok well I have found the issue but this isn't something really reproducible, it's more technical.
I basically exported the broken lumetri effect as a preset, and then a normal lumetri preset. I looked at the text difference between both files, and then applied what I thought the problem was to the normal preset; which did break it.
Ok so in the XML of the preset, one of the ArbVideoComponentParam's (which is my lumentri) StartKeyframeValue field contains Base64, here is the path to that.
<Lumetri>
# ...
<shader>
<name>"LUT"</name>
<customname>"LUT"</customname>
<opacity>"0.009999999776483"</opacity> # <-- THIS IS THE PROBLEM! The normal preset had a value of "1", but this value breaks the effect.
# ...
</shader>
# ...
</Lumetri>
I
- Updated the value as shown.
- Re-encoded that new XML.
- Replaced the StartKeyframeValue field with the new Base64 encoded XML.
- Imported the new modified preset into premiere. - Applied it -> this successfully caused the bug.