Andrea added information about remuxing and handy script

diff --git a/parts/Advanced.tex b/parts/Advanced.tex
index b056b2cf8197b29db2dd4ecbd878530dc4c5f874..7ea9e216ab7b4544a8326f0ec5384e38d7e08043 100644 (file)
--- a/parts/Advanced.tex
+++ b/parts/Advanced.tex
@@ -249,6 +249,11 @@ The BIGGEST gain from using this is if you have media that is not \textit{seekab
 
 Another important function of Transcode is being able to convert the project's media into a high-quality \textit{mezzanine} codec \index{mezzanine codec} (sometimes also called \textit{intermediate} codec \index{digital intermediate}), which makes timeline work lighter and more efficient. In fact such codecs (ffv1, ProRes, DNxHD, OpenEXR, huffyuv, etc) are generally little or not at all compressed; the type of compression is intraframe --more suitable for editing, and the image quality (4:2:2 up; 10-bit color up; floating point; etc) is suitable for \textit{Color Correction}, \textit{Chroma Key} and \textit{Rotoscoping}. The use of mezzanine codecs leads to very large files, so you need to make sure you have enough storage space.
 
 
 Another important function of Transcode is being able to convert the project's media into a high-quality \textit{mezzanine} codec \index{mezzanine codec} (sometimes also called \textit{intermediate} codec \index{digital intermediate}), which makes timeline work lighter and more efficient. In fact such codecs (ffv1, ProRes, DNxHD, OpenEXR, huffyuv, etc) are generally little or not at all compressed; the type of compression is intraframe --more suitable for editing, and the image quality (4:2:2 up; 10-bit color up; floating point; etc) is suitable for \textit{Color Correction}, \textit{Chroma Key} and \textit{Rotoscoping}. The use of mezzanine codecs leads to very large files, so you need to make sure you have enough storage space.
 

+\paragraph{NOTE:} \CGG{} cannot do \textit{remuxing} without transcoding. For remuxing only, use \textit{ffmpeg} as shown in the following script. First move to the folder containing the files to be remuxed; the script takes all video files of a certain extension (in the following example \texttt{avi}) from the folder and its subfolders and makes a remux in a new container (in this example \texttt{mkv}) inside the new folder \texttt{remux}. The internal codec will remain the original one.  Here is an example script:
+
+\begin{lstlisting}[numbers=none]
+       for f in $(find . -name '*.avi'); do ffmpeg -i "$f" -c:v copy -c:a copy "remux/{f%.*}.mkv "; done
+\end{lstlisting}

 
 \section{OpenEDL}%
 \label{sec:openedl}
 
 \section{OpenEDL}%
 \label{sec:openedl}

diff --git a/parts/Rendering.tex b/parts/Rendering.tex
index ab6dc45d871c3c8115ffc242d8f17cbf26a15f42..8438ecd153768f96a4188a958673a33d30071bde 100644 (file)
--- a/parts/Rendering.tex
+++ b/parts/Rendering.tex
@@ -13,7 +13,8 @@ in/out points are set, the affected region is rendered.  When no
 region is highlighted, everything after the insertion point is
 rendered.  By positioning the insertion point at the beginning of a
 track and unsetting all in/out points, the entire track is rendered.
 region is highlighted, everything after the insertion point is
 rendered.  By positioning the insertion point at the beginning of a
 track and unsetting all in/out points, the entire track is rendered.

-But you also have the choice to render \textit{one frame}.
+But you also have the choice to render \textit{one frame}. Reminder,
+\CGG{} does not do remuxing without rendering - see \nameref{sec:transcode}.

 
 \section{Single File Rendering}%
 \label{sec:single_file_rendering}
 
 \section{Single File Rendering}%
 \label{sec:single_file_rendering}