More specific information on which plugins need to use \textit{Proxy 1:1}. is provided here next. If the keyframe data uses coordinate data that is absolute, then the Factor scale = 1 should be used. If the data is normalized (like always $0-100\%$) then the proxy can be done with downsize (i.e. classic \textit{Proxy}). The session geometry format, shown in \texttt{Settings $\rightarrow$ Format} as $width \times height$, is changed if scale factor $\neq$ 1 is used to cause all of the data to be in the reduced format. If this affects the plugin operation, then \textit{Proxy 1:1} should be used. Examples of plugins that need the \textit{Proxy 1:1} are: Title, AutoScale, Scale, ScaleRatio, and Translate. Most others are safe to use with downsize.
+\subsection{Proxies with Alpha channel}%
+\label{sub:proxies_alpha_channel}
+
+Next are some examples of tested and working configurations that maintain the alpha channel:
+
+\begin{lstlisting}[numbers=none]
+Proxy #1
+ Scale factor: 1/4
+ Rescaled to project size (FFMEG only) = unchecked
+ File Format: FFMPEG | qt
+ Video Preset-->
+ Compression: png.qt
+ Bitrate: 0
+ Quality: -1
+ Pixels: rgba (or rgba64be)
+
+
+Proxy #2
+ Scale factor: 1/4
+ Rescaled to project size (FFMEG only) = unchecked
+ File Format: FFMPEG | qt
+ Video Preset-->
+ Compression: magicyuv.qt
+ Bitrate: 0
+ Quality: -1
+ Pixels: yuva444p
+
+
+Proxy #3
+ Scale factor: 1/4
+ Rescaled to project size (FFMEG only) = unchecked
+ File Format: FFMPEG | qt
+ Video Preset-->
+ Compression: openjpeg.qt
+ Bitrate: 0
+ Quality: -1
+ Pixels: yuva420p
+
+
+Proxy #4
+ Scale factor: 1/4
+ Rescaled to project size (FFMEG only) = unchecked
+ File Format: FFMPEG | pro
+ Video Preset-->
+ Compression: prores_4444.pro
+ prores_4444xq.pro
+ Bitrate: 0
+ Quality: -1
+ Pixels: yuva444p10le
+
+
+Proxy #5
+ Scale factor: 1/4
+ Rescaled to project size (FFMEG only) = unchecked
+ File Format: FFMPEG | mkv
+ Video Preset-->
+ Compression: user_ffvhuff.mkv
+ Bitrate: 0
+ Quality: -1
+ Pixels: yuva4--p
+ yuva4--p--le
+\end{lstlisting}
+
\section{Transcode}%
\label{sec:transcode}
\index{transcode}
\nomenclature{\color{CinBlueText}{Bezier curve}}{a parametric curve used in computer graphics. In image manipulation programs, bezier curves are used to model smooth curves.}
-\nomenclature{\color{CinBlueText}{Bitrate}}{represents the amount of information that is stored per unit of time of a recording. The higher the bitrate, the higher the quality.}
+\nomenclature{\color{CinBlueText}{Bitrate}}{represents the amount of information that is stored per unit of time of a recording. The higher the bitrate, the higher the quality. When setting Bitrate in rendering, be sure to not set any Quality or CRF values because they take precdence.}
\nomenclature{\color{CinBlueText}{Brightness}}{human perception of the amount of light emitted by a source; overall lightness or darkness of an image. In video signals it is represented by luma. The measure of brightness is value.}
list. The list is provided by ffmpeg as input selection, but is
more like suggestions than fact. For example, the raw formats can
take almost any format, but the rawvideo codec actually specifies no
- legal formats.
+ legal formats. Note that if you want a very specific Bitrate you must
+ make sure there is not conflicting parameter values set such as Quality
+ or CRF.
\end{itemize}
\noindent Some option files provide \textit{cin\_pix\_fmt} to
parameter dictates pixel format must be \texttt{yuv420p}.
\paragraph{cin\_bitrate} If you specify the bitrate, you can not
-specify the quality.\\ Example: \textit{cin\_bitrate=2000000}
+specify the quality or CRF.\\ Example: \textit{cin\_bitrate=2000000}
\paragraph{cin\_quality} If you specify the quality, you can not
specify the bitrate.\\ Example: \textit{cin\_quality=7}