From f6533647006d7c65bd6091b2668743d490a68859 Mon Sep 17 00:00:00 2001 From: Good Guy Date: Fri, 26 Dec 2025 16:29:10 -0700 Subject: [PATCH] Fixed website changed links and checked other http references for a couple of corrections --- parts/Developer.tex | 6 ++--- parts/Editing.tex | 4 +-- parts/Installation.tex | 24 +++++++++--------- parts/Introduction.tex | 2 +- parts/Licenses.tex | 2 +- parts/Plugins.tex | 56 ++++++++++++++++++++---------------------- parts/Quickstart.tex | 5 ++-- parts/Real-World.tex | 7 ++---- parts/Rendering.tex | 2 +- parts/Transition.tex | 4 +-- parts/Trouble.tex | 8 +++--- parts/Windows.tex | 2 +- 12 files changed, 56 insertions(+), 66 deletions(-) diff --git a/parts/Developer.tex b/parts/Developer.tex index c9f52f3..4bf5ca4 100644 --- a/parts/Developer.tex +++ b/parts/Developer.tex @@ -717,7 +717,7 @@ The steps to recreate the appimage are: A new appimage will be created like the original but containing the changes. -Alternatively, download the \texttt{appimagetool} version from \url{https://github.com/AppImage/AppImageKit/releases} if available for your distro and use the command: +Alternatively, download the \texttt{appimagetool} version from \url{https://github.com/AppImage/appimagetool/releases} if available for your distro and use the command: \begin{lstlisting}[numbers=none] ./appimagetool --comp /{path to appimage}/squashfs-root /tmpCinGG-yyyymmdd.AppImage @@ -769,11 +769,11 @@ Then move to the \texttt{/\{path to cinelerra-5.1}/\} directory. There are two preliminaries to do before running the script: -1- If context sensitive help in the appimage version is required, the source of the manual and the tools (packages) to build it must be on the system. In the bld\_appimage.sh script, set the variable \texttt{MANUAL\_DIRECTORY=\$(pwd)/../../ cin-manual-latex} to the path of the source of the manual. If the variable is empty, or the specified directory does not exist, \CGG{} will be built without built-in help. The path to the manual source can be an absolute or relative one. An easier method to include the help from the manual rather than having to install a bunch of latex building software, is to simply download the latest tgz version from {\small\url{https://cinelerra-gg.org/download/images/HTML_Manual-202xxxxx.tgz}}. +1- If context sensitive help in the appimage version is required, the source of the manual and the tools (packages) to build it must be on the system. In the bld\_appimage.sh script, set the variable \texttt{MANUAL\_DIRECTORY=\$(pwd)/../../ cin-manual-latex} to the path of the source of the manual. If the variable is empty, or the specified directory does not exist, \CGG{} will be built without built-in help. The path to the manual source can be an absolute or relative one. An easier method to include the help from the manual rather than having to install a bunch of latex building software, is to simply download the latest tgz version from {\small\url{https://download.cinelerra-gg.org/?path=\%2Fimages} look for HTML\_Manual-202xxxxx.tgz}. Then extract the files using "tar xvf" into the cinelerra AppDir/usr/bin/doc directory. This alternative method may not contain the most recent changes to the Manual but rather will contain what had been checked into Git by the date of the tgz file. -2- The script bld\_appimage.sh uses a platform specific version of appimagetool so that it can create appimages for \textit{x86\_64}, \textit{i686}, \textit{aarch64}, or \textit{armv7l} architecture. We need to add appimagetool-(platform).AppImage to the \texttt{/\{path to cinelerra- 5.1\}/tools} directory, or somewhere in your path. You can download the tool for your system (e.g. appimagetool-x86\_64.AppImage) from git: {\small\url{https://github.com/AppImage/AppImageKit/releases}}. Be aware of the possibility that an older appimagetool from 2020 might work better on some systems compared to the latest release. +2- The script bld\_appimage.sh uses a platform specific version of appimagetool so that it can create appimages for \textit{x86\_64}, \textit{i686}, \textit{aarch64}, or \textit{armv7l} architecture. We need to add appimagetool-(platform).AppImage to the \texttt{/\{path to cinelerra- 5.1\}/tools} directory, or somewhere in your path. You can download the tool for your system (e.g. appimagetool-x86\_64.AppImage) from git: {\small\url{https://github.com/AppImage/appimagetool/releases/}}. Be aware of the possibility that an older appimagetool from 2020 might work better on some systems compared to the latest release. Always remember to make it executable. The four supported platforms are: diff --git a/parts/Editing.tex b/parts/Editing.tex index 68cd6ce..19e9d41 100644 --- a/parts/Editing.tex +++ b/parts/Editing.tex @@ -1511,8 +1511,8 @@ having a local file in your \texttt{\$HOME} directory, named Detailed information on how to modify your local \texttt{.shuttlerc} file is described next, but if you need help you can request more -information in the forum at {\small - \url{https://cinelerra-gg.org}}. In the \texttt{shuttlerc} file, a +information in the forum at {\small + \url{https://cinelerra-gg.org/forum/}}. In the \texttt{shuttlerc} file, a \# always represents a comment and blank lines are ignored. The first thing you must do is copy the system supplied \texttt{shuttlerc} file to your \texttt{\$HOME} directory and rename diff --git a/parts/Installation.tex b/parts/Installation.tex index 26a785b..2636b83 100644 --- a/parts/Installation.tex +++ b/parts/Installation.tex @@ -46,9 +46,9 @@ Finally start the program from a window in the directory where the image is stor \end{lstlisting} or create a convenient desktop icon with a link to the run action, or do a \textit{Desktop Integration} manually or with external programs. There is a -description of a GUI methodology for doing so in the file README\_appimage at: +description of a GUI methodology for doing so in the file to download at: -\url{https://download.cinelerra-gg.org/?path=\%2Fimages} +\url{https://download.cinelerra-gg.org/download.php?file=images\%2FREADME_appimage.txt} Most distros already have the libraries to run the appimage, but if not you may need an additional installation. For example Arch Linux needs the \texttt{libappimage} package. @@ -72,7 +72,7 @@ Using AppImage means you do not have the installation folder and work on the fil \label{sec:appimage_standard_shortcuts} In video editing it is important to learn how to use shortcuts to speed up your work. \CGG{} uses shortcuts different from those considered standard in both the Linux world and video editing. For example, \texttt{"s"} is used instead of \texttt{Ctrl+S}, \texttt{"q"} instead of \texttt{Ctrl+Q}, and even the classic editing keys \texttt{J, K, L} are different. -In addition, in \CGG{} the keys are fixed and not customizable. A new user may have a hard time getting used to a new combination of shortcuts. To make it a little easier, an appimage containing a patch that makes use of some of the more frequently used classic key combinations is available. It can be downloaded \href{https://cinelerra-gg.org/download/images/CinGG-20230930-alternative_shortcuts.AppImage}{here} (note that the file contains the month and last day of the month, but you will want to go up a directory and download the latest date instead to include the current changes). A table showing the changes from \CGG{} mode to standard mode can be found here: \nameref{sec:alternative_shortcuts}. +In addition, in \CGG{} the keys are fixed and not customizable. A new user may have a hard time getting used to a new combination of shortcuts. To make it a little easier, an appimage containing a patch that makes use of some of the more frequently used classic key combinations is available. It can be downloaded \href{https://download.cinelerra-gg.org/download.php?file=images\%2F/CinGG-20251121-alternative_shortcuts.AppImage}{here} (note that the file contains the month and last day of the month, but you will want to go up a directory and download the latest date instead to include the current changes). A table showing the changes from \CGG{} mode to standard mode can be found here: \nameref{sec:alternative_shortcuts}. \section{Download Already Built \CGG{}}% \label{sec:download_already_built_cinelerra_gg} @@ -130,7 +130,7 @@ system area and for multi-user systems. In addition, performing the package install checks the md5sum in the file \texttt{md5sum.txt} to ensure the channel correctly transmits the package. There is a -\href{https://download.cinelerra-gg.org/}{README.pkgs} +\href{https://download.cinelerra-gg.org/download.php?file=\%2FREADME.pkgs} file in the \texttt{download} directory with instructions so you can \textit{cut and paste} and avoid typos; it is also shown next. @@ -168,8 +168,6 @@ and will have the name of HTML\_Manual-20251121.tgz substituting for Then unpack to your cinelerra/bin/doc directory so it is included in your built system. -\url{https://download.cinelerra-gg.org/?path=\%2Fimages} and look for the latest release in that folder. - Alternatively, there are some pre-built dynamic or static binaries in the \textit{images} folder which are updated on a fairly regular basis (as long as code changes have been made) available at this link. @@ -234,7 +232,7 @@ To do a system build \index{build} , you should read the file \begin{lstlisting}[style=sh] # This is where you need the 6.0GB of disk space: cd // -git clone --depth 1 https://git.cinelerra-gg.org/goodguy/cinelerra.git +git clone --depth 1 https://git.cinelerra-gg.org/goodguy/cinelerra.git cinelerra # Change to the cloned directory: cd cinelerra/cinelerra-5.1 \end{lstlisting} @@ -306,7 +304,7 @@ the top level after you get the source. \begin{lstlisting}[style=sh] # This is where you need the 6GB of disk space cd // -git clone --depth 1 https://git.cinelerra-gg.org/goodguy/cinelerra.git +git clone --depth 1 https://git.cinelerra-gg.org/goodguy/cinelerra.git cinelerra # Toplevel directory: cd cinelerra/cinelerra-5.1 \end{lstlisting} @@ -748,7 +746,7 @@ keep it. \begin{lstlisting}[style=sh] cd // -git clone --depth 1 https://git.cinelerra-gg.org/goodguy/cinelerra.git +git clone --depth 1 https://git.cinelerra-gg.org/goodguy/cinelerra.git cinelerra cp -a //cinelerra-5.1 /tmp/ cd /tmp/cinelerra-5.1 ./bld.sh @@ -953,7 +951,7 @@ Terminal \begin{enumerate} \item Download the libxcb-bld-tar.bz2 tar file at: - \href{https://download.cinelerra-gg.org/?path=\%2Ftesting}{libxcb-bld.tar.bz2}. + \href{https://download.cinelerra-gg.org/download.php?file=testing\%2Flibxcb-bld.tar.bz2}. \item Install libxcb from the tar file -- installs into \texttt{/usr/local} and requires approximately 21MB storage. @@ -964,7 +962,7 @@ tar -C /usr/local -xJf /path/libxcb-bld.tar.bz2 Cinelerra. \item Download the cygcin-bld.tar.bz2 file at: - \href{https://download.cinelerra-gg.org/?path=\%2Ftesting}{cygcin-bld.tar.bz2}. + \href{https://download.cinelerra-gg.org/download.php?file=testing\%2Fcygcin-bld.tar.bz2}. \item Install cygcin from the tar file - this installs into home directory. Note this is cygcin \emph{not} cygwin. You must change the @@ -1050,7 +1048,7 @@ make install \item Download cinelerra-gg: \begin{lstlisting}[style=sh] cd /build_path/ -git clone https://git.cinelerra-gg.org/goodguy/cinelerra.git +git clone https://git.cinelerra-gg.org/goodguy/cinelerra.git cinelerra cd cinelerra/cinelerra-5.1 \end{lstlisting} \item Apply cygwin patch: @@ -1171,7 +1169,7 @@ is the build farm for \CGG{} deb and rpm packages that is maintained regularly at this location \url{https://github.com/einhander/cin-gg-packages/releases}. It will build packages on every git change in the main repo with releases corresponding to a build date, not a git commit date. -Current build hosts are \textbf{Debian 12}, \textbf{Debian 11}, +Current build hosts are \textbf{Debian 13},\textbf{Debian 12}, \textbf{Debian 11}, \textbf{Suse Leap 15.5}, \textbf{Fedora 38}, and \textbf{Ubuntu 22.04}. This build farm creates packages for the latest current versions of these distros with the potential for additional distros to be added in the future. diff --git a/parts/Introduction.tex b/parts/Introduction.tex index 9569047..c700ec8 100644 --- a/parts/Introduction.tex +++ b/parts/Introduction.tex @@ -151,7 +151,7 @@ programmers. \end{itemize} \end{description} -\paragraph{NOTE:} In \CGG{} the editing workflow is different from the workflow used by other NLEs. It is less intuitive and requires us to think first about what we want to achieve. In fact, it is a workflow based on the tracks in their entirety and not on individual clips. See \href{https://download.cinelerra-gg.org/download.php?file=\%2FWorkflow.pdf}{workflow is different!} for a comparison with the Adobe Premiere Pro workflow. +\paragraph{NOTE:} In \CGG{} the editing workflow is different from the workflow used by other NLEs. It is less intuitive and requires us to think first about what we want to achieve. In fact, it is a workflow based on the tracks in their entirety and not on individual clips. See \href{https://download.cinelerra-gg.org/download.php?file=\%2FWorkflow.pdf}{workflow is different!} for a comparison with the Adobe Premiere Pro workflow. \section*{Chapters Overview}% \label{sec:chapters_overview} diff --git a/parts/Licenses.tex b/parts/Licenses.tex index 09f9817..9eb85a9 100644 --- a/parts/Licenses.tex +++ b/parts/Licenses.tex @@ -21,7 +21,7 @@ License: GPLv2+ and CeCILL and BSD and CC-BY and Public Domain \CGG{} codebase is licensed GPLv2+ -See: {\small \url{https://www.gnu.org/licenses/old-licenses/gpl-2.0-standalone.html }} +See: {\small \url{https://www.gnu.org/licenses/old-licenses/gpl-2.0.html}} \vspace{2ex} \textbf{Creative Commons Attribution 4.0 International License} diff --git a/parts/Plugins.tex b/parts/Plugins.tex index 21d3c1f..6852da9 100644 --- a/parts/Plugins.tex +++ b/parts/Plugins.tex @@ -19,7 +19,7 @@ The plugins are shown and selected from the \textit{Resources window} (figure~\r There is a choice of plugin icons \index{plugins!icons} which can be displayed. -In \texttt{Settings$\rightarrow$ Preferences$\rightarrow$ Appearance} tab, there is a pulldown for \textit{Plugin icons} where the user can choose between the \textit{original} icons, \textit{regular} or \textit{smoother}, \textit{cinfinity}\protect\footnote{Cinfinity /2 icon set is credited to Sam - Creative Common By -- \url{https://creativhecommons.org/licenses/by/3.0/}} -- the default modernized set, or \textit{cinfinity2} (figure~\ref{fig:audio-plugins}). +In \texttt{Settings$\rightarrow$ Preferences$\rightarrow$ Appearance} tab, there is a pulldown for \textit{Plugin icons} where the user can choose between the \textit{original} icons, \textit{regular} or \textit{smoother}, \textit{cinfinity}\protect\footnote{Cinfinity /2 icon set is credited to Sam - Creative Common By -- \url{https://creativecommons.org/licenses/by/3.0/}} -- the default modernized set, or \textit{cinfinity2} (figure~\ref{fig:audio-plugins}). \begin{figure}[H] \centering @@ -389,8 +389,8 @@ NOTE: The capability to put the expanders.txt file in \texttt{./bcast5} (see \na For users running \CGG{} using the AppImage, to make an initial copy of expanders.txt, execute the following lines on /tmp: \begin{lstlisting}[numbers=none] - git clone --depth 1 git://git.cinelerra-gg.org/goodguy/cinelerra.git cinelerra5 - cp /tmp/cinelerra5/cinelerra-5.1/expanders.txt $HOME/.bcast5/expanders.txt + git clone --depth 1 https://git.cinelerra-gg.org/goodguy/cinelerra.git cinelerra + cp /tmp/cinelerra5/cinelerra-5.1/expanders.txt \$HOME/.bcast5/expanders.txt \end{lstlisting} \subsection{Speed-up of Ffmpeg plugin usage with OPTS files}% @@ -974,13 +974,13 @@ Automatically scale to a specified size. The Blend Algebra/Blend Program plugins provide the advanced feature of combining and modifying color pixels and transparencies of several tracks according to a mathematic algorithm written entirely by the user in the form of compact and simple piece of code. Such user defined algorithms (blend functions) are compiled, dynamically linked and immediately executed inside \CGG{} on the fly without the need to restart the application, reload the project, reattach plugins, and so on. -The following description is based on the \texttt{~/cinelerra-5.1/doc/README.blendalg} that accompanies the code by the author of both the code and the document. It is the authoriative documentation; the most detailed/original source and has additional commentary and programming information. If you encounter problems or confusion when using these plugins, always refer directly to that document \href{https://cinelerra-gg.org/download/testing/BlendPluginExamples/README.blendalg}{here}. If running \CGG{} from an \textit{AppImage}, testing has shown that it should work as well as if run from a build - just be aware of filename extensions that appear by default in the input field for the funtion name and change them accordingly. +The following description is based on the \texttt{~/cinelerra-5.1/doc/README.blendalg} that accompanies the code by the author of both the code and the document. It is the authoriative documentation; the most detailed/original source and has additional commentary and programming information. If you encounter problems or confusion when using these plugins, always refer directly to that document \href{https://download.cinelerra-gg.org/download.php?file=testing\%2FBlendPluginExamples/README.blendalg}{here}. If running \CGG{} from an \textit{AppImage}, testing has shown that it should work as well as if run from a build - just be aware of filename extensions that appear by default in the input field for the funtion name and change them accordingly. The idea behind these plugins\protect\footnote{credit to Georgy} is that the user can program sufficiently short and simple blending algorithms, called \textit{Functions}, by following detailed instructions with very little programming skills required. Blend Algebra and Blend Program come with a library of Functions (\textit{System Library}) that mimic the 30 overlay effects found in the Patchbay or Overlay plugins. The user can modify these Functions as needed or create new ones. To look at these example functions, there is an \texttt{Edit...} button in the respective plugin dialog. You will need a text editor to do so, which by default is \textit{emacs} if it is installed. If not, you can set your favorite editor via the corresponding environment variable in a terminal (\texttt{export CIN\_EDITOR='name editor'}) and then start \CGG{} from that same terminal. -If you can not wait to get started, checkout these examples \href{https://cinelerra-gg.org/download/testing/BlendPluginExamples/Examples.txt}{here}. You will also find test projects to \href{https://cinelerra-gg.org/download/testing/BlendPluginExamples}{download} to learn more about the plugins and to see the various ways they can be used to create your own functions. +If you can not wait to get started, checkout these examples \href{https://download.cinelerra-gg.org/download.php?file=testing\%2FBlendPluginExamples/Examples.txt}{here}. You will also find test projects to \href{https://download.cinelerra-gg.org/download.php?file=testing\%2FBlendPluginExamples}{download} to learn more about the plugins and to see the various ways they can be used to create your own functions. Both plugins, Blend Algebra and Blend Program, are similar. They are described together along with their differences. The main difference between the two plugins is that Blend Algebra is like a function; it combines its arguments (tracks) and yields the result which is placed into the single track configured for output. However, Blend Program does not produce a function result, but instead directly modifies its arguments. If more than one track is to be modified, Blend Program is the only choice. If a single track is to be processed, Blend Program is the best choice and might run slightly faster. Any Blend Algebra function can be rewritten to become a Blend Program function. But if a function processes several tracks and modifies only one, it will run faster in Blend Algebra which has more controls in its plugin dialog. @@ -1289,7 +1289,7 @@ In the distribution 30 Blend Algebra functions are provided for all the 30 \CGG{ \item Overlayer always clears its input frames. In Blend Algebra the user has a choice, either to clear them, or to leave them intact. \end{itemize} -There are several example functions from totally different areas of application: a user programmable plugin is a really universal tool and can be handy in unexpected cases. A programmer can sometimes make use of this plugin when creating new effects. It has the big advantage that you can more quickly test different combinations without spending time to restart \CGG{}, recompile it, reload project, and reattach plugins, etc. See the examples \href{https://cinelerra-gg.org/download/testing/BlendPluginExamples/Examples.txt}{here}. +There are several example functions from totally different areas of application: a user programmable plugin is a really universal tool and can be handy in unexpected cases. A programmer can sometimes make use of this plugin when creating new effects. It has the big advantage that you can more quickly test different combinations without spending time to restart \CGG{}, recompile it, reload project, and reattach plugins, etc. See the examples \href{https://download.cinelerra-gg.org/download.php?file=testing\%2FBlendPluginExamples/Examples.txt}{here}. There is the \texttt{ydiff.ba} function, actually representing the complete \textit{ydiff} application running inside a plugin. In addition, there is a Transition example, @@ -3361,8 +3361,7 @@ Plugin variables: \label{sub:svg_via_inkscape} \index{SVG via Inkscape} -This plugin allows the user to manipulate an SVG (scalable vector graphics) image with \textit{Inkscape} without having to leave the program. The associated \CGG{} window provides the ability to change the DPI, the Out $x/y$ coordinates, and the Out w/h values. For more information on use of inkscape, refer to: {\small \url{https://inkscape.org/develop/about-svg/}} - +This plugin allows the user to manipulate an SVG (scalable vector graphics) image with \textit{Inkscape} without having to leave the program. The associated \CGG{} window provides the ability to change the DPI, the Out $x/y$ coordinates, and the Out w/h values. For more information on use of inkscape, refer to: {\small \url{https://wiki.inkscape.org/wiki/Inkscape}} \begin{description} \item[DPI] is Dots per inch and it represents the resolution of the SVG image. Since the image is scaled with interpolation mode linear, the edges will look blurry when the input resolution is lower than the output resolution. You can either set the desired \textit{DPI value} in the window or use the tumbler on the integer text box, then use the \textit{update dpi} button to have the change take effect. Changing DPI causes the entire image to be re-exported via inkscape. DPI changes cause adjustments in the resolution, speed of re-import, and storage needed for the image data. \item[Out\_x/Out\_y] allow for changing the location of the SVG via the $x$ or $y$ coordinates. @@ -4298,12 +4297,12 @@ cin/plugins/opencv/stylizeobj.plugin \begin{enumerate} \item do your package install of the current build for your distro as usual - \item look in {\small \url{https://cinelerra-gg.org/download/tars}} to see your distro name's static tar + \item look in {\small \url{https://download.cinelerra-gg.org/?path=\%2Ftars}} to see your distro name's static tar \item download the corresponding distro static tarball; for example for arch: \end{enumerate} - {\small \url{https://cinelerra-gg.org/download/tars/cinelerra-5.1-arch-{date}-x86_64-static.txz}} + {\small \url{https://download.cinelerra-gg.org/download.php?file=tars\%2Fcinelerra-5.1-arch-20201031.x86_64-static.txz}} \begin{enumerate}[resume] \item create a temporary directory on your computer @@ -4345,9 +4344,9 @@ that is considered to be more stable. A build using the tarball requires that y system have \textit{wget} already installed to initially download the prepared source tar. There are currently 2 tarballs of stable versions on the website used for user builds. The 20180401 version:\newline -{\small \url{ https://cinelerra-gg.org/download/opencv/opencv-20180401.tgz}}\newline +{\small \url{https://download.cinelerra-gg.org/download.php?file=opencv\%2Fopencv-20180401.tgz}}\newline works with older version of cmake, and 20200308 is the current 4.2 release:\newline -{\small \url{https://cinelerra-gg.org/download/opencv/opencv-20200306.tgz}} +{\small \url{https://download.cinelerra-gg.org/download.php?file=opencv\%2Fopencv-20200306.tgz}} To build using the tarballs on the website, use this bld.sh procedure (you may want to run "make clean" first): @@ -4355,7 +4354,7 @@ clean" first): #!/bin/bash ( ./autogen.sh ./configure --with-single-user --with-booby \ - --with-opencv=sta,tar=http://cinelerra-gg.org/download/opencv/opencv-20200306.tgz + --with-opencv=sta,tar=https://download.cinelerra-gg.org/download.php?file=opencv\%2Fopencv-20200306.tgz make && make install ) 2>&1 | tee log mv Makefile Makefile.cfg cp Makefile.devel Makefile @@ -4367,13 +4366,12 @@ cp Makefile.devel Makefile To build findobject and the other plugins using OpenCV, access the src using git: \begin{lstlisting}[style=sh] -git clone --depth 1 git://git.cinelerra-gg.org/goodguy/cinelerra.git cinelerra5 +git clone --depth 1 https://git.cinelerra-gg.org/goodguy/cinelerra.git cinelerra \end{lstlisting} To use the latest version, the method for creating a tarball is: - \begin{enumerate} - \item download both opencv and opencv\_contrib source tarballs from the web: - {\small \url{https://sourceforge.net/projects/opencvlibrary/files/4.2.0/}} + \item download both opencv and opencv\_contrib source tarballs from the web:\newline + {\small \url{https://sourceforge.net/projects/opencvlibrary/files/4.2.0/}}\newline {\small \url{https://github.com/opencv/opencv\_contrib/archive/4.2.0.tar.gz}} \item create a temporary directory opencv\_src and unpack the tarballs into the src directory \item rename these sources to opencv and opencv\_contrib @@ -4381,20 +4379,20 @@ To use the latest version, the method for creating a tarball is: \end{enumerate} \begin{lstlisting}[style=sh] -cd opencv\_src +cd opencv_src mkdir build cd build && cmake \ - -DCMAKE\_BUILD\_TYPE=RELEASE \ - -DWITH\_IPP=OFF \ - -DWITH\_LAPACK=OFF \ - -DWITH\_GPHOTO2=OFF \ - -DBUILD\_SHARED\_LIBS=ON \ - -DINSTALL\_C\_EXAMPLES=ON \ - -DINSTALL\_PYTHON\_EXAMPLES=ON \ - -DBUILD\_EXAMPLES=ON .. \ - -DBUILD\_opencv\_python3=no \ - -DCMAKE\_INSTALL\_PREFIX=/usr/local \ - -DOPENCV\_EXTRA\_MODULES\_PATH="\$(opencv)\_contrib/modules/" + -DCMAKE_BUILD_TYPE=RELEASE \ + -DWITH_IPP=OFF \ + -DWITH_LAPACK=OFF \ + -DWITH_GPHOTO2=OFF \ + -DBUILD_SHARED_LIBS=ON \ + -DINSTALL_C_EXAMPLES=ON \ + -DINSTALL_PYTHON_EXAMPLES=ON \ + -DBUILD_EXAMPLES=ON .. \ + -DBUILD_opencv\_python3=no \ + -DCMAKE_INSTALL_PREFIX=/usr/local \ + -DOPENCV_EXTRA_MODULES_PATH="\$(opencv)_contrib/modules/" \end{lstlisting} Next configure the build, but add the \texttt{-{}-with-opencv} configure parameter. An example diff --git a/parts/Quickstart.tex b/parts/Quickstart.tex index b6ccf66..94930e9 100644 --- a/parts/Quickstart.tex +++ b/parts/Quickstart.tex @@ -380,9 +380,8 @@ We thus obtain a list of all frames in the analyzed media and their type. For ex \end{lstlisting} There are also 2 useful scripts that not only show the keyframe type but also show the GOP length of the media. They are zipped tars with readme's at: \newline -{\small\url{https://cinelerra-gg.org/download/testing/getgop_byDanDennedy.tar.gz}} \newline -{\small\url{https://cinelerra-gg.org/download/testing/iframe-probe_byUseSparingly.tar.gz}} - +{\small\url{https://download.cinelerra-gg.org/download.php?file=testing\%2Fgetgop_byDanDennedy.tar.gz}} AND \newline +{\small\url{https://download.cinelerra-gg.org/download.php?file=testing\%2Fiframe-probe_byUseSparingly.tar.gz}} We can now look at the timeline of \CGG{} to see the frames that give problems in playback. Using a codec of type Long GOP, it is probably the rare I-frames that give the freezes. To find a solution you can use MKVToolNix ({\small\url{https://mkvtoolnix.download/}}) to correct and insert new keyframes into the mkv file (matroska talks about \textit{cues data}). It can be done even without new encoding. Or you can use the \texttt{Transcode} tool within \CGG{} because during transcoding new keyframes are created that should correct errors. diff --git a/parts/Real-World.tex b/parts/Real-World.tex index 9c8cb77..bfe519f 100644 --- a/parts/Real-World.tex +++ b/parts/Real-World.tex @@ -178,11 +178,10 @@ Let's take the case of a professional magician filmed in multicam while performi You can find the files to test the workflow that is described next at the following address: %begin{latexonly} -\url{https://cinelerra-gg.org/download/testing/cinelerra-Manual-reference.zip} +\url{https://download.cinelerra-gg.org/download.php?file=testing\%2Fcinelerra-Manual-reference.zip} %end{latexonly} \begin{htmlonly} -\url{https://cinelerra-gg.org/download/testing/cinelerra-forum.zip} - +\url{https://download.cinelerra-gg.org/download.php?file=testing\%2Fcinelerra-forum.zip} \end{htmlonly} [Media files are licensed under a \href{https://creativecommons.org/licenses/by-nc-sa/4.0/legalcode}{CC 4.0 BY, NC, SA license}.] @@ -339,8 +338,6 @@ For historical reasons, almost every piece of video software uses \textit{limite However, this is not an option for you if you're either a perfectionist or trying to fight color banding. Color banding is a video artifact that could be visible in smooth areas of the video. -Here's an example: {\small \url{https://youtu.be/KL8CIZej19o}} - If you don't see the ugly background, then you don't need to worry about the whole issue. Color banding is different from compression artifacts. You can't fix it just by increasing the bitrate of your video. Color banding comes from color correction performed too much or in inaccurate way. And it accumulates, so if you have it, then you should get rid of dynamic range compression every step of the way. \CGG{} has a native full color range support, and you can enable it via: diff --git a/parts/Rendering.tex b/parts/Rendering.tex index 136efcc..acbd813 100644 --- a/parts/Rendering.tex +++ b/parts/Rendering.tex @@ -238,7 +238,7 @@ More information on all these options can be found at \href{https://ffmpeg.org/ffmpeg-all.html#Format-Options}{ffmpeg.org} sections 19 and 21. See also \nameref{sub:modifying_ffmpeg_cinelerra}. -Render presets in \CGG{} should work Out Of the Box. You can still configure the \textit{Global Options} and \textit{Private Options} manually. Finding the combination of parameters that best suits your needs, or simply finding working (\textit{legal}) combinations, requires studying each codec in depth. You can start by looking in Wikipedia until you get to download and study the \textit{white papers} of the codecs of interest. In any case, you must then start a long experimental phase, trying presets with different configurations or creating new ones, until you get satisfactory results. If you create new presets it is a good idea to make them known on the mailing list ({\small \url{https://lists.cinelerra-gg.org/mailman/listinfo/cin}}) or on the MantisBT Bug Tracker ({\small \url{https://www.cinelerra-gg.org/bugtracker/my_view_page.php}}) so that they can be integrated into subsequent versions of \CGG{}. For an introduction see \nameref{sec:overview_formats}. +Render presets in \CGG{} should work Out Of the Box. You can still configure the \textit{Global Options} and \textit{Private Options} manually. Finding the combination of parameters that best suits your needs, or simply finding working (\textit{legal}) combinations, requires studying each codec in depth. You can start by looking in Wikipedia until you get to download and study the \textit{white papers} of the codecs of interest. In any case, you must then start a long experimental phase, trying presets with different configurations or creating new ones, until you get satisfactory results. If you create new presets it is a good idea to make them known on the mailing list ({\small \url{https://lists.cinelerra-gg.org/mailman/listinfo/cin}}) or on the MantisBT Bug Tracker ({\small \url{https://bug.cinelerra-gg.org/my_view_page.php}}) so that they can be integrated into subsequent versions of \CGG{}. For an introduction see \nameref{sec:overview_formats}. \section{Some Specific Rendering}% \label{sec:some_specific_rendering} diff --git a/parts/Transition.tex b/parts/Transition.tex index 7efb1b1..b1b8fff 100644 --- a/parts/Transition.tex +++ b/parts/Transition.tex @@ -154,9 +154,9 @@ at {\small \url{http://assistcg.com}} - click on the \textit{Transitions} option To include new images in the Shape Wipe Transition, simply copy the file \textit{shape.jpg} or \textit{shape.png} to the subdirectory \texttt{plugins/shapes} in your \CGG{} directory path. If you prefer to have a better quality png used instead of the included 90\% jpg version, you can download -the equivalent png versions at {\small \url{https://cinelerra-gg.org/download/testing/ShapeWipe\_pngs.txz}}. +the equivalent png versions at {\small \url{https://download.cinelerra-gg.org/download.php?file=testing\%2FShapeWipe\_pngs.txz}}. You will then need to untar this file, choose the ones you want, and add them to your directory path. -And if that is not enough, you can download another 32 different transitions at {\small \url{https://cinelerra-gg.org/download/testing/ShapeWipe\_additional.txz}}. One particularly interesting ShapeWipe +And if that is not enough, you can download another 32 different transitions at {\small \url{https://download.cinelerra-gg.org/download.php?file=testing\%2FShapeWipe\_additional.txz}}. One particularly interesting ShapeWipe in this set is \textit{Fleur-de-lis-of-Florence}. After an update of \CGG{}, they will have to be restored each time. \subsection*{Slide}% diff --git a/parts/Trouble.tex b/parts/Trouble.tex index d9e3de7..552c364 100644 --- a/parts/Trouble.tex +++ b/parts/Trouble.tex @@ -9,9 +9,7 @@ To help new users, a pdf has been created comparing the editing workflow of \CGG \CGG{} is a complex and feature-rich program. Using a guide is indispensable. The official manual (in English) can be found in PDF and HTML format: -\url{https://cinelerra-gg.org/download/CinelerraGG_Manual.pdf} - -\url{https://cinelerra-gg.org/download/CinelerraGG_Manual/} +\url{https://download.cinelerra-gg.org/download.php?file=\%2FCinelerraGG_Manual.pdf}\newline From within the program, you can invoke \textit{Context Help}, which references sections of the HTML manual\protect\footnote{credit Georgy(sge) for full implementation}. @@ -234,8 +232,8 @@ possible that your LV2 plugin path may have been modified and be in disagreement for \CGG{}. This could result in a crash upon startup. Look at the messages in the window from where you started \CGG{} to see if they look similiar to the following: \begin{lstlisting}[numbers=none,xleftmargin=10mm] -LOAD: http://eq10q.sourceforge.net/matrix\_lr2ms -LOAD: http://eq10q.sourceforge.net/matrix\_ms2lr +LOAD: http://eq10q.sourceforge.net/matrix_lr2ms +LOAD: http://eq10q.sourceforge.net/matrix_ms2lr LOAD: https://community.ardour.org/node/7596 LOAD: urna-comp ** segv at 0x7f2cd80813c4 in pid 4540, tid 4540 diff --git a/parts/Windows.tex b/parts/Windows.tex index 6292ed9..30b244f 100644 --- a/parts/Windows.tex +++ b/parts/Windows.tex @@ -899,7 +899,7 @@ from which: $H = 816$ pixels At the same time as changing the \textit{Height} parameter we also need to set \texttt{Display Aspect rati}o to 2.35. In fact, the parameters in Canvas Size are not related to those in Display Aspect ratio, unless we keep the \texttt{Auto} option checked, and we need to set both before we click on the \texttt{Apply} button. To set the aspect ratio to 2.35:1 we can choose from the drop-down menu the value 2.35 or set the value directly in the two input fields. Or again, it can be done automatically via the Auto option. Finally we can click on the Apply button to complete the calculations. Now we have arrived at the desired result: typical Super 35 mm dimensions and aspect ratio, although starting from a 16:9 FullHD. The new canvas, however, lost the pixels of a part of the initial video (crop), to be precise $1080 - 816 = 264$ lines of pixels from top and bottom. \CGG{} allows you to vary the input and output aspect ratio in the ways indicated in the previous section: by varying the pixels of the sides (Width/Height) or by setting a multiplication coefficient (W/H Ratio; in this example: placing $H Ratio = 816 : 1080 = 0.7556$) which performs the calculation automatically. If you set \textit{W Ratio} and \textit{H Ratio} at the same time with the same values, they work as multipliers and you get a resizing of the canvas, without altering the initial aspect ratio. If you change them to two different values or change only one of the two parameters, leaving the other at 1, you get an anamorphic video, with the pixels no longer being square (1:1) but becoming rectangular, deforming the image. If you use a non-standard aspect ratio, this has impact on other areas like titles, included stills and included non-anamorphic footage. To avoid anamorphosis, the \texttt{Display Aspect ratio} must also be adjusted at the same time, for example, with the Auto option. \textit{Anamorphic} format is a complex field that is discussed -in Andrea's paper: {\small \url{https://cinelerra-gg.org/download/Anamorphic.pdf}}. +in Andrea's paper: {\small \url{https://download.cinelerra-gg.org/download.php?file=\%2FAnamorphic.pdf}}. as well as in the Raffaella Traniello's guide: {\small \url{http://www.g-raffa.eu/Cinelerra/HOWTO/anamorphic.html}}. \subsection{Camera and Projector}% -- 2.34.1