I am 99% sure that the Fall algo has nothing to do with it.Arrival from 1:01:50 to 1:02:30 has several visible brightness adjustments - at least for me. This is exhibited by both the recent live algo and also from my tweaked measurement file playback for this title. Curious if this could be from the way the Fall algo treats this material and not just scene change detection at play? Hoping @Soulnight might review?
EDIT: Might just be a scene change issue. I will retest later so maybe wait if not that interesting.
Probably a scene change issue.
2 evils possible:
the target nits gets resetted at scene change at a bad time.
You can get a visible brightness jump between 2 people discussing with camera change but the viewer sees it as "one single scene".
- LIVE algo current implementation always reset at each scene cut and will definitely display a lot of the associated issues
- Our tool behaviour depends on the settings used. Default settings try to avoid this kind of unwanted reset.
Huge change in brightness and scene cut not detected.
- Our tool may try to smooth this out with the rolling avg which can result in pumping.
- Live algo will be either too dark or overblown if big scene is missed.
So the default settings in our tool try to avoid both bad options.
Can you share the settings you are using?
And also maybe share a video sample to look at the issue?