Timeline for Why does ffprobe report color space as unknown?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 10, 2023 at 4:26 | comment | added | Gyan | if videos automatically included "color space" definitions for each of standardized Red, Green and Blue, would that permit ... --> that's what the 4 color attributes are for. ffmpeg is a video processor which transforms inputs into outputs, so they must be set in the input. ffmpeg can't "discover" these properties. You can get ffmpeg to manually record some user-set values in the output but the validity is for the user to ensure. | |
| Jan 10, 2023 at 4:20 | comment | added | Gyan | how ffprobe comes up with pix_fmt of yuv420p ? --> ffprobe opens the decoder and inspects the stream. If the colorimetry attributes are not set, then it's shown as 'unknown'. | |
| Jan 9, 2023 at 20:05 | comment | added | Eric Marceau | As an aside, if videos automatically included "color space" definitions for each of standardized Red, Green and Blue, would that permit "normalizing" of generated video streams such that it would be near impossible to incorrectly remap the colors to an RGB space ... or any other for that matter? Could ffmpeg define/build a proper color space definition using such a basic triplet of info? | |
| Jan 9, 2023 at 19:48 | comment | added | Eric Marceau | Trying to understand/integrate what you said. If mediainfo is giving "color space" as YUV, and Chroma subsampling is 4:2:0, is that how ffprobe comes up with pix_fmt of yuv420p ? or is there a specific reference to yuv420p in the video header and that header does not have a value assigned to color space? | |
| Jan 9, 2023 at 4:02 | history | answered | Gyan | CC BY-SA 4.0 |