diff options
author | Oneric <oneric@oneric.stub> | 2022-11-02 17:16:15 +0100 |
---|---|---|
committer | Oneric <oneric@oneric.stub> | 2022-11-02 17:45:45 +0100 |
commit | 52783a46c0f56ccfb66795667f069a1d2993cfcf (patch) | |
tree | a81e70aab85ea937de437744a8be9825f6c3dd9d | |
parent | 113649bc9717909adcc44b246ac8e40c90391b10 (diff) | |
download | libass-52783a46c0f56ccfb66795667f069a1d2993cfcf.tar.bz2 libass-52783a46c0f56ccfb66795667f069a1d2993cfcf.tar.xz |
doc: document xy* not mangling colours on RGB video
This was confirmed on Cyberbeing/xy-VSFilter, xy-VSFilter from CCCP
and pinterf/XySubFilter + madVR.
-rw-r--r-- | libass/ass_types.h | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/libass/ass_types.h b/libass/ass_types.h index 15d6d8a..53ecfeb 100644 --- a/libass/ass_types.h +++ b/libass/ass_types.h @@ -180,7 +180,7 @@ typedef struct ass_event { * know the real colorspace of the video they're rendering to, so the * header wasn't created as a simple "Use ColourMangling: yes/no", but instead * specifies exactly which colorspace to use for the initial conversion - * from the subtitle's RGB values. So we now got + * from the subtitle's RGB values to the video's YCbCr. So we now got * * screen_rgb = video_csp_to_rgb(rgb_to_ycbcr_header_csp(ass_rgb)) * @@ -191,6 +191,10 @@ typedef struct ass_event { * renderers like libass an additional special value "None" was also added. * "None" tells the renderer to directly use untouched RGB values without * any conversion. + * + * If the video itself is already in RGB natively, then no color mangling + * happens regardless of the presence or value of a "YCbCr Matrix" header. + * * The above mangling process with special value "None" to opt out * of any colour mangling is the recommended default behaviour. * |