Survey: What min/max levels does your cam shoot?

Kommentare

RogerS schrieb am 03.04.2021 um 08:50 Uhr

@Howard-Vigorita Is that for ProRes .mov files?

Just saw a post here that says

ProRes private frame headers have no tag (neither MOV container) to specify range. By design ProRes should be always limited range. You can send full range YUV data to it (ProRes also always stores data as YUV, even if you send RGB to it) and it will preserve it, but reading app will have no clue what is the real range of the file.

https://www.voukoder.org/forum/thread/733-davinci-resolve-now-allows-for-third-party-render/?pageNo=4
 

So I guess if you decide to choose other levels you should also manually set it in post.

Marco. schrieb am 03.04.2021 um 10:05 Uhr

"It is reported in cli@ metadata as "Color range: Limited" which Vegas does not seem to pick up on."

That should't make a difference in Vegas Pro. If a clip has no color range meta data or the meta data can't be read, Vegas Pro will process the video as if it is limited range when used in an 8 bit full level project.

Reyfox schrieb am 22.11.2021 um 17:54 Uhr

Not sure if it's listed:

Panasonic DC-G9 Luminance Levels: Selectable 0-255, 16-235, 16-255

Zuletzt geändert von Reyfox am 22.11.2021, 17:55, insgesamt 1-mal geändert.

Newbie😁

Vegas Pro 22 (VP18-21 also installed)

Win 11 Pro always updated

AMD Ryzen 9 5950X 16 cores / 32 threads

32GB DDR4 3200

Sapphire RX6700XT 12GB Driver: 25.3.1

Gigabyte X570 Elite Motherboard

Panasonic G9, G7, FZ300

rgr schrieb am 28.05.2022 um 20:47 Uhr

Sony DSC-HX90V:
- AVHCD (10/16-254) - no color range meta data in the mts file - "Color space: YUV, Chroma subsampling: 4:2:0, Bit depth: 8 bit"
- MP4 (10/16-254) - "Color range: limited" (Color range: Limited, Color primaries: BT.709, Transfer characteristics: xvYCC, Matrix coefficients: BT.709)

forart.it schrieb am 11.04.2024 um 11:52 Uhr

Hi everyone, we can confirm the 16-255 range for VIXIA HF100 cameras by Canon too.

Anyway, there's an interesting (11 pages) videohelp 3ad about color range "legalization" through FFMPEG which could inspire...

Hope that helps.

EDIT

According to ChatGPT the formula for this linear mapping (= "legalization") is:

y={[(x−input_min)/(input_max−input_min)]×(output_max−output_min)}+output_min

 

Where:

x is the input color value

y is the transformed output color value

input_min and input_max sets the input color range (eg. 16-255)

output_min and output_max sets the desired output range (eg. 16-235)

This formula will map the input color value x to the corresponding output color value y using a linear transformation.

So, in our Canon HF100 (16-255) case, it becomes:

y={[(x−16)/239]×219}+16

...any opinion about this ?

Question: does Vegas automatically "legalizes" input color ranges ?

If not, how to enable/perform it ?

RogerS schrieb am 11.04.2024 um 13:22 Uhr

Vegas, like other editing programs, just looks at the metadata which indicates full or limited range. When working in 8-bit full or 32 bit full project mode it will conform the limited range files for you. However 16-255 isn't either so you can use a custom levels Fx or LUT to bring back the highlights.

mark-y schrieb am 11.04.2024 um 20:30 Uhr

Quick 'n dirty solution is a LUT

https://www.vegascreativesoftware.info/us/forum/does-your-camera-shoot-16-255-try-this-free-3d-lut--121652/

You can do the same thing with Vegas Levels:

With your Vixia HF 100 video footage, which is common the last 15 years, either of these fixes will work in an

8 bit Legacy (Video Levels) Project.

@forart.it The fix in Vegas is more simple than the math makes it seem.