minor fixes for Android

[goodguy/cin-manual-latex.git] / parts / Attributes.tex

diff --git a/parts/Attributes.tex b/parts/Attributes.tex
index fc7f99659188912155f3a93c2b263ccea538da0a..9f466c3638eae5665d830df04eb675e2851154d7 100644 (file)
--- a/parts/Attributes.tex
+++ b/parts/Attributes.tex
@@ -198,7 +198,7 @@ range.  16 bit integers were used in the past and were too lossy and
 slow for the amount of improvement.  RGB float does not destroy
 information when used with YUV source footage and also supports
 brightness above 100\,\%.  Be aware that some effects, like
-Histogram, still clip above 100\,\% when in floating point.
+Histogram, still clip above 100\,\% when in floating point. See also \ref{sec:color_space_range_playback} and \ref{sec:conform_the_project}.
 
 \item[Interlace mode:] \index{interlacing} this is mostly obsolete in the modern digital
 age, but may be needed for older media such as that from broadcast
@@ -228,6 +228,30 @@ Generally, best practice is to perform the following sequence of preparations fo
        \item Whole editing: if you need to change frame rate of some restricted part, particularly when smooth acceleration/deceleration is needed, it can be done here. But if frame rate has to be changed only due to different source fps, it is better to do it during the preparation stage.
 \end{enumerate}
 
+\CGG{} does not have color management \index{color management}, but we can still give some general advice on how to set color spaces:
+
+\begin{enumerate}
+       \item Profiling and setting the monitor: \\
+       source: \textit{sRGB} $\rightarrow$ monitor: \textit{sRGB}  (we get a correct color reproduction) \\
+       source: \textit{sRGB} $\rightarrow$ monitor: \textit{rec709} (we get slightly dark colors) \\
+       source: \textit{sRGB} $\rightarrow$ monitor: \textit{DCI-P3} (we get over-saturated colors) \\
+       
+       source: \textit{rec709} $\rightarrow$ monitor: \textit{rec709} (we get a correct color reproduction) \\
+       source: \textit{rec709} $\rightarrow$ monitor: \textit{sRGB} (we get slightly faded colors) \\
+       source: \textit{rec709} $\rightarrow$ monitor: \textit{DCI-P3} (we get over-saturated colors)
+       \item It would be better to set the project as RGB(A)-FLOAT, allowing system performance, because it collects all available data and does not make rounding errors. If we can't afford it, starting from YUV type media it is better to set the project as YUV(A)8, so as not to have a darker rendering in the timeline. On the contrary, if we start from RGB signals, it is better to use RGB(A)8. If we don't display correctly on the timeline, we'll make adjustments from the wrong base (metamerism) and get false results.
+       \item Among the rendering options always set the values \\      
+       \texttt{color\_trc=...} (gamma correction) \\
+       \texttt{color\_primaries=...} (gamut) \\
+       \texttt{colorspace=...} (color spaces conversion, more depth-color); \\
+       or \\
+       \texttt{colormatrix=...} (color spaces conversion, faster).
+       
+       These are only metadata that do not affect rendering but when the file is read by a player later they are used to reproduce the colors without errors.
+\end{enumerate}
+
+For more tips on how \CGG{} processes colors on the timeline see  \nameref{sec:color_space_range_playback} and \nameref{sec:conform_the_project}.
+
 %%% Local Variables:
 %%% mode: latex
 %%% TeX-master: "../CinelerraGG_Manual"