I know I’ve posted about this recently but I am certain a quick answer will get it through my skull properly… Apologies if this is unnecessarily using up forum/dev space and time…
I need confirmation this is doing what I think it’s doing. That’s all.
I have a Sony Camera which can aquire in both 0-255 as well as 16-235 using the different Picture Profiles. I’ve done lots of tests and as far as I can see it does record in 16-235 and 0-255. Please see an example of the 0-255 (Even though I’ve chopped of the top of the screenshot the Luma does in fact show 0-255 in the example):
This is where I’m confused. And part of it stems from my research where Dan mentions that people who are often having problems with their files not being signalled properly. This seems the case here. The MP4 file is shown both in the mediainfo file and and in the Colour Range as being Limited, that is 16-235.
The most reasonable conclusion I’ve come to understand, is this:
1: The files are not being signalled correctly. My camera shoots in either 16-235 or 0-255 depending on the Picture Profile chosen. However, the files are just rendered illegally for the 16-235 and record luma in the range of 0-255 regardless.
2: Shotcut doesn’t actually do anything to the files it treats all files as 0-255 and lets the dice fall where they may. That is, a 16-235 luma file is placed in the correct range by default. Hence my illegally signalled files work because shotcut just leaves the illegal data in the files and doesn’t strip them.
3: I can’t see how my files can show 0-255 range if there isn’t 0-255 luma in there?
Is this correct? Thanks very much in advance for any replies.
I’m partially coloured blind (which is what you might be hinting at?) and rely on the scopes and knowledge of lighting to guide me. Which means I’m running blind as it were.
That’s part of my worry as I’ve seen inconsistant behaviour with different filters and have seen that with my own eyes (I think the one I noticed happening on is Levels). If I change the range to full (jpeg) it just squashes the range which seems counterproductive.
I’ve been experimenting with using ffmpeg to correctly signal the files by force rewrapping them to being properly labelled. Not sure this is a good path to go down.
One thing you should know is I can see clear as day on the different Picture Profiles that the one that is supposed to be 0-255, is (albeit rarely) on the scope, and the one that is 16-235 stays in the constrained range.