I tried to reproduce your issue but couldn't. Which plugins are you using in addition to Advanced Lightning to generate glow etc?
Some troubleshooting points:
In Project Settings, switch to Software Rendering to eliminate errors that may be occurring on the GPU side.
If you switch to 8bpc or 16bpc, rather than 32bpc, does the error still occur? What if you stay in 32bpc but add a colour profile? What if you then linearise?
Note that Advanced Lightning is an 8bpc effect, and heed the warning from Adobe:
Here's what I'm using to make my lightning effects. My project settings are set to software rendering. The error goes away at 8 or 16bpc. I've toggled through several color profiles and toggled linear on and off, the clipping artifact still remains. If you're looking to replicate what I'm getting, it's worth stressing that each bolt of lightning is on its own separate layer and the layers are all set to screen.
1 person found this helpful
Okay, using your same effects stack I was able to replicate the issue. It appears to be some kind of mathematical error in the 32bpc math involved. If you turn off the Glow and Exposure effects it disappears, so some combination of their actions and the Screen mode seem to create the error.
Workaround: change your blend mode to Add rather then Screen. You'll get slightly "hotter" blends, but the error doesn't seem to occur in this mode.
i've fixed stuff like this before by sandwiching the effect <levels> set to clip 32bpc placed just before the 8 bpc effects.
also, compander effect is useful for some hdr effects as well with the Compress-Expand Dynamic Range animation preset.
In this way, you can use tools that don’t support HDR color, such as 8-bpc and 16-bit effects.
Sorry for this issue. Did you ever find a solution? Please let us know if you have or if you still need help.
Yes. Just tried Chris and Andrew's methods and they both worked. Chris's worked better since it preserved the blending intensity I had set up.