BUG: Fusion Misinterprets full-range video
Posted: Sun Jul 07, 2019 3:17 pm
Over on We Suck Less, a question came up regarding some video shot on a Canon 550D in h264. Apparently the Canon records full-range values, and Fusion does not detect it as such. As a result, when the clip is read in at 8-bit, it is clipped. If the bit-depth of the Loader is changed to float, then the values are unclamped, but what should be at 0 has negative code values.
In Resolve's Fusion page (and elsewhere in Resolve), on the other hand, the values are scaled to the legal range and nothing is clamped:
The footage we were testing with is not mine to distribute, but here is the original conversation on the other forum:
https://www.steakunderwater.com/wesuckl ... =16&t=3157
This bug is also present in Fusion 9.
In Resolve's Fusion page (and elsewhere in Resolve), on the other hand, the values are scaled to the legal range and nothing is clamped:
The footage we were testing with is not mine to distribute, but here is the original conversation on the other forum:
https://www.steakunderwater.com/wesuckl ... =16&t=3157
This bug is also present in Fusion 9.