Andrea minor changes to keep relevant

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

diff --git a/parts/Rendering.tex b/parts/Rendering.tex
index cbdcaf9095e2652b9dc33cf3ed472602559dd615..23ff4514904238b8e9ebdceaa3bfb31e33d8089d 100644 (file)
--- a/parts/Rendering.tex
+++ b/parts/Rendering.tex
@@ -174,7 +174,9 @@ all parameter configurations.
        list.  The list is provided by ffmpeg as input selection, but is
        more like suggestions than fact.  For example, the raw formats can
        take almost any format, but the rawvideo codec actually specifies no
-       legal formats.
+       legal formats.  Note that if you want a very specific Bitrate you must
+       make sure there is not conflicting parameter values set such as Quality
+       or CRF.
 \end{itemize}
 
 \noindent Some option files provide \textit{cin\_pix\_fmt} to
@@ -185,7 +187,7 @@ errors when the other provided parameters conflict with the
 parameter dictates pixel format must be \texttt{yuv420p}.
 
 \paragraph{cin\_bitrate} If you specify the bitrate, you can not
-specify the quality.\\ Example: \textit{cin\_bitrate=2000000}
+specify the quality or CRF.\\ Example: \textit{cin\_bitrate=2000000}
 
 \paragraph{cin\_quality} If you specify the quality, you can not
 specify the bitrate.\\ Example: \textit{cin\_quality=7}
@@ -681,7 +683,7 @@ Video Preset textbox.
 
 \CGG{} supports image sequences with both decoding and encoding.
 
-\CGG{} by default uses ffmpeg as encoding/decoding engine but we can disable it to have the specific internal engine available. See \nameref{sec:ffmpeg_early_probe_explanation} on how to switch between engines. With the internal engine we can create and load sequences of OpenEXR; PNG; TIFF; TGA; GIF; PPM and JPEG. With ffmpeg we can create and load DPX sequences or create a custom preset for any kind of image. Using these formats results in great timeline efficiency and high video quality at the cost of taking up a lot of space because they are uncompressed (or with lossless compression).
+\CGG{} by default uses ffmpeg as encoding/decoding engine but we can disable it to have the specific internal engine available. See \nameref{sec:ffmpeg_early_probe_explanation} on how to switch between engines. With the internal engine we can create and load sequences of OpenEXR; PNG; TIFF; TGA; GIF; PPM and JPEG. There is also support for DPX sequences, but only in read and without rendering presets. With ffmpeg we can create and load DPX sequences or create a custom preset for any kind of image. Using these formats results in great timeline efficiency and high video quality at the cost of taking up a lot of space because they are uncompressed (or with lossless compression).
 By rendering, you will get as many still images as there are frames in the project, plus a \textit{file-list} (or \textit{TOC}) that indexes the images. A good practice is to create a folder to contain the images (for example \texttt{/tmp/img\_seq/}) and then open the rendering window in \CGG{} and set a serial and increasing number as the name (for example: \texttt{/tmp/img\_seq/image \%05d.png}). \textit{image} is a generic name chosen at will; $\%$ creates a progressive sequence of distinct images; $05d$ indicates how many digits the image number will be, in this case 5 digits to go from $00000$ to $99999$.
 Once we have our folder of images, if we want to import it in a project just load the file-list, which includes the link to all the files of the sequence.
 To learn more about using and creating a preset with ffmpeg of an image sequence, see \nameref{sec:ffmpeg_image2_streams} and/or \nameref{sec:image_sequence_creation}.