From 8a5787886b95940e92bc3999ab56c7a88c248eae Mon Sep 17 00:00:00 2001 From: Good Guy Date: Tue, 19 Sep 2023 19:03:32 -0600 Subject: [PATCH] updates to add link to Workflow.pdf + --- parts/Developer.tex | 8 -------- parts/Faq.tex | 2 +- parts/Introduction.tex | 2 ++ parts/Trouble.tex | 4 +++- parts/Windows.tex | 3 --- 5 files changed, 6 insertions(+), 13 deletions(-) diff --git a/parts/Developer.tex b/parts/Developer.tex index 4abbf25..84b9796 100644 --- a/parts/Developer.tex +++ b/parts/Developer.tex @@ -405,14 +405,6 @@ compile; and use binaries that you do not know what they contain since no source Look into opencv4/opencv2/core/types.hpp:711;27 \end{description} -\textbf{webp} -\begin{description}[noitemsep] - \item Status - currently at version 1.1.0 - \item Problem - requires cmake 3.5 - \item Workaround already in use by \CGG{} - leaving out of Ubuntu14, Ubuntu, Centos7 - \item Your workaround - upgrade on those systems to cmake 3.5 -\end{description} - \textbf{libaom} \begin{description}[noitemsep] \item Status - currently at version 3.0.0 for older O/S and 3.1.1 for newer O/S diff --git a/parts/Faq.tex b/parts/Faq.tex index b4b1f05..d29b42d 100644 --- a/parts/Faq.tex +++ b/parts/Faq.tex @@ -2,7 +2,7 @@ \label{cha:faq_problems_workarounds} \index{workarounds} -Some workarounds for issues and a few known problems that have not yet been fixed, are described here. +Some workarounds for issues and a few known problems that have not yet been fixed, are described here. More workarounds can be found \href{https://cinelerra-gg.org/download/Workflow.pdf}{here}. \paragraph{Workaround for access to modifiable text files when using AppImage.} This includes such files as FFmpeg video or audio files, fonts that you want to add for usage in the Title diff --git a/parts/Introduction.tex b/parts/Introduction.tex index eb36c0a..d70ec71 100644 --- a/parts/Introduction.tex +++ b/parts/Introduction.tex @@ -143,6 +143,8 @@ 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://cinelerra-gg.org/download/Workflow.pdf}{workflow is different!} for a comparison with the Adobe Premiere Pro workflow. + \section*{Chapters Overview}% \label{sec:chapters_overview} diff --git a/parts/Trouble.tex b/parts/Trouble.tex index dce311c..810ab73 100644 --- a/parts/Trouble.tex +++ b/parts/Trouble.tex @@ -1,6 +1,8 @@ \chapter{Troubleshooting and Help}% \label{cha:troubleshooting_help} +To help new users, a pdf has been created comparing the editing workflow of \CGG{} with the more usual editing workflow of Adobe Premiere Pro. See \href{https://cinelerra-gg.org/download/Workflow.pdf}{here}. + \section{Help and Context Help}% \label{sec:help_context_help} \index{context help} @@ -16,7 +18,7 @@ From within the program, you can invoke \textit{Context Help}, which references Context help can be requested from almost any \CGG{} window or subwindow by pointing with the mouse cursor on the GUI element of interest and pressing \texttt{Alt/h}. That HTML manual page will be shown via the configured web browser, which is assumed as most relevant to the GUI element currently under the mouse pointer. \subsection{How Context Help works}% -\label{sub:how_it_works} +\label{sub:how_context_help_works} The hotkey to request context help is \texttt{Alt/h}. What particular help page is shown, depends on the mouse cursor location while \texttt{Alt/h} is pressed. Usually, when the mouse is located in some window or dialog, the help page related to the functionality of this window or dialog is shown. In this case the mouse can point either on some widget, or on an empty area in the window. In \CGG{} GUI there are several rich loaded windows, \textit{Timeline} and \textit{Compositor} for example. In such a case different help pages can be requested depending on the particular GUI element under the mouse. For example, pressing \texttt{Alt/h} while pointing on the \textit{Autos curve} in a track would show help on \textit{automation keyframes} section, pointing on the \textit{Overlay} mode button in the \textit{patchbay} would show help on \textit{overlays}, pointing on the \textit{camera control} in \textit{Compositor} would show help on \textit{camera and projector}. diff --git a/parts/Windows.tex b/parts/Windows.tex index 546a555..a500bc0 100644 --- a/parts/Windows.tex +++ b/parts/Windows.tex @@ -487,9 +487,6 @@ and waveforms with transluent colors. The pink media file has been self-colored The main window pulldowns as pointed out in figure~\ref{fig:insertion-points} are quite obvious in their meaning and usage, so here is only a summary. -%TODO Figure 3 shows an example of the pulldowns as displayed in the main window.Appearance - - \begin{description} \item[File] \index{file} options for loading, saving, and rendering as described in other sections (\ref{cha:load_save_and_the_EDL}). \item[Edit] \index{edit} edit functions; most of which have shortcuts that you will quickly learn (\ref{cha:editing}). -- 2.26.2