Frames per seconds is usually $29.97$ for NTSC and $25$ fps for PAL. The standard SD dvd generally uses the MPEG-2 program stream with a filename extension of \texttt{m2v}. BD blu-ray media is not normally interlaced, but you can leave it interlaced. Blu-ray uses the MPEG transport stream which contains 1 or more program streams with a default filename extension of \texttt{m2ts}.
Requirements for creating DVDs is the hardware device to write the media on and, obviously, the blank media for either BD or SD. When generating SD media, you will have to install \textit{dvdauthor} and for BD media, install \textit{udftools} if they are not on your system. Also, keep in mind that to mount filesystems for creating files and to burn DVDs, you will have to be root since you have to have privileges, unless special permissions have been provided for a non-root user. It is also highly recommended to
-run the cinelerra startup from a terminal window, instead of the icon, in order to see informative messages of how to actually write the output (at prompt: keyin \texttt{<install\_directory\_path/bin/cin}).
+run the Cinelerra startup from a terminal window, instead of the icon, in order to see informative messages of how to actually write the output (at prompt: keyin \texttt{<install\_directory\_path/bin/cin}).
A warning here -- writing blu-ray BDs and regular SDs can take a large amount of clock time. Keep in mind that a blu-ray can contain 25 hours of viewing, so would take multiple hours to just write one.
Any problems encountered will require that you read more information in this section to include specific details, helpful hints, and problem resolution.
-\paragraph{Details and specific explanations} to create blu-ray or regular DVD are provided here. It is very advantageous to startup cinelerra from the command line prompt instead of the icon. Also, please be root or your hard work will be lost when the automount is issued and fails for bluray udfs mounting.
+\paragraph{Details and specific explanations} to create blu-ray or regular DVD are provided here. It is very advantageous to startup Cinelerra from the command line prompt instead of the icon. Also, please be root or your hard work will be lost when the automount is issued and fails for bluray udfs mounting.
The general design of the DVD/blu-ray generation operations is to first render media using batch rendering and then terminate Cinelerra to start a script which creates the target device filesystem data. These scripts are the \texttt{dvd.sh} and \texttt{bd.sh} scripts written into the target directory. For DVD, the general plan is to write a directory \texttt{<target>/iso} with the dvd filesystem via \textit{dvdauthor} and then generate an iso9660 filesystem and write it to a dvd via \textit{growisofs}.
\label{fig:dvd-batch03}
\end{figure}
-Figure~\ref{fig:dvd-batch04} shows the availability of 10-bit high quality 4:2 :2 for a Batch Render seen by clicking on wrench icon. You need specially compiled cinelerra in order to use the x265 10-bit as opposed to 8-bit.
+Figure~\ref{fig:dvd-batch04} shows the availability of 10-bit high quality 4:2 :2 for a Batch Render seen by clicking on wrench icon. You need specially compiled Cinelerra in order to use the x265 10-bit as opposed to 8-bit.
\begin{figure}[htpb]
\centering
\section{Output Terminal Messages from Creating DVDs}%
\label{sec:output_terminal_messages_dvd}
-Below are examples of what the batch jobs generate and you will see on the terminal screen if you started the cinelerra program in the recommended manner from a terminal window. It is just informational but will let you know if errors. In looking at any of the output, you can safely ignore the errors that read \texttt{Unsupported codec with id 100357 for input stream 0} -- this comes from \textit{nav-data} (navigation data). The first 2 examples are seen from running the batch jobs; the last 2 are from the single line execution which records the media output to the DVD hardware.
+Below are examples of what the batch jobs generate and you will see on the terminal screen if you started the Cinelerra program in the recommended manner from a terminal window. It is just informational but will let you know if errors. In looking at any of the output, you can safely ignore the errors that read \texttt{Unsupported codec with id 100357 for input stream 0} -- this comes from \textit{nav-data} (navigation data). The first 2 examples are seen from running the batch jobs; the last 2 are from the single line execution which records the media output to the DVD hardware.
\subsubsection*{SD Example: Partial Output during Cinelerra run}
\label{ssub:sd_example_partial_output}
\begin{itemize}
\item Are you logged in as root? This is required in order to loopback mount files for bluray and to write media on \texttt{/dev/hardware}. See section \hyperref[sec:bluray_workaround_mount_umount]{13.7} for a workaround for normal user mode.
- \item Did you startup cinelerra from a terminal window so you can see informative messages?
+ \item Did you startup Cinelerra from a terminal window so you can see informative messages?
\item Is udftools installed for BD and dvdauthor installed for SD?
\item Do you have loopback not enabled for bluray? At least temporarily, disable automount via:
\begin{lstlisting}[language=bash,numbers=none]
An MTS file is a video file saved in the high-definition (HD) MPEG Transport Stream video format, commonly called \textit{AVCHD}. It contains HD video compatible with Blu-ray disc format and is based on the MPEG-2 transport stream. MTS files are often used by Sony, Panasonic, Canon and other HD camcorders. Legal input for Video --- MPEG1VIDEO, MPEG2VIDEO, H264; Audio --- MP1, MP2, AC3, AC3PLUS, DTS, TRUHD.
-For creating a blu-ray disc, if you have HDV MPEG-2 media that is in blu-ray format, you can save the original quality of your work, rather than rendering it to another format. Follow the steps below directly instead of going through cinelerra. It has been tested on 10 different MTS files.
+For creating a blu-ray disc, if you have HDV MPEG-2 media that is in blu-ray format, you can save the original quality of your work, rather than rendering it to another format. Follow the steps below directly instead of going through Cinelerra. It has been tested on 10 different MTS files.
\begin{lstlisting}[language=bash,numbers=none]
du -sb /yourHDVfile.MTS # Determine the size of your file in bytes.
blocks=((size-in-bytes/2048 + 4096)) # Convert bytes into blocks + a little more.
mkudffs /tmp/newfilename.udfs blocks # Create a file with that \# of blocks + some extra.
mount -o loop /tmp/newfilename.udfs /mntX # Use a mount point like mntX that is not in use.
-/<cinelerra_installed_path>/bin/bdwrite /mntX /tmp/yourHDVfile.MTS # Substitute cinelerra path.
+/<cinelerra_installed_path>/bin/bdwrite /mntX /tmp/yourHDVfile.MTS # Substitute Cinelerra path.
umount /mntX # You must unmount the udfs filesystem
growisofs -Z /dev/bd=/tmp/newfilename.udfs # Replace /dev/bd with your bluray hardware device.
OR dd if=/tmp/newfilename.udfs of=/dev/bd bs=2048000 # if using rewritable blu-ray; replace bd.
\section{Blu-ray Workaround for Mount/Umount}%
\label{sec:bluray_workaround_mount_umount}
-Creating BD images to be written to media requires usage of \textit{mount} and \textit{umount} which typically can only be done by the root user due to security. If you want to avoid running cinelerra as root, you can implement a workaround by adding a line in \texttt{/etc/fstab} (must be root to edit the file initially) and by creating a directory in your home area, called \texttt{bluray}. You only have to do this once unless you upgrade the Operating System and it wipes out the line in \texttt{/etc/fsta}b. Now the cinelerra program will automatically do the mount and umount for you each time you execute BD Render and you can run as an ordinary user.
+Creating BD images to be written to media requires usage of \textit{mount} and \textit{umount} which typically can only be done by the root user due to security. If you want to avoid running Cinelerra as root, you can implement a workaround by adding a line in \texttt{/etc/fstab} (must be root to edit the file initially) and by creating a directory in your home area, called \texttt{bluray}. You only have to do this once unless you upgrade the Operating System and it wipes out the line in \texttt{/etc/fsta}b. Now the Cinelerra program will automatically do the mount and umount for you each time you execute BD Render and you can run as an ordinary user.
The line to add to \texttt{/etc/fstab} will look something like the following, assuming your username is \textit{name} and your groupid may be \textit{users} or \textit{name}. If you do an \texttt{ls -l} in your home directory, the $3^{rd}$ and $4^{th}$ fields shown will be your uid or name and gid or groupid which you must substitute in the line below.
/home/name/image /home/name/bluray udf noauto,loop,rw,user,uid=name,gid=groupid 0 0
\end{lstlisting}
-Also, be sure to do a \texttt{mkdir bluray} in your \texttt{/home/name} directory as this is a requirement (owned by you; uid=gid=name). When the actual image to be written to disc media is created, it will first d any current \texttt{/home/name/image} file. Warning – make sure you do not already have a file called \textit{image} that you want to save as it will be automatically deleted every time you initiate a BD Render. So you will want to burn a bluray disc after cinelerra creates the \textit{image} since it will written over on the next rendition. The actual writing to your bluray burner (something like \texttt{/dev/sr0}) is done outside of cinelerra at a terminal prompt and requires root privilege usually. You can either use \textit{sudo} for 1 line or create user wheel group to get around this.
+Also, be sure to do a \texttt{mkdir bluray} in your \texttt{/home/name} directory as this is a requirement (owned by you; uid=gid=name). When the actual image to be written to disc media is created, it will first d any current \texttt{/home/name/image} file. Warning – make sure you do not already have a file called \textit{image} that you want to save as it will be automatically deleted every time you initiate a BD Render. So you will want to burn a bluray disc after Cinelerra creates the \textit{image} since it will written over on the next rendition. The actual writing to your bluray burner (something like \texttt{/dev/sr0}) is done outside of Cinelerra at a terminal prompt and requires root privilege usually. You can either use \textit{sudo} for 1 line or create user wheel group to get around this.
\section{Blu-ray from Multiple Cinelerra Output}%
\label{sec:bluray_multiple_cinelerra_output}
-Writing prepared multiple cinelerra output files, \texttt{bd.m2ts}, to a single bluray disc is relatively easy to do but is not done automatically. You can render all of the desired files via the Create BD menu, save each individual \texttt{bd.m2ts} file with a unique name, construct a Menu Title that reflects the contents of each of these files, then manually use a few commands to create a udfs file to be written to BD.
+Writing prepared multiple Cinelerra output files, \texttt{bd.m2ts}, to a single bluray disc is relatively easy to do but is not done automatically. You can render all of the desired files via the Create BD menu, save each individual \texttt{bd.m2ts} file with a unique name, construct a Menu Title that reflects the contents of each of these files, then manually use a few commands to create a udfs file to be written to BD.
Usage of the final preparation taken from the bdwrite program comments:
\begin{enumerate}
\item Create all of the \texttt{bd.m2ts} files that you want to put on the Bluray.
- \item Using cinelerra, design your Title page using a few seconds of video and the \textit{Title} plugin.
+ \item Using Cinelerra, design your Title page using a few seconds of video and the \textit{Title} plugin.
\item Use BD Create to render your short Title video.
\item Next is the most complicated part which is to run \texttt{mkudffs} with a sufficient amount of disk space to hold all of the \texttt{bd.m2ts} files \textit{plus a little more!} To calculate this, you can record the sizes from having run BD Create mkudffs. This number is displayed on the terminal screen when using the command line interface each time and add them together. Or recalculate the size of each bd.m2ts using the formula below and adding them all together. This is the number of blocks used to make a bluray image space for bdwrite to use. For many files, this could require a huge amount of space, so check first.
\begin{lstlisting}[language=bash,numbers=none]
\end{lstlisting}
Now create the image file via: \texttt{mkudffs image <Total size>} where image or udfs is the image name.
\item Loop mount the disk image (refer to Section \hyperref[sec:bluray_workaround_mount_umount]{13.7}).
- \item Then actually write your multiple bd.m2ts type files onto the \textit{image} where \texttt{<cin\_path>} is the location of the
cinelerra binary \textit{bdwrite} file and \texttt{<path>} is your directory path. Below is a single line that wrapped around with 4 Titles.
+ \item Then actually write your multiple bd.m2ts type files onto the \textit{image} where \texttt{<cin\_path>} is the location of the
Cinelerra binary \textit{bdwrite} file and \texttt{<path>} is your directory path. Below is a single line that wrapped around with 4 Titles.
\begin{lstlisting}[language=bash,numbers=none]
<cin_path>/bin/bdwrite image /<path>menu_titles.m2ts --- /<path>/bd1.m2ts -- /<path>/bd2.m2ts -- /<path>/bd3.m2ts -- /<path>bd4.m2ts
\end{lstlisting}
\fontsize{10pt}{12pt}\selectfont
\begin{verbatim}
-`configure' configures cinelerra 5.1 to adapt to many kinds of systems.
+`configure' configures Cinelerra to adapt to many kinds of systems.
Usage: ./configure [OPTION]... [VAR=VALUE]...
Since in a make file, the \$ is a special character, it must be escaped so in order to represent a \$ as part of an input parameter, it has to be stuttered.
That is, you will need \$\$ (2 dollar signs) to represent a single dollar sign.
-It may be necessary on some distros which have missing or incomplete up-to-date libraries, to build cinelerra without Ladspa.
+It may be necessary on some distros which have missing or incomplete up-to-date libraries, to build Cinelerra without Ladspa.
To do so, use:
\begin{lstlisting}[language=bash,numbers=none]
apt install software-properties-common apt-transport-https
apt-add-repository https://cinelerra-gg.org/download/pkgs/ub14
# UBUNTU 16/17/18 note - This has been known to work, but things change quickly:
-# VIP - for the first install, the above line adds cinelerra to /etc/apt/sources.list but...
+# VIP - for the first install, the above line adds Cinelerra to /etc/apt/sources.list but...
# Version 16/17/18 of Ubuntu are more strict for licensing so you will have to edit
# the file /etc/apt/sources.list to add [trusted=yes] after deb and before https...cin...
# For example the line should be: deb [trusted=yes] https://cinelerra-gg.org/download/pkgs/ub16 xenial main
# Or for ub17: deb [trusted=yes] https://cinelerra-gg.org/download/pkgs/ub17 zesty main
# Or for ub18: deb [trusted=yes] https://cinelerra-gg.org/download/pkgs/ub18 bionic main
-# Also, on the install you will get an error message that you can either ignore as cinelerra
+# Also, on the install you will get an error message that you can either ignore as Cinelerra
# will run anyway, or else (the first time only) on the commnand line keyin:
# echo > /etc/sysctl.d/50-cin.conf "kernel.shmmax=0x7fffffff"
apt update
\item[Chapter \ref{cha:capturing_recording_media}] \nameref{cha:capturing_recording_media}.
If this is what you want to do, then read this chapter.
- A section on using cinelerra with broadcast TV is especially useful if that is something you want to do.
+ A section on using Cinelerra with broadcast TV is especially useful if that is something you want to do.
\item[Chapter \ref{cha:dvd_bluray_creation}] \nameref{cha:dvd_bluray_creation}.
\label{sub:recover_mixer_windows}
\begin{wrapfigure}[18]{O}{1em + 0.3\textwidth}
- \vspace{-8ex}
+ \vspace{-6ex}
\centering
\includegraphics[width=0.3\textwidth]{images/mixer-patchbay01.png}
\caption{Mixer patchbay}
Cinelerra-GG supports 2 separate preferences for the playback configuration. Cinelerra can be operated in a single or dual screen configuration, both by using Xinerama or dual screen configuration of X windows. It will take some setup using Xconfig to make this work.
-The \texttt{Settings $\rightarrow$ Preferences} menu has \textit{Playback A and Playback B} tabs. The target display and audio device configuration can be separate, to support up to 2 display and/or audio device stations. The active configuration displays an asterisk (*) in its selection tab and the selected tab will be made active when \texttt{OK} is pressed. For example: you may have a dual screen monitor system with the left screen showing the cinelerra main window and the right screen showing the composer. Another setup might use a monitor for the left screen and an HDTV as the right screen displaying the composer. When a playback configuration is selected, the audio/video device configuration is switched to the playback selection. The active playback setup can be changed through use of the menu pulldown of \texttt{Settings $\rightarrow$ Preferences} or via the remote control menu selection (see the section Remote Control for DVB for more detail).
+The \texttt{Settings $\rightarrow$ Preferences} menu has \textit{Playback A and Playback B} tabs. The target display and audio device configuration can be separate, to support up to 2 display and/or audio device stations. The active configuration displays an asterisk (*) in its selection tab and the selected tab will be made active when \texttt{OK} is pressed. For example: you may have a dual screen monitor system with the left screen showing the Cinelerra main window and the right screen showing the composer. Another setup might use a monitor for the left screen and an HDTV as the right screen displaying the composer. When a playback configuration is selected, the audio/video device configuration is switched to the playback selection. The active playback setup can be changed through use of the menu pulldown of \texttt{Settings $\rightarrow$ Preferences} or via the remote control menu selection (see the section Remote Control for DVB for more detail).
-\subsubsection*{Yes, you can watch TV on cinelerra instead of cinelerra on TV.}%
+\subsubsection*{Yes, you can watch TV on Cinelerra instead of Cinelerra on TV.}%
\label{ssub:watch_tv_on_cinelerra}
Figure~\ref{fig:multi-screen01} shows partial window of \textit{*Playback A} selected and the second tab for \textit{Playback B}. Note that on the bottom right of the window, \texttt{Default B Display:} is set to $:0.1$, representing the setting for Screen 1. On the unseen \textit{Playback A} window, the \texttt{Default A Display:} will be set to $:0.0$ meaning for Screen 0. Otherwise, the default would be nothing there or just <empty>.
\item[Burn:] Darkens the destination color to reflect the source color. Burning with white produces no change. In photography, burning is a technique used in a darkroom to increase the exposure in particular areas of the image. This brings out details in the highlights. Math formula is the same as used by SVG and Gimp.
\item[Dodge:] Brightens the destination color to reflect the source color. Dodging with black produces no change. The result color is a lightening of the source color to reflect the underlying layer color by decreasing the contrast. If the source color is pure black, the result color is the underlying color. In photography, dodging is a technique used in a darkroom to decrease the exposure in particular areas of the image. This brings out details in the shadows. Math formula is the same as used by SVG and Gimp.
\item[Difference:] Subtracts the darker of the two constituent colors from the lighter. This is the same as \textit{Subtract} except that the absolute value is used. \textit{Subtract} colors which would be black due to clipping become visible instead. Differencing with white inverts the destination color. Differencing with black produces no change. Math formula is the same as used by SVG and Gimp.
- \item[Hardlight:] Multiplies or screens the colors, dependent on the source color value. If the source color is lighter than $0.5$, the destination is lightened as if it were screened. If the source color is darker than $0.5$, the destination is darkened, as if it were multiplied. The degree of lightening or darkening is proportional to the difference between the source color and $0.5$. If it is equal to $£0.5$ the destination is unchanged. Using pure black or white produces black or white. The effect is similar to shining a harsh spotlight on the destination. This mode is useful for creating the appearance of shadows on a layer. You might use this mode to combine two photographs and obtain bright colors and sharp edges. Math formula is the same as used by SVG and Gimp.
+ \item[Hardlight:] Multiplies or screens the colors, dependent on the source color value. If the source color is lighter than $0.5$, the destination is lightened as if it were screened. If the source color is darker than $0.5$, the destination is darkened, as if it were multiplied. The degree of lightening or darkening is proportional to the difference between the source color and $0.5$. If it is equal to $0.5$ the destination is unchanged. Using pure black or white produces black or white. The effect is similar to shining a harsh spotlight on the destination. This mode is useful for creating the appearance of shadows on a layer. You might use this mode to combine two photographs and obtain bright colors and sharp edges. Math formula is the same as used by SVG and Gimp.
\item[Softlight:] Darkens or lightens the colors, dependent on the source color value. If the source color is lighter than 0.5, the destination is lightened. If the source color is darker than $0.5$, the destination is darkened, as if it were burned in. The degree of darkening or lightening is proportional to the difference between the source color and $0.5$. If it is equal to $0.5$, the destination is unchanged. Using pure black or white produces a distinctly darker or lighter area, but does not result in pure black or white. The effect is similar to shining a diffused spotlight on the destination. A layer with pure black or white becomes markedly darker or lighter, but does not become pure black or white. Soft light is not related to “Hard light” in anything but the name, but it does tend to make the edges softer and the colors not so bright. Math formula is the same as used by Gimp; SVG formula differs.
\end{description}
Below describes the necessary steps for recording freely available media from the internet for your own personal use. You have to be on a system using pulseaudio, such as ubuntu, fedora, centos.
\begin{enumerate}
- \item Start cinelerra and select \texttt{Settings $\rightarrow$ Preferences $\rightarrow$ Recording} From a terminal (with a wide text window) run: \texttt{pactl list}. You will see all of the audio sources and sinks on your system. Identify the source associated with the normal output your system uses. Example: \texttt{Source $\#1$}. Locate the source which monitors your normal audio output. For example: \texttt{front stereo}.
+ \item Start Cinelerra and select \texttt{Settings $\rightarrow$ Preferences $\rightarrow$ Recording} From a terminal (with a wide text window) run: \texttt{pactl list}. You will see all of the audio sources and sinks on your system. Identify the source associated with the normal output your system uses. Example: \texttt{Source $\#1$}. Locate the source which monitors your normal audio output. For example: \texttt{front stereo}.
\item Choose a \textit{File Format} and \textit{File Type} (for example: \texttt{FFMPEG \& qt}).
\begin{itemize}
\item Check \texttt{Record audio tracks}.
Listed below are the steps for the initial DVB setup. Setup will be preserved until you make changes.
\begin{enumerate}
- \item Start cinelerra, and click \texttt{Settings $\rightarrow$ Preferences $\rightarrow$ Recording}
+ \item Start Cinelerra, and click \texttt{Settings $\rightarrow$ Preferences $\rightarrow$ Recording}
\item Select \textit{File Format} checkbox: \texttt{Realtime TOC} (Table of Contents)
\begin{itemize}
\item It is not necessary to set File Format at this point as it will automatically be set later.
\subsection{Dual Screen Mode}%
\label{sub:dual_screen_mode}
-Dual screen mode is useful for displaying cinelerra video/project on a large screen digital Television set or for watching a previously recorded broadcast TV program via Cinelerra. The physical configuration results in one screen (an \textit{Xwindow}) on one monitor and the other screen on the other monitor or TV screen. Before the mode is usable for Cinelerra, X has to be configured in \textit{dual screen mode} --- that is, you must first split the configuration into 2 displays to operate Dual Screen Mode. On some systems, you may be able to get to the dual screen mode by using \textit{Xinerama} allowing for use of 2 physical displays to act as 1 virtual display.
+Dual screen mode is useful for displaying Cinelerra video/project on a large screen digital Television set or for watching a previously recorded broadcast TV program via Cinelerra. The physical configuration results in one screen (an \textit{Xwindow}) on one monitor and the other screen on the other monitor or TV screen. Before the mode is usable for Cinelerra, X has to be configured in \textit{dual screen mode} --- that is, you must first split the configuration into 2 displays to operate Dual Screen Mode. On some systems, you may be able to get to the dual screen mode by using \textit{Xinerama} allowing for use of 2 physical displays to act as 1 virtual display.
The main menu pulldown, \texttt{Settings $\rightarrow$ Preferences $\rightarrow$ Playback A} and \texttt{B} Tabs, must be properly configured in order to take advantage of the Dual Screen Mode capability.
Since Dual Screen Mode is most widely used for either a demonstration or watching TV, you will want to take advantage of Remote Control mode as described in a following section. In the camera shots below, note the square red box that shows up in the upper left hand corner of the Viewer window (arrow pointing to it but it looks more orange than red) which denotes that the Application/Menu key was used to get into Remote Control mode.
-Figure~\ref{fig:two-monitors01} shows 2 monitors (could just as well be a big-screen TV for the second monitor) with Tile left where all of the cinelerra windows are on the left most monitor. The big red arrow points to the little red square box indicating that Remote Control mode is in effect.
+Figure~\ref{fig:two-monitors01} shows 2 monitors (could just as well be a big-screen TV for the second monitor) with Tile left where all of the Cinelerra windows are on the left most monitor. The big red arrow points to the little red square box indicating that Remote Control mode is in effect.
\begin{figure}[htpb]
\centering
\label{fig:two-monitors01}
\end{figure}
-Figure~\ref{fig:two-monitors02} shows 2 monitors with Tile right (b key) where all of the cinelerra windows are on the right monitor. The left monitor shows the Suse distro logo and a couple of xterm type windows.
+Figure~\ref{fig:two-monitors02} shows 2 monitors with Tile right (b key) where all of the Cinelerra windows are on the right monitor. The left monitor shows the Suse distro logo and a couple of xterm type windows.
\begin{figure}[htpb]
\centering
\label{fig:two-monitors03}
\end{figure}
-Figure~\ref{fig:two-monitors04} shows 2 monitors with Compositor window on the 2nd monitor in FULLSCREEN mode so that no cinelerra borders are visible to distract from the picture. The big red arrow points to the little red square box indicating that Remote Control mode is in effect.
+Figure~\ref{fig:two-monitors04} shows 2 monitors with Compositor window on the 2nd monitor in FULLSCREEN mode so that no Cinelerra borders are visible to distract from the picture. The big red arrow points to the little red square box indicating that Remote Control mode is in effect.
\begin{figure}[htpb]
\centering
\end{wrapfigure}
Cinelerra DVB recording/playback can now easily be done in “couch potato” mode using a remote control. This comes in handy when you want to playback on a big TV screen for multiple person viewing. You can use the Application/Menu key on the keyboard to toggle between standard Cinelerra usage or a Dispatcher methodology through use of a remote control, an Android programmed device such as a tablet, or keyboard. The Application/Menu key on most keyboards is between the Alt and Ctrl keys on the right hand side bottom and depicts a menu on it either with or without a pointer (see image below). An ati-x10 Remote Control device (figure~\ref{fig:remote01}) is currently working with Cinelerra and other remote controls may work but have never been tried. The red/orange box on the top left main screen of Cinelerra indicates Dispatcher Method access is activated which allows for keyboard grab which routes all key strokes until toggled off. Below are the currently defined operations.
+\newline
Remote Control Keys (Application/Menu key toggle for ati-x10 remote)
-\begin{tabular}{lc p{10cm}}
+% Should find something so that the last column width automatically adapts to margin/font/pagesize.
+\begin{tabular}{lc p{12cm}}
up arrow&=&forward 1 minute\\
down arrow&=&forward single frame\\
book key&=&toggles channel scan (always available)\\
- hand key&=&terminates cinelerra (always available)\\
+ hand key&=&terminates Cinelerra (always available)\\
\end{tabular}
\noindent Plus usual Transport keys:
\subsection{Android Remote Control for DVB}%
\label{sub:android_remote_control_dvb}
-Cinelerra GG Infinity has android remote interface code (figure~\ref{fig:remote02}). Any device, such as a tablet or a phone, can be used as long as it is running the Android operating system. Programming an Android Remote Control for DVB is a bit complicated at first, but becomes pretty simple after a bit.
+Cinelerra GG Infinity has Android remote interface code (figure~\ref{fig:remote02}). Any device, such as a tablet or a phone, can be used as long as it is running the Android operating system. Programming an Android Remote Control for DVB is a bit complicated at first, but becomes pretty simple after a bit.
\begin{enumerate}
- \item The Android Remote Control requires you to download and install the android \textit{CineRmt} app package (apk). To install it simply download it (any way you can) to your phone or tablet and click it to install, if it doesn't run automatically.
- \item You should be able to open Settings You should be able to open Settings→Preferences→Interface tab. And see Android Remote Control in the Operation section. Enable it using the checkbox. The default port 23432 and default PIN cinelerra are OK. \texttt{Preferences $\rightarrow$ Interface} tab. And see Android Remote Control in the Operation section. Enable it using the checkbox. The default port $23432$ and default PIN cinelerra are OK.
+ \item The Android Remote Control requires you to download and install the Android \textit{CineRmt} app package (apk). To install it simply download it (any way you can) to your phone or tablet and click it to install, if it doesn't run automatically.
+ \item In Cinelerra, open \texttt{Settings $\rightarrow$ Preferences $\rightarrow$ Interface} tab, and enable \texttt{Android Remote Control} in the Operation section using the checkbox. The default port $23432$ and default PIN value \texttt{cinelerra} are OK.
\item After you install the new phone/tablet app in step 1, start it up from your apps menu.
\end{enumerate}
cd <cin-path>/bin
mkdir /cinelerra #yes, currently only in the / filesystem
./cin_db /cinelerra/media.db #to create a new empty commercial capture database
-export BC_USE_COMMERCIALS=1 #in the command shell that is starting cinelerra
+export BC_USE_COMMERCIALS=1 #in the command shell that is starting Cinelerra
\end{lstlisting}
This activates the gui tools and database access. As of yet, all of the requisite permission changes
\item set the Total number of jobs to create;
\item click OK on the bottom of the Preferences window.
\end{itemize}
- \item On the client computers ($192.168.1.12$), start 5 background cinelerra tasks via:
+ \item On the client computers ($192.168.1.12$), start 5 background Cinelerra tasks via:
\begin{lstlisting}[language=bash,numbers=none]
$ cd /{path_to_cinelerra}
$ cin -d 401
...
$ cin -d 405
\end{lstlisting}
- \item On the master node (localhost), start the 2 background cinelerra tasks via:
+ \item On the master node (localhost), start the 2 background Cinelerra tasks via:
\begin{lstlisting}[language=bash,numbers=none]
$ cd /{path_to_cinelerra}
$ cin -d 406
Be aware that you may have to adjust any security or firewalls you have in place. \textit{Most firewalls will require extra rules to allow nfs access}. Many have built-in configurations for this.
\end{enumerate}
- \item[Configure Rendering on Master Node] There is 1 master node which is running the Cinelerra gui and where the video will be edited and the command given to start up the rendering. Any number of client computers can be run from the command line only, so they can be headless since no X or any graphical libraries are needed. Of course, the cinelerra software must be installed on each of the client computers.
+ \item[Configure Rendering on Master Node] There is 1 master node which is running the Cinelerra gui and where the video will be edited and the command given to start up the rendering. Any number of client computers can be run from the command line only, so they can be headless since no X or any graphical libraries are needed. Of course, the Cinelerra software must be installed on each of the client computers.
\begin{enumerate}
\item Assuming you already have Cinelerra installed on the master node, start Cinelerra by clicking on the
icon or by typing the following command on the terminal screen: \texttt{/{cinelerra\_path}/cin}.
\begin{lstlisting}[language=bash,numbers=none]
/{cinelerra_pathname}/cin -d [port #] ; \#for example /mnt1/bin/cinelerra -d 401
\end{lstlisting}
- This starts cinelerra in command prompt mode so that it listens to the specified port number for commands from the master node for rendering. When you start each of the clients up, you will see some messages scroll by as each client is created on that computer, such as:
+ This starts Cinelerra in command prompt mode so that it listens to the specified port number for commands from the master node for rendering. When you start each of the clients up, you will see some messages scroll by as each client is created on that computer, such as:
\begin{lstlisting}[language=bash,numbers=none]
RenderFarmClient::main_loop: client started
RenderFarmClient::main_loop: Session started from 127.0.0.1
\begin{lstlisting}[language=bash,numbers=none]
or n in `seq 1501 1505`; do cin -d $n; done
\end{lstlisting}
- \item[Render Using Render Farm] After you have followed the preceding steps, you are ready to use the render farm. Click on \texttt{File $\rightarrow$ Render}\dots which opens the render dialog. The most important point here is to use for \textit{the Output path / Select a file to render to} a path/file name that is on the shared volume that is also mounted on the clients. Click on OK to render. The cinelerra program divides the timeline into the number of jobs specified by the user. These jobs are then dispatched to the various nodes depending upon the load balance. The first segment will always render on the master node and the other segments will be farmed out to the render nodes. Batch Rendering, as well as BD/DVD rendering, may use the render farm. Each line in the batchbay can enable/disable the render farm. Typically, video can be rendered into many file segments and concatenated, but normally audio is rendered as one monolithic file (not farmed).
+ \item[Render Using Render Farm] After you have followed the preceding steps, you are ready to use the render farm. Click on \texttt{File $\rightarrow$ Render}\dots which opens the render dialog. The most important point here is to use for \textit{the Output path / Select a file to render to} a path/file name that is on the shared volume that is also mounted on the clients. Click on OK to render. The Cinelerra program divides the timeline into the number of jobs specified by the user. These jobs are then dispatched to the various nodes depending upon the load balance. The first segment will always render on the master node and the other segments will be farmed out to the render nodes. Batch Rendering, as well as BD/DVD rendering, may use the render farm. Each line in the batchbay can enable/disable the render farm. Typically, video can be rendered into many file segments and concatenated, but normally audio is rendered as one monolithic file (not farmed).
Another performance feature which can use the Render Farm is \textit{Background Rendering}. This is also enabled on the \texttt{Preferences $\rightarrow$ Performances} tab. The background render function generates a set of image files by pre-rendering the timeline data on the fly. As the timeline is update by editing, the image data is re-rendered to a \textit{background render} storage path. The Render Farm will be used for this operation if it is enabled at the same time as the \textit{background render} feature.
\item[Assemble the Output Files] Once all of the computer jobs are complete, you can put the output files together by using the shell script, \textit{RenderMux} (from the menubar \textit{scripts} button just above FF), if the files were rendered using ffmpeg, or you can load these by creating a new track and specifying concatenate to existing tracks in the load dialog in the correct numerical order. File types which support direct copy can be concatenated into a single file by rendering to the same file format with render farm disabled as long as the track dimensions, output dimensions, and asset dimensions are equal.
\item If one of the client computers is unavailable, check to see if there is an \texttt{X} to the left of the \texttt{nodename}
in the Nodes listbox. Check the \texttt{X} to disable it which sets ON to OFF.
\item A red message in the lower left hand corner of the main timeline that reads \textit{Failed to start render
- farm} often means that the client cinelerra programs were not started up.
+ farm} often means that the client Cinelerra programs were not started up.
\item A message of \texttt{RenderFarmWatchdog::run 1 killing server thread \\ \#address\#} means that the client did
not respond in time. You can adjust the timer in \texttt{Settings $\rightarrow$ Preferences, Performance} tab.
\item When you get the message \texttt{RenderFarmClient::main\_loop: bind port 400: Address already in use}, use a different port.
\item set up your Render (\texttt{Shift-R}), you can choose a raw format such as \textit{yuv} or \textit{rgb}
\item for the filename \textit{Select a file to render to}, use the named pipe as created in step 1 (\texttt{/tmp/piper.yuv})
\item for \textit{Insertion Strategy}, you will want to make sure to select \textit{insert nothing}
- \item click for OK on the green checkmark.(the cinelerra gui will look like it is hanging while waiting for a command line to use the pipe.)
+ \item click for OK on the green checkmark.(the Cinelerra gui will look like it is hanging while waiting for a command line to use the pipe.)
\item on the terminal window, keyin your command, for example:
\begin{lstlisting}[language=bash,numbers=none]
/mnt0/build5/cinelerra-5.1/thirdparty/ffmpeg-3.4.1/ffmpeg -f rawvideo -pixel_format yuv420p \ -video_size 1280x720 -framerate 30000/1001 -i /tmp/piper.yuv /tmp/pys.mov
\textcolor{blue}{Remote} & MENU & & Toggle remote control state (grabs/ungrabs keys) \\
& KPTV & & Open or close the record window \\
& KPBOOK & & Start/stop dvb channel scan \\
- & KPHAND & & Quit cinelerra program \\
+ & KPHAND & & Quit Cinelerra program \\
\midrule
\textcolor{blue}{Commercial} & & Shift-A & Edit commercial\\
\subsubsection*{2. Media cut and paste operations}%
\label{ssub:media_cut_paste_operations}
-To create a media selection, highlight a region on the cinelerra media timeline, then use the main menubar or compositor/viewer edit panel to operate the clip cut, copy, or copy-keyframe menu buttons. This selection can then be pasted to a target selection on the timeline using the main menubar or compositor/viewer edit panel to operate the clip paste or paste-keyframe operation. Also, by using the resource window you can select the \textit{Clips} folder and right mouse the resources list box, then use the \texttt{Paste Clip} menu item to paste the selection to a named clip. Additionally, these methods work between running instances of cinelerra, which means you can move media clips between the cinelerra program instances. The clip data is also copied to the secondary clipboard buffer. This makes it possible to examine the clip content directly if so desired.
+To create a media selection, highlight a region on the Cinelerra media timeline, then use the main menubar or compositor/viewer edit panel to operate the clip cut, copy, or copy-keyframe menu buttons. This selection can then be pasted to a target selection on the timeline using the main menubar or compositor/viewer edit panel to operate the clip paste or paste-keyframe operation. Also, by using the resource window you can select the \textit{Clips} folder and right mouse the resources list box, then use the \texttt{Paste Clip} menu item to paste the selection to a named clip. Additionally, these methods work between running instances of Cinelerra, which means you can move media clips between the Cinelerra program instances. The clip data is also copied to the secondary clipboard buffer. This makes it possible to examine the clip content directly if so desired.
\subsubsection*{3. The older cut\_buffer method}%
\label{ssub:older_cut_buffer_method}
\begin{itemize}
- \item For text, if there is an active selection when a window closes, it uses \texttt{cut\_buffer0}. Normally when a paste is performed, the target window \textit{notifies} the selection owner to \textit{send it now} when you do a paste, but if the window has closed there is no source window, so no pasting. Some programs, like cinelerra, use \texttt{cut\_buffer0} as a fallback. This makes it possible to paste data from a closed window.
+ \item For text, if there is an active selection when a window closes, it uses \texttt{cut\_buffer0}. Normally when a paste is performed, the target window \textit{notifies} the selection owner to \textit{send it now} when you do a paste, but if the window has closed there is no source window, so no pasting. Some programs, like Cinelerra, use \texttt{cut\_buffer0} as a fallback. This makes it possible to paste data from a closed window.
\item To move media clip, data \texttt{cut\_buffer2} is used because it does not require the selection owner interface, and works simply and reliably. This buffer is not normally in use by other programs.
\end{itemize}
\subsection*{Final note}%
\label{sub:final_note}
-When a text selection is set, the selected text is redrawn using selected-highlight color when the textbox loses focus. This convenience feature shows the active text selection as you move the pointer to the new target window. When a new selection is set anywhere else on your screen, the current text selection will be redrawn using the inactive-highlight color as the textbox loses selection ownership. In most cinelerra themes, the drag selection text-highlight color is BLUE ($\#0000FF$), the selected-highlight color is SLBLUE ($\#6040C0$) -- really sort of purple, and the inactive-highlight color is MEGREY ($\#AFAFAF$).
+When a text selection is set, the selected text is redrawn using selected-highlight color when the textbox loses focus. This convenience feature shows the active text selection as you move the pointer to the new target window. When a new selection is set anywhere else on your screen, the current text selection will be redrawn using the inactive-highlight color as the textbox loses selection ownership. In most Cinelerra themes, the drag selection text-highlight color is BLUE ($\#0000FF$), the selected-highlight color is SLBLUE ($\#6040C0$) -- really sort of purple, and the inactive-highlight color is MEGREY ($\#AFAFAF$).
\section{Playing is Different than Seeking/Positioning!}%
\label{sec:playing_seeking_positioning}
\section{Simple Animation (Festival)}%
\label{sec:simple_animation_festival}
-This functionality was added to cinelerra by the original author to create simple animation. The file type for this animation is \textit{Scene}.
+This functionality was added to Cinelerra by the original author to create simple animation. The file type for this animation is \textit{Scene}.
To get started making a simple animated movie copy from the directory: \texttt{<cin\_path>/cinelerra/tests} the \texttt{text2movie} and \texttt{text2movie.xml}. You can see what this does via \texttt{File $\rightarrow$ Load\dots $\rightarrow$ text2movie.xml}. The file text2movie acts like a normal asset, except changes to it are immediately reflected on the timeline without reloading and the length is infinite. You can just edit the text2movie file to change the script. If the length of the movie increases, drag the right edit handle to extend the edit or use the pulldown \texttt{Edit $\rightarrow$ edit length}. There is one audio channel created for every character. The frame rate, sample rate, frame size, and camera angles are fixed. To see these values, right click on the asset and look at the \textit{Asset info}.
You can add your own images to the Shape Wipe transition and there are some free ones available to download such as under the Video$\rightarrow$Transitions pulldown at \url{assistcg.com}.
To include new images in the Shape Wipe Transition, simply copy the file \texttt{{shape}.png} to the
- subdirectory \texttt{plugins/shapes} in your cinelerra directory path.
+ subdirectory \texttt{plugins/shapes} in your Cinelerra directory path.
\subsection*{Slide}%
\label{sub:slide}
Preview mode can be used to pop up a window which draws the vicons/aicons thumbnails in a larger size.
-Preview or \textit{draw vicons} mode is a helpful feature of cinelerra that lets you see and/or hear the first 5 seconds of the video for identification purposes.
+Preview or \textit{draw vicons} mode is a helpful feature of Cinelerra that lets you see and/or hear the first 5 seconds of the video for identification purposes.
The Preview mode/playback toggle is to the right of the Visibility label as seen in the screenshot above.
Preview mode is available for the Media, Proxy, Media User Bins, and Clips but clips are only 1 image.
\item right click on an unused portion of that window to bring up the popup menu
\item select the \textit{Copy file list} item and a file list box will appear that contains the full path filenames
\item wipe the textbox using your standard copy/paste method to put the list of files in the copy buffer
- \item in another cinelerra instance, choose the \textit{Paste file list} of the media Resources window
+ \item in another Cinelerra instance, choose the \textit{Paste file list} of the media Resources window
\item paste the list of files, again using your standard paste method, into the new file list box; press OK
\item the status bar of the main window will be updated as the file list is loaded to the media folder (the purpose of displaying the status is simply to show that the load is progressing normally).
\end{enumerate}
-Obviously this \textit{Paste file list} feature means you can create a list of files outside of cinelerra using an editor, wipe the names, and then use \textit{Paste file list} to load them into the media Resources window.
+Obviously this \textit{Paste file list} feature means you can create a list of files outside of Cinelerra using an editor, wipe the names, and then use \textit{Paste file list} to load them into the media Resources window.
It is important to note that in the steps above, the Operating System cut and paste capabilities are in use for steps 4 and 6 as opposed to Cinelerra’s c/v shortcuts.
Since the procedure varies among the distros, you will have to adapt to your specific one. For example, a usage for ubuntu consists of:
\label{fig:copy_files1}
\end{figure}
-In the Figure~\ref{fig:copy_files1}, one instance of cinelerra has 6 items in the Media area highlighted that were copied to the file list.
+In the Figure~\ref{fig:copy_files1}, one instance of Cinelerra has 6 items in the Media area highlighted that were copied to the file list.
Note how it includes the full pathname.
-In this screenshot on another instance of cinelerra, there are only 2 items in the media but the \textit{Paste file list} box is ready to have the items inserted via the standard text box paste method. When that is done, the additional 6 media files will be available on this other instance too.
+In this screenshot on another instance of Cinelerra, there are only 2 items in the media but the \textit{Paste file list} box is ready to have the items inserted via the standard text box paste method. When that is done, the additional 6 media files will be available on this other instance too.
Another possible usage of this capability:
projects / goodguy / cin-manual-latex.git / commitdiff