X-Git-Url: https://git.cinelerra-gg.org/git/?p=goodguy%2Fcin-manual-latex.git;a=blobdiff_plain;f=parts%2FRecording.tex;h=9a61832a072909a642f1f305916b6302e3f76c52;hp=6fb57e3e9f9b3936a99f9c31bc2409e75211cba9;hb=6b9ffc5e7544ea2090ef8251d33b2b507974a8ad;hpb=57a86b4cce1e2f98b917a90db8027f55ea3e0d7b diff --git a/parts/Recording.tex b/parts/Recording.tex index 6fb57e3..9a61832 100644 --- a/parts/Recording.tex +++ b/parts/Recording.tex @@ -80,7 +80,7 @@ Screenshot to illustrate some appropriate settings which are described above/bel \begin{figure}[htpb] \centering - \includegraphics[width=0.8\linewidth]{images/recording01.png} + \includegraphics[width=0.8\linewidth]{recording01.png} \caption{Recording window with tipical settings} \label{fig:recording01} \end{figure} @@ -159,7 +159,7 @@ One other noted new feature is a new choice for recording - \texttt{V4L2 MPEG}. \begin{figure}[htpb] \centering - \includegraphics[width=0.8\linewidth]{images/recording02.png} + \includegraphics[width=0.8\linewidth]{recording02.png} \caption{new feature v4l2 mpeg} \label{fig:recording02} \end{figure} @@ -234,7 +234,7 @@ Figure~\ref{fig:recording03} shows the Preferences window as a good example of w \begin{figure}[htpb] \centering - \includegraphics[width=0.99\linewidth]{images/recording03.png} + \includegraphics[width=0.99\linewidth]{recording03.png} \caption{Example of the Recording settings} \label{fig:recording03} \end{figure} @@ -255,7 +255,7 @@ Figure~\ref{fig:channels01} on the left shows the Channels window and the popup \begin{figure}[htpb] \centering - \includegraphics[width=0.99\linewidth]{images/channels01.png} + \includegraphics[width=0.99\linewidth]{channels01.png} \caption{Clockwise: Channels window; Video In (behind); Recording and Scan confirm} \label{fig:channels01} \end{figure} @@ -264,7 +264,7 @@ Figure~\ref{fig:channels02} shows scanning in progress. Note the \textit{Video \begin{figure}[htpb] \centering - \includegraphics[width=0.99\linewidth]{images/channels02.png} + \includegraphics[width=0.99\linewidth]{channels02.png} \caption{Scanning in progress ($6\%$)} \label{fig:channels02} \end{figure} @@ -301,7 +301,7 @@ Figure~\ref{fig:channels03} shows \textit{Channel Info} window after the Ctrl-Al \begin{figure}[htpb] \centering - \includegraphics[width=1.0\linewidth]{images/channels03.png} + \includegraphics[width=1.0\linewidth]{channels03.png} \caption{Channels Info window with many TV channels buttons} \label{fig:channels03} \end{figure} @@ -331,7 +331,7 @@ Figure~\ref{fig:recording04} shows the recording of a currently running broadcas \begin{figure}[htpb] \centering - \includegraphics[width=0.95\linewidth]{images/recording04.png} + \includegraphics[width=0.95\linewidth]{recording04.png} \caption{Recording in real-time a tv weather report} \label{fig:recording04} \end{figure} @@ -345,7 +345,7 @@ Figure~\ref{fig:realtime_toc} shows the red-checked \textit{Realtime TOC} for th \begin{figure}[htpb] \centering - \includegraphics[width=0.8\linewidth]{images/realtime_toc.png} + \includegraphics[width=0.8\linewidth]{realtime_toc.png} \caption{Realtime TOC check red button} \label{fig:realtime_toc} \end{figure} @@ -386,7 +386,7 @@ Figure~\ref{fig:two-monitors01} shows 2 monitors (could just as well be a big-sc \begin{figure}[htpb] \centering - \includegraphics[width=0.85\linewidth]{images/two-monitors01.png} + \includegraphics[width=0.85\linewidth]{two-monitors01.png} \caption{Dual screen - initial} \label{fig:two-monitors01} \end{figure} @@ -395,7 +395,7 @@ Figure~\ref{fig:two-monitors02} shows 2 monitors with Tile right (b key) where a \begin{figure}[htpb] \centering - \includegraphics[width=0.85\linewidth]{images/two-monitors02.png} + \includegraphics[width=0.85\linewidth]{two-monitors02.png} \caption{Dual screen - \CGG{} and desktop on different screens} \label{fig:two-monitors02} \end{figure} @@ -404,7 +404,7 @@ Figure~\ref{fig:two-monitors03} shows 2 monitors with Compositor window on the 2 \begin{figure}[htpb] \centering - \includegraphics[width=0.85\linewidth]{images/two-monitors03.png} + \includegraphics[width=0.85\linewidth]{two-monitors03.png} \caption{Dual screen - \CGG{} compositor on own screen windowed} \label{fig:two-monitors03} \end{figure} @@ -413,7 +413,7 @@ Figure~\ref{fig:two-monitors04} shows 2 monitors with Compositor window on the 2 \begin{figure}[htpb] \centering - \includegraphics[width=0.85\linewidth]{images/two-monitors04.png} + \includegraphics[width=0.85\linewidth]{two-monitors04.png} \caption{Dual screen - \CGG{} compositor on own screen full screen} \label{fig:two-monitors04} \end{figure} @@ -423,7 +423,7 @@ Figure~\ref{fig:two-monitors04} shows 2 monitors with Compositor window on the 2 \begin{wrapfigure}[18]{O}{0.3\linewidth} \centering - \includegraphics[width=0.5\linewidth]{images/remote01.png} + \includegraphics[width=0.5\linewidth]{remote01.png} \caption{Ati-x10 Remote} \label{fig:remote01} \end{wrapfigure} @@ -501,7 +501,7 @@ Remote Control Keys (Application/Menu key toggle for ati-x10 remote) \end{tabular} The Application/Menu key \quad -\includegraphics[height=\baselineskip]{images/alt-ctrl.png} \quad +\includegraphics[height=\baselineskip]{alt-ctrl.png} \quad is used to get into remote control mode, even if there is no remote control hardware device in use, allowing for use of the same defined remote control keys to work on the keyboard. Once the Application/Menu key enables remote mode, the remote control keys don't allow the standard \CGG{} keys to work. \subsection{Android Remote Control for DVB}% @@ -517,7 +517,7 @@ is used to get into remote control mode, even if there is no remote control hard \begin{figure}[htpb] \centering - \includegraphics[width=0.9\linewidth]{images/remote02.png} + \includegraphics[width=0.9\linewidth]{remote02.png} \caption{Interface tab shows Android Remote Control} \label{fig:remote02} \end{figure} @@ -532,7 +532,7 @@ Figure~\ref{fig:remote03} shows an Android Tablet that can be used as a Remote C \begin{figure}[htpb] \centering - \includegraphics[width=0.6\linewidth]{images/remote03.png} + \includegraphics[width=0.6\linewidth]{remote03.png} \caption{A Tablet with Android Remote Control} \label{fig:remote03} \end{figure} @@ -568,7 +568,7 @@ It mostly works, but it takes more time to setup and maintain the database as th Currently, to activate the commercial database (db) methods you must do the following as root: -\begin{lstlisting}[language=bash,numbers=none] +\begin{lstlisting}[style=sh] cd /bin mkdir /cinelerra #yes, currently only in the / filesystem ./cin_db /cinelerra/media.db #to create a new empty commercial capture database @@ -602,10 +602,15 @@ To review media stored in the \texttt{media.db}, and delete old expired commerci Currently, only a customized \textit{ati-x10} (kernel mod required) radio remote control works. But this can quite readily be modified for other remote control models. -\section{Transfer VHS/DVD Media into \CGG{}}% -\label{sec:transfer_vhs_dvd_into_cinelerra} +\section{Transfer VHS/DVD Media or Video8/Hi8 Tapes into \CGG{}}% +\label{sec:transfer_vhs_dvd_tapes_into_cinelerra} -If you want to transfer the data on a VHS tape or DVD disc into \CGG{}, you can do so by playing the media and recording while playing. This captures the media, which you are able to view as it plays, and writes it to a file so it can be played directly or edited. Because there is so much variation in hardware on both the Computer side and the Media Player side, these \textit{how to} directions are only a guideline. You will most likely still have to do some experimentation and testing to see what works for you. +If you want to transfer the data on a VHS tape, DVD disc, or Video8/Hi8 Tapes into \CGG{}, you +can do so by playing the media and recording while playing. This captures the media, which you +are able to view as it plays, and writes it to a file so it can be played directly or edited. +Because there is so much variation in hardware on both the Computer side and the Media Player side, +these \textit{how to} directions are only a guideline. You will most likely still have to do some +experimentation and testing to see what works for you. The basic strategy consists of 3 operations: connect the relevant outputs to representative inputs, configure the capture card to match the video, and start the Record monitor. Each of these may have to be experimented with to get them correct for your hardware setup. @@ -613,7 +618,7 @@ The basic strategy consists of 3 operations: connect the relevant outputs to re For example in a test case using the \textit{CX23418} capture card (an older/unusual single chip MPEG-2 encoder with integrated analog video/broadcast audio decoder), one end of an S-Video cable was plugged into the back of a DVD player and the other end plugged into this computer’s Capture card; the audio was plugged into the \textit{line in} on the computer sound card. -\textit{Step 2}:Setup \CGG{} and it might be best the first time if you start with a default \texttt{.bcast5} file by using a +\textit{Step 2}: Setup \CGG{} and it might be best the first time if you start with a default \texttt{.bcast5} file by using a command line from a window of \\ \texttt{CIN\_CONFIG=\$HOME/bcast6 {cinelerra\_path}/bin/cin} @@ -621,13 +626,13 @@ command line from a window of \\ \item Choose \texttt{Settings $\rightarrow$ Preferences $\rightarrow$ Recording} tab in the Preferences menu (figure~\ref{fig:recordingx}). \item Choose a \textit{File Format} -- a common suggestion is \textit{ffmpeg} with a \textit{file type} of mp4. In some cases depending on your capture card, the File Format will be set to \textit{MPEG stream} capture. Some formats support MPEG stream capture technique, otherwise the data has to be decoded first and then encoded. \item Check that the \textit{Audio In} section has the \textit{Record Driver} set to \textit{Alsa} with \textit{Device} set to \textit{default} as the Capture Source. If you are using something besides Alsa, change that selection accordingly. This may not always be default and you may have to change to something else based on your specific hardware. It has to match up what you see in our Control Panel on your computer. So for example, if your device is HDMI, than the \textit{default} could be \textit{HDMI}\dots instead. - \item In the \textit{Video In} section, change the\textit{ Record Driver} to whatever makes sense for your capture card. The test case for the CX23418 would use Video4Linux2 MPEG. If unknown what your card uses, you should experiment with Video4Linux2 or Screencapture as good possibilities. - \item Also, \textit{Device path} should be verified to be correct in case you have more than 1 device. + \item In the \textit{Video In} section, change the\textit{ Record Driver} to whatever makes sense for your capture card. The test case for the CX23418 would use Video4Linux2 MPEG. A test case for an EasyCap Model \#DC60 would use Video4Linux2 JPEG. If unknown what your card uses, you should experiment with Video4Linux2 or Screencapture as good possibilities. + \item Also, \textit{Device path} should be verified to be correct in case you have more than 1 device. In the 2 previously mentioned devices, it should proabably be set to /dev/video0. \end{itemize} \begin{figure}[htpb] \centering - \includegraphics[width=0.9\linewidth]{images/recording03.png} + \includegraphics[width=0.9\linewidth]{recording03.png} \caption{Example of the Preferences menu with the Recording tab highlighted} \label{fig:recordingx} \end{figure} @@ -643,7 +648,7 @@ command line from a window of \\ \begin{figure}[htpb] \centering - \includegraphics[width=0.9\linewidth]{images/vhs01.png} + \includegraphics[width=0.9\linewidth]{vhs01.png} \caption{Example of the Recording, Video In, and Channels, along with the Add option, menus.} \label{fig:vhs01} \end{figure} @@ -659,10 +664,83 @@ There are many more parameters that you may want to vary in the Recording menu o \begin{figure}[htpb] \centering - \includegraphics[width=0.9\linewidth]{images/vhs02.png} + \includegraphics[width=0.9\linewidth]{vhs02.png} \caption{Recording menu and Video In screen while capturing media. Note the Transport stop option.} \label{fig:vhs02} \end{figure} Now you can \textit{Load} the file that you played and recorded via the \textit{Insertion strategy} choices on the bottom of the Recording menu and edit the file as usual. Note, that the audio and video may have started at slightly different times so you might have to initially line them up at the beginning using \texttt{nudge}. Generally once they are correctly aligned they will stay that way. Nudge is in the expanded patchbay. The nudge value is the amount the track is shifted left or right during playback. The track is not displayed shifted on the timeline, but it is shifted when it is played back. +\subsection{Use Case \#1 – EasyCap Model \# DC60} +\label{sub:use_case_easycap_model_dc60} + +A very specific case using an Easy CAPture USB 2.0 Video Adapter with Audio, Model \#DC60 (supports +NTSC and PAL) is shown here next. The setup for this device is seen in figure~\ref{fig:recording-usb}. +A somewhat unusual choice to make note of in this image is the setting for the Video In, Record Driver +of Video4Linux2 JPEG. + +\begin{figure}[htpb] + \centering + \includegraphics[width=0.9\linewidth]{recording05.png} + \caption{Recording setup for EasyCap device} + \label{fig:recording-usb} +\end{figure} + +Output on startup window while playing: +\begin{lstlisting}[style=sh] +DeviceV4L2Base::v4l2_open pixels="MJPG"; res="480x320 640x480 720x480" +DeviceV4L2Base::v4l2_open pixels="YUYV"; res="480x320" +v4l2 s_fmt 640x480 MJPG +DeviceV4L2Base::v4l2_open VIDIOC_S_STD: Inappropriate ioctl for device +DeviceV4L2Base::v4l2_open VIDIOC_G_JPEGCOMP: Inappropriate ioctl for device +DeviceV4L2Base::v4l2_open VIDIOC_S_JPEGCOMP: Inappropriate ioctl for device +[Detaching after vfork from child process 6539] +\end{lstlisting} + +\begin{lstlisting}[style=sh] +Output from "dmesg" for EasyCap - Model \# DC60: + +[ 748.560775] usb 3-1.2: new high-speed USB device number 8 using xhci_hcd +[ 748.574296] usb 3-1.2: New USB device found, idVendor=534d, idProduct=0021, bcdDevice= 1.21 +[ 748.574303] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 +[ 748.574307] usb 3-1.2: Product: AV TO USB2.0 +[ 748.574310] usb 3-1.2: Manufacturer: MACROSILICON +[ 748.574313] usb 3-1.2: SerialNumber: 20150130 +[ 748.635600] hid-generic 0003:534D:0021.0008: hiddev97,hidraw0: USB HID v1.10 Device [MACROSILICON AV TO USB2.0] on usb-0000:16:00.3-1.2/input4 +[ 748.698491] mc: Linux media interface: v0.10 +[ 748.727360] videodev: Linux video capture interface: v2.00 +[ 748.796533] usbcore: registered new interface driver snd-usb-audio +[ 748.796660] uvcvideo: Found UVC 1.00 device AV TO USB2.0 (534d:0021) +[ 748.796876] uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround. +[ 748.797204] uvcvideo 3-1.2:1.0: Entity type for entity Processing 2 was not initialized! +[ 748.797212] uvcvideo 3-1.2:1.0: Entity type for entity Camera 1 was not initialized! +[ 748.797353] usbcore: registered new interface driver uvcvideo +[ 748.797356] USB Video Class driver (1.1.1) +[ 3982.626522] retire_capture_urb: 7 callbacks suppressed +[ 3982.747515] usb 3-1.2: USB disconnect, device number 8 +[ 4007.286371] usb 3-1.2: new high-speed USB device number 9 using xhci_hcd +[ 4007.302726] usb 3-1.2: New USB device found, idVendor=534d, idProduct=0021, bcdDevice= 1.21 +[ 4007.302732] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 +[ 4007.302736] usb 3-1.2: Product: AV TO USB2.0 +[ 4007.302740] usb 3-1.2: Manufacturer: MACROSILICON +[ 4007.302743] usb 3-1.2: SerialNumber: 20150130 +[ 4007.354826] uvcvideo: Found UVC 1.00 device AV TO USB2.0 (534d:0021) +[ 4007.354939] uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround. +[ 4007.355252] uvcvideo 3-1.2:1.0: Entity type for entity Processing 2 was not initialized! +[ 4007.355256] uvcvideo 3-1.2:1.0: Entity type for entity Camera 1 was not initialized! +[ 4007.420828] hid-generic 0003:534D:0021.0009: hiddev97,hidraw0: USB HID v1.10 Device [MACROSILICON AV TO USB2.0] on usb-0000:16:00.3-1.2/input4 +\end{lstlisting} + +\subsection{Use Case \#2 – Hauppauge WinTV-HVR} +\label{sub:use_case_wintv} + +In the case of the Hauppauge 9500 WinTV-HVR Hybrid TV stick, the setup is similar as in case +\#1 with the major exception being that the Video In, Record Driver should be Video4Linux2 MPEG. + +\begin{figure}[htpb] + \centering + \includegraphics[width=0.9\linewidth]{recording06.png} + \caption{Two possible capture devices using USB} + \label{fig:recording-usb} +\end{figure} +