#6440(undetermined:new): Support and re-export of floating-point RGB-type color spaces (e.g. for YUV -based input)
#6440: Support and re-export of floating-point RGB-type color spaces (e.g. for YUV -based input) -------------------------------------+------------------------------------- Reporter: mtc | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- sYUV or sYCbCr-based color spaces' domain contains colors that if transformed into sRGB that are often clipped or clamped which discards the data but may be useful (defined in exif2.0 sYCC (most modern camera jpegs)) negative values represent values outside the RGB primaries, and for YUV incidentally, ceiling-clipping is most evident for blue-color channel (e.g. lightning pictures), if ffmpeg supported openEXR output, perhaps, this data could be recovered (export to programs that support HDR), also higher bit-precision (may avoid barely-noticible posterization banding fron rounding when transforming color space) it no dithering used in highly smooth-low-noise areas also paves way for xvYCC based support, also note sRGB curve definitions for negative values how the function is defined. use case include importing camera pictures that are overexposed in the RGB but not YUV channel thus blues seem washed out.. -- Ticket URL: <https://trac.ffmpeg.org/ticket/6440> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker
#6440: Support and re-export of floating-point RGB-type color spaces (e.g. for YUV -based input) -------------------------------------+------------------------------------- Reporter: mtc | Owner: Type: defect | Status: closed Priority: normal | Component: Version: unspecified | undetermined Keywords: | Resolution: duplicate Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by cehoyos): * status: new => closed * resolution: => duplicate Comment: Apparently a duplicate of ticket #3657. -- Ticket URL: <https://trac.ffmpeg.org/ticket/6440#comment:1> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker
#6440: Support and re-export of floating-point RGB-type color spaces (e.g. for YUV -based input) -------------------------------------+------------------------------------- Reporter: mtc | Owner: (none) Type: defect | Status: closed Priority: normal | Component: | undetermined Version: unspecified | Resolution: duplicate Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by Balling): Oh, very interesting. -- Ticket URL: <https://trac.ffmpeg.org/ticket/6440#comment:2> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker
#6440: Support and re-export of floating-point RGB-type color spaces (e.g. for YUV -based input) -------------------------------------+------------------------------------- Reporter: mtc | Owner: (none) Type: defect | Status: closed Priority: normal | Component: | undetermined Version: unspecified | Resolution: duplicate Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by Andrew-R): speaking about xvYCC I found two documents: https://www.researchgate.net/publication /250999893_192_xvYCC_A_New_Standard_for_Video_Systems_using_Extended- Gamut_YCC_Color_Space and preview/sample of iec-61966-2-4 (it works as of today, I saved it just because) https://cdn.standards.iteh.ai/samples/14431/9e5a80b3c1a54ad0866f818def33466c... so it seems those opto-electrical and inverse transfer functions are simple, but defined as 3 separate segments? -- Ticket URL: <https://trac.ffmpeg.org/ticket/6440#comment:3> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker
#6440: Support and re-export of floating-point RGB-type color spaces (e.g. for YUV -based input) -------------------------------------+------------------------------------- Reporter: mtc | Owner: (none) Type: defect | Status: closed Priority: normal | Component: | undetermined Version: unspecified | Resolution: duplicate Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by Balling): There are more pages in the standard, Annex A, Annex B, Annex C. I have it, but, I suppose I should not post it... Anyway, yes, same EOTF was used by Photo CD. -- Ticket URL: <https://trac.ffmpeg.org/ticket/6440#comment:4> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker
participants (1)
-
FFmpeg