\begin{center}
\begin{tabular}{l l l l}
PNGLIST = *.png & PPMLIST = *.ppm & TGALIST = *.tga & TIFFLIST = *.tiff \\
- EXALIST = *.exa & CR2LIST = *.cr2 & JPEGLIST = *.jpg & GIFLIST = *.gif
+ EXRLIST = *.exr & CR2LIST = *.cr2 & JPEGLIST = *.jpg & GIFLIST = *.gif
\end{tabular}
\end{center}
%\vspace*{1ex}
-Using the example of jpeg’s, the jpeg list sequence file type is the easiest and fastest way to access a sequence of jpg images as a single asset. First build a jpeglist sequence file and name it something like jpeglist.sh. There is an example script of how to do this in the Auxiliary Programs section of the Appendix (\ref{sec:image_sequence_creation}). Once the jpeglist.sh file is built you can then run it similar to this line:
+Using the example of jpeg’s, the jpeg list sequence file type is the easiest and fastest way to access a sequence of jpg images as a single asset. First build a jpeglist sequence file and name it something like jpeglist.sh. There is an example script of how to do this in the Auxiliary Programs section of the Appendix (\ref{sec:image_sequence_creation}). Once the jpeglist.sh file is built and made executable you can then run it similar to this line:
\begin{lstlisting}[style=sh]
-jpeglist.sh /<path>/file.jpg /<path>/DSC*.jpg
+./jpeglist.sh /<path>/outputfile.jpgs /<path>/inputfilesDSC*.jpg
\end{lstlisting}
-\vspace*{1ex} \noindent If <\texttt{path}> is the same on both outfile and infiles, then file.jpg is created in the same directory as infiles, the directory contains the entire asset, and the file list uses relative paths; otherwise the file list contains absolute paths. Since this creates outfile list as a single asset, the memory demand and access time is much lower. When you load the outfile in \CGG{}, you will need to set \textit{Try ffmpeg last} since ffmpeg does not work with jpeglist sequence files.
+\vspace*{1ex} \noindent If <\texttt{path}> is the same on both outputfile and inputfiles, then file.jpgs is created in the same directory as infiles, the directory contains the entire asset, and the file list uses relative paths; otherwise the file list contains absolute paths. Since this creates outputfile list as a single asset, the memory demand and access time is much lower. When you load the outputfile in \CGG{}, you might need to set \textit{Try ffmpeg last} if ffmpeg does not work with that particular type of sequence files.
-An example output file from running this script residing in the directory where \texttt{DSC*.jpg} files exist is shown below.
+An example output file from running this script residing in the directory where \texttt{DSC*.jpg} files exist is shown below. To use this, turn off ffmpeg probes first, and open \texttt{outputfile.jpgs} using File $\rightarrow$ Load files. Of course, you can edit this file to change frame rate or names of files to include.
+The width and height are expected to be of the same or similar size.
-To use this, turn off ffmpeg probes first, and open \texttt{timelapse.jpg} using File $\rightarrow$ Load files.
-
-\begin{lstlisting}[style=sh,caption={Example: timelapse.jpg},captionpos=t]
+\begin{lstlisting}[style=sh,caption={Example: outputfile.jpgs},captionpos=t]
JPEGLIST
# First line is always JPEGLIST
# Frame rate:
\noindent Keep in mind that to maintain the integrity of your project xml file for easy moving to another computer, do not delete the symbolic links. You will want to use \texttt{cp\,-a} to maintain the links for moving to a USB key or another computer.
+\subsection{Export to EDL}%
+\label{sub:export_to_edl}
+
+CMX3600 is an outdated and limited format for EDL. For example it only goes up to 999 edits per project, supports only 4 audio tracks per video track and supports only Cuts, Fades and Keys. But it has the advantage of being a standard format supported by many NLEs. \CGG{} uses a rich XML format that is not compatible with other NLEs. You can use the \textit{Export to EDL} option to try to produce EDL files of type CMX3600 in \textit{strict mode} and thus be able to bring them into other NLEs. Given the limitation of this format, however, it is difficult to get a working EDL file that exactly reproduces the original xml. This feature also produces files that each contain a video track or an audio track and does not embed video with audio or audio with audio. Manual intervention with a plain text editor on the produced EDL files may be necessary. For example, if the program in which you want to open the EDL reports the message of not being able to find the source files, then we can manually add the path to each line that reports the source file.
+
\subsection{Backup and Perpetual Session}%
\label{sub:backup_perpetual_session}
\index{backup}
projects / goodguy / cin-manual-latex.git / blobdiff