VA-API, Video Acceleration API, is an open source library which provides both hardware accelerated video encoding and decoding for use mostly with Intel (and AMD) graphics boards.
-Currently only the most common codecs, such as MPEG-1, MPEG-2, MPEG-4, and H.264 /MPEG-4, are accelerated/optimized by the graphics card to play these particular video formats efficiently. The other formats are not optimized so you will see no performance improvement since the CPU will handle them as before, just as if no hardware acceleration was activated. There are many different graphics cards and computer systems setup, so you will have to test which specific settings work best for you. So far this has been tested at least with Nvidia, Radeon, and Broadwell graphics boards on some AMD and Intel computers; depending on the graphics card, two to ten times higher processing speeds can be achieved. However, most graphic operations are single-threaded so that
+Currently only the most common codecs, such as MPEG-1, MPEG-2, MPEG-4, H.264 /MPEG-4 and h265 (hevc), are accelerated/optimized by the graphics card to play these particular video formats efficiently. The other formats are not optimized so you will see no performance improvement since the CPU will handle them as before, just as if no hardware acceleration was activated. There are many different graphics cards and computer systems setup, so you will have to test which specific settings work best for you. So far this has been tested at least with Nvidia, Radeon, and Broadwell graphics boards on some AMD and Intel computers; depending on the graphics card, two to ten times higher processing speeds can be achieved. However, most graphic operations are single-threaded so that
performing the operations in the hardware may actually be slower than in software making use of multiple CPUs, which frequently multi-thread many operations simultaneously.
\subsection{GPU hardware decoding}%
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.7\linewidth]{images/render-vaapi.png}
+ \includegraphics[width=1.0\linewidth]{render-vaapi.png}
\caption{Render menu setup to encode using GPU with vaapi}
\label{fig:render-vaapi}
\end{figure}
\begin{lstlisting}[numbers=none]
env CUDA_PATH=/opt/cuda
-#OR if using the bash shell:
+OR if using the bash shell:
export CUDA_PATH=/opt/cuda
\end{lstlisting}
For all distros you will need to add to the ./configure line in your build script, the following:
\begin{lstlisting}[numbers=none]
--with-cuda
-#so your configure line will look something like this:
+so your configure line will look something like this:
./configure --with-single-user --with-booby --with-cuda
\end{lstlisting}
As usual, you can delete proxy files from the project or disk in the Resources window if you no longer want to retain them.
And you can save your project either as proxied or not.
+Because Proxy works on the original media in all circumstances, when you resize the
+media in the Resources window, it does not actually resize the media but puts it in
+a "buffer" in that format. This might lead to some confusion for the user who
+expects this resizing to be maintained when disabling Proxy for that media. However,
+that does not happen because the resize is only in a buffer and not in the original
+media. This result is different than in the case of media "edits", like cuts or
+adding plugins because this information is not in a buffer but rather part of the
+copy "Editing Decision List" (EDL).
+
You can also nest clips while in a proxied state, but you can not drag the proxied nested clips
to the viewer or the timeline.
If you create proxies for Nested clips they will be saved in \texttt{\$HOME/Videos} unless you modify that in
There are two ways that the proxy files can be used, with or without input scaling. When the proxy is done without rescaling, the Mask, Camera and Projector automations are re-scaled accordingly. In this situation, the entire project will be re-sized so that the session is in the resized geometry. Not all plugins are useful when the project is rescaled, because the keyframe data must be in the original geometry. In this case, you can use the rescaler, by enabling \textit{Use scaler (FFMPEG only)}. This has the added advantage that the project size does not change and the proxy media is down-scaled as usual and up-scaled on read-in, which means the project editing is done in full scale. Since decoding is done on smaller video, there is a time savings, but all rendering is done full scale. The main reason for using \textit{scaler} is that it does not change the image coordinate data, so that automation and plugin parameters will be in the original project geometry. This is not as fast as the first option, but is a performance gain, and may be needed if you are using plugins that need coordinate data such as the Title plugin. As noted, the scaler only works on ffmpeg video formats.
-In the upper right hand corner of the main window, there is a toggle button to easily switch back and forth when you have a proxied file on the timeline. The icon is to the left of the FF icon. It will have the letter “P” as the icon for Proxy or if \textit{Using Scaler}, the letter “S”. \quad \includegraphics[height=\baselineskip]{images/proxy-01.png} \quad This quick switch is especially useful when editing and you need to see a better image temporarily.
+In the upper right hand corner of the main window, there is a toggle button to easily switch back and forth when you have a proxied file on the timeline. The icon is to the left of the FF icon. It will have the letter “P” as the icon for Proxy or if \textit{Using Scaler}, the letter “S”. \quad \includegraphics[height=\baselineskip]{proxy-01.png} \quad This quick switch is especially useful when editing and you need to see a better image temporarily.
Screencast in figure~\ref{fig:proxy-02} shows the Use scaler checked so you can still use plugins and the original project size is kept. The Scale factor pull-down gives you available size options. Note the new media dimensions shown (partially covered). If the size is an odd number, 1 is added to make the dimensions both even numbers.
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.6\linewidth]{images/proxy-02.png}
+ \includegraphics[width=0.6\linewidth]{proxy-02.png}
\caption{Proxy settings dialog}
\label{fig:proxy-02}
\end{figure}
More specific information on which plugins need to use scaler is provided here next. If the keyframe data uses coordinate data that is absolute, then the scaler should be used. If the data is normalized (like always $0-100\%$) then the proxy can be done without the scaler. The session geometry format, shown in \texttt{Settings $\rightarrow$ Format} as $width \times height$, is changed if the scaler is not used to cause all of the data to be in the reduced format. If this affects the plugin operation, then scaler should be used. Examples of plugins that need the scaler are: Title, AutoScale, Scale, ScaleRatio, and Translate. Most others are safe to use without scaling.
- This makes its so that you can save your project
-either as proxied or not.
-
\textbf{Transcode}, an option under the Settings pulldown right next to the Proxy settings option, is a type of full resolution \textbf{1:1 Proxy}.
The process of transcoding works directly from the resource; it is independent of the timeline.
All of the loaded asset media will be converted, that is, rendered in the selected format and loaded onto the timeline.
\begin{figure}[htpb]
\centering
- \includegraphics[width=1.0\linewidth]{images/aeval.png}
+ \includegraphics[width=1.0\linewidth]{aeval.png}
\caption{Use Audio$\rightarrow$Render effect to set render parameter values and then that effect can be varied.}
\label{fig:aeval}
\end{figure}
\begin{figure}[htpb]
\centering
- \includegraphics[width=0.8\linewidth]{images/ringtone.png}
+ \includegraphics[width=0.8\linewidth]{ringtone.png}
\caption{Using the Compressor plugin graph to create a ringtone}
\label{fig:ringtone}
\end{figure}
projects / goodguy / cin-manual-latex.git / blobdiff