Hi, Here some samples for several figures, choose that you want. % two figures and one caption \begin{figure}[h] \begin{minipage}[h]{0.49\linewidth} \center{\includegraphics[width=0.5\linewidth]{image} \\ а)} \end{minipage} \hfill \begin{minipage}[h]{0.49\linewidth} \center{\includegraphics[width=0.5\linewidth]{image} \\ б)} \end{minipage} \caption{Corellation.} \label{ris:image1} \end{figure} %four \begin{figure}[H] \begin{minipage}[h]{0.47\linewidth} \center{\includegraphics[width=1\linewidth]{image}} a) \\ \end{minipage} \hfill \begin{minipage}[h]{0.47\linewidth} \center{\includegraphics[width=1\linewidth]{image}} \\b) \end{minipage} \vfill \begin{minipage}[h]{0.47\linewidth} \center{\includegraphics[width=1\linewidth]{image}} c) \\ \end{minipage} \hfill \begin{minipage}[h]{0.47\linewidth} \center{\includegraphics[width=1\linewidth]{image}} d) \\ \end{minipage} \caption{Correlation signal peaks: a) numerical experiment, b) registered correlation signals, c) intensity distribution of correlation signals in numerical experiment, d) correlation signals intensity distribution for DCRAW processed data.} \label{ris:experimentalcorrelationsignals} \end{figure} % Two figures with separate caption \begin{figure}[h] \begin{center} \begin{minipage}[t]{0.4\linewidth} \includegraphics[width=1\linewidth]{image} \caption{Исходное изображение.} %% подпись к рисунку \label{ris:experimoriginal} %% метка рисунка для ссылки на него \end{minipage} \hfill \begin{minipage}[t]{0.4\linewidth} \includegraphics[width=1\linewidth]{image} \caption{Закодированное изображение.} \label{ris:experimcoded} \end{minipage} \end{center} \end{figure} % three with subfigure % add below into preamble \usepackage{subfigure} \begin{figure}[ht!] \vspace{-4ex} \centering \subfigure[]{ \includegraphics[width=0.25\linewidth]{actuatorscouplingSheme_decoupledcase.eps} \label{fig:actuatorscouplingSheme_decoupledcase} } \hspace{4ex} \subfigure[]{ \includegraphics[width=0.25\linewidth]{actuatorscouplingSheme_nearestcoupledcase.eps} \label{fig:actuatorscouplingSheme_nearestcoupledcase} } \hspace{4ex} \subfigure[]{ \includegraphics[width=0.24\linewidth]{actuatorscouplingSheme_nearestcoupled_and_diag_case.eps} \label{fig:actuatorscouplingSheme_nearestcoupled_and_diag_case} } \caption{Coupling cases for the DM models: \subref{fig:actuatorscouplingSheme_decoupledcase} decoupled case; \subref{fig:actuatorscouplingSheme_nearestcoupledcase} coupling between the closest neighbours; \subref{fig:actuatorscouplingSheme_nearestcoupled_and_diag_case} coupling between the closest neighbour and diagonally adjacent actuators.} \label{fig:threeDMcases} \end{figure} Thu, Jul 18, 2019 at 10:39:26AM +0200, Andrea paz написал:

Added chapter 10 (only 4 pages). I was thinking of using "subcaption" to create grids of images each with its own caption. What do you think? Actually, I tried to put it on, but it doesn't work for me. -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin

-- С уважением, к.т.н., доц. каф. ТЛХП, ХД и ФХ СПбГЛТУ Спицын Андрей Александрович +79500166982

Hi Andrea, It's a default behavior of TeXstudio. Glossary creation is separate process. It can be included in main compilation routine, or may not. In my TeXstudio setup I use separate command for glossary creation. To do so, go to Options-> Configure TeXstudio -> Commands. Change Makeindex command to: makeindex %.nlo -s nomencl.ist -o %.nls Click Ok and go to Tools -> Commands -> Makeindex. Hit F5 to recompile. The Glossary should be updated. Mon, Aug 19, 2019 at 09:48:32AM +0200, Andrea paz написал:

Hi Andrey, I wanted to add some entries in the glossary but it's not possible. I write the new entry but then when I create the updated pdf (F5) it does not appear. No errors are reported, simply the new entry is ignored. With the other chapters of the manual, everything is OK. Is that just my problem? -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin

-- С уважением, к.т.н., доц. каф. ТЛХП, ХД и ФХ СПбГЛТУ Спицын Андрей Александрович +79500166982

Hi Andrea, About chapter ten and eleven numbering. To fix the issue we need to change right border of page or choose a different chapter style. In any case we should to double-check all pages because printable area decreases. I prefer to change right border from 2cm to 3 cm. It can be done in file common/settings.tex line 5 from \geometry{right=2.0cm} to \geometry{right=3.0cm} If you want to change chapter style go to line 31 and change \chapterstyle{madsen} to something else. Some chapter styles are shown in http://mirrors.ctan.org/info/latex-samples/MemoirChapStyles/MemoirChapStyles... Best regards, Andrey пн, 19 авг. 2019 г. в 14:33, Andrea paz <[email protected]>:

It works perfectly; thank you very much. -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin

Hi Igor, Please export them as a vector PDF images. Latex can handle pdf with ease. It's also decrease whole file size. ср, 25 сент. 2019 г., 15:56 Igor BEGHETTO <[email protected]>:

Hi! @Phyllis and @Andea_paz About Pipeline images for the manual I have done that, if you want. Two PNGs added. They are made with Inkscape and esported to PNG @300dpi (dot per inch) for printing. If someone has already drawn them, feel free to put my PNGs in the trash. =) Thanks

IgorBeg -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin

Hi Andrey! Okay. I thought You wanted the PNGs file for the illustrations. Here the PDFs. @Phyllis Thanks!

Andrey wrote:

But if you create a vector image it's best to export it as vector PDF file. I agree with you. I don't know nothing about LatTex and I thought that LaTex was not able to digest the pdf format. Sorry. Thanks!

- I had to force the pdf because they are present in ".gitignore". Did You have done absolutely right to force pdf images. Add following line to .gitignore to allow pdf in images folder.

!/images/*.pdf

I take this opportunity to clarify how I insert the images: I use 144 Dpi PNG because, in my opinion, they are the minimum acceptable quality. By minimum quality I mean: being able to easily read the smallest text on the screen. If we make a version for printing we will have to replace all the images. I propose to postpone this work until I'm think its fine for now. You can add a high dpi version of images in separate folder, for ex. ./imagesHQ/ In settings file we can switch folders used for a manual compilation. There is a many methods in latex to do it almost automatically.

Thu, Sep 26, 2019 at 08:10:22PM +0200, Andrea paz написал:

- Changed \geometry(right=3.0cm). Thanks, Andrey. - I have inserted Igor's beautiful pdf in manual_latex. (Usual address: https://www.dropbox.com/s/0js49r47s0qu621/CinelerraGG_Manual.pdf?dl=0) - I had to force the pdf because they are present in ".gitignore". Did I do wrong?

I take this opportunity to clarify how I insert the images: I use 144 Dpi PNG because, in my opinion, they are the minimum acceptable quality. By minimum quality I mean: being able to easily read the smallest text on the screen. If we make a version for printing we will have to replace all the images. I propose to postpone this work until after the completion of the manual. What do you think? I'm fine with any solution. And, as always, the last word is up to Phyllis. -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin

Andrea, I saw the Manual with the new illustrations but the "compositing_pipeline-masks.pdf" is in the wrong place, I think. Take a look at the Cinelerra-CV_manual, please; also for the good images in Masks chapter. Probably You (all) already have it; however I put here the link to the Cinelerra_CV_manual (temporarily), if it can help. http://www.visi1.org/temp/cinelerra_cv_manual_en.pdf Thanks for your work! IgorBeg

Hi Andrea, I put references to corresponding chapters and done a quick fix for the lines that goes beyond right page border. All changes already in my repo. -- Best regards Fri, Sep 27, 2019 at 04:26:33PM +0200, Andrea paz написал:

About compositing_pipeline_masks you're completely right. I put it in its place (mask section) and apologize (same dropbox link). As for the section on the mask tool, I think it needs to be rewritten to incorporate the latest news. Phyllis, could you get me the odt? -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin

I forgot: I added the section on VHS capture at the end of chapter 12.

I'm sorry, my fault. It' ok now.

Thanks, I merged your commits into my repo. вт, 8 окт. 2019 г., 15:33 Andrea paz <[email protected]>:

I'm sorry, my fault. It' ok now. -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin

In the manual; in chapter 14 ("the 5 multi-s"; section "14.5 multi session"), you can say that, by starting multiple sessions of CinGG, you can assign to each one its own .bcast through: Settings --> Preferences --> Interface --> Index files --> index files go here: ?

Hi people, I am a lurker in this ml, I am sorry, I also am not really a cinelerra user but I do like _very much_ the project, the spirit, the people. To cut through the chase I want to contribute somehow with a suggestion. Here is my 2 cents: I see you talk about Latex because you seem to use it as a doc tool for cinelerra. I am sorry but I do not think that Latex is really a good language to write docs apart from math books. I mean that now there are better laguages that permits to write docs in an easier way. An easier way means also that you can attract more contributions, make more powerful conversions, manage translations in a more easier/more manageable way ... and so on. What am I talking about? I am talking about lightweight markup languages https://en.wikipedia.org/wiki/Lightweight_markup_language I am sure you know already at least a couple of them. One of my favourite is asciidoc. https://en.wikipedia.org/wiki/AsciiDoc https://asciidoctor.org/docs/what-is-asciidoc/ For many reasons I think Asciidoc is the best markup language for docs. It is easy. It is readable. It is complete. It is standard (it in an advanced stardardization stage). It is implemented in many languages, currently python, ruby, javascript and java. The ruby version through the asciidoctor compiler being the most advanced and most actively developed and the python version still the most used... Example of users of asciidoc are: - github, which uses asciidoctor to render in real time docs committed to its git repos - the git manual, the kicad manual (which I am partly responsible for) and many, many others, see: Who's Using Asciidoctor? https://github.com/asciidoctor/asciidoctor.org/issues/270 Through the po4a tool it is easy to create, and most importantly manage, automatically updated multilanguage versions of the docs. See for example: (on the upper right side of the page you can switch the docs language...) http://docs.kicad-pcb.org/ Let me know if you want to know more about it... -- Best regards, Marco Ciampa I know a joke about UDP, but you might not get it. ------------------------ GNU/Linux User #78271 FSFE fellow #364 ------------------------

On Thu, Oct 10, 2019 at 02:55:48PM +0200, Andrea paz wrote:

@Marco

Thanks for your prompt reply,

...

For many reasons I think Asciidoc is the best markup language for docs. My compliments: the page of the KiCAD guides is really nice and convenient to use. Who knows if in the future we can do something similar. For now, we are stopping at a simple collection of pdfs (but we are now close to the end of the manual in LaTeX).

Right, lets first finish what you have. If you are close to finish it, that is the most sensible thing to do. For the future, I'm here.

I'll try to say my opinion. The use of LaTeX is mainly due to two factors: 1- Power of this language: Easy transposition from the originals (in .odt);

Guess in which format were the kicad original manuals? ;-)

easy incorporation of user additions and corrections without involving the global structure;

same as but easier in asciidoc

total control over the final result (about 600 pages full of images, tables and lists); being able to get a nice PDF.

same as but easier in asciidoc

2- We are few and no one has proposed to use asciidoc. Instead Andrey proposed himself for Latex, and his knowledge of the language is so deep that he managed to explain it easily even to an ignorant person like me. :-).

good point but ... with asciidoc there is almost no knowledge in writing the contents, so you don't have to ask the latex guru to make index, tables or so. If you look at the format it is almost like as writing this email. Yes it is that easy. Anyway when I have some spare time I can try to convert all 600 pages of docs in asciidoc to see how it comes out... PS: where are the doc sources? With the program sources I do not see anything like in /doc, perhaps in another repo? -- Best regards, Marco Ciampa I know a joke about UDP, but you might not get it. ------------------------ GNU/Linux User #78271 FSFE fellow #364 ------------------------

Hi Marco, We have a discussion about markdown, and other markup languages in bugtracker https://www.cinelerra-gg.org/bugtracker/view.php?id=77 Asciidoc, markdown and other Lightweight markup language(LML) has advantages and disadvantages. The advantages you already mentioned is convertibility into html and into other formats. Syntax IMHO is a mater of taste. The disadvantages of LML is a continuation of it advantages, LML has a lack of control of output format. To produce a good pdf from Asciidoc, you have to fine tune the standard latex template and entire document, because Asciidoc and other LMLs use latex to convert into pdf. No Tikz drawing support. Sometime a conversion goes wrong, see attached file. And so on. LMLs produce a much simpler documents even with a latex support. LaTeX has much more power to do with pdf format, and because of that produce nice looking pdfs, that looks like a real book. And it's goes closer to some kind of art, see https://github.com/jemmybutton/byrne-euclid

Anyway when I have some spare time I can try to convert all 600 pages of docs in asciidoc to see how it comes out...

I don't know can I speak for a whole community, but we are welcome any help. It would be nice to have ability to convert latex manual into asciidoc. Best regards, Andrey

On Thu, Oct 10, 2019 at 10:49:05PM +0300, Спицын Андрей wrote:

Hi Marco,

We have a discussion about markdown, and other markup languages in bugtracker https://www.cinelerra-gg.org/bugtracker/view.php?id=77

Markdown is a nightmare of dialects...

Asciidoc, markdown and other Lightweight markup language(LML) has advantages and disadvantages. The advantages you already mentioned is convertibility into html and into other formats. Syntax IMHO is a mater of taste. The disadvantages of LML is a continuation of it advantages, LML has a lack of control of output format. To produce a good pdf from Asciidoc, you have to fine tune the standard latex template and entire document,

This is past. Asciidoctor-pdf produces beautiful pdf from scratch. No need to convert into docbook or latex anymore.

because Asciidoc and other LMLs use latex to convert into pdf. No Tikz drawing support. Sometime a conversion goes wrong, see attached file. And so on. LMLs produce a much simpler documents even with a latex support.

LaTeX has much more power to do with pdf format, and because of that produce nice looking pdfs, that looks like a real book. And it's goes closer to some kind of art, see https://github.com/jemmybutton/byrne-euclid

As already said, this is good for math books, and perhaps even for math book it is not compulsory since now you can just insert a small latex code into asciidoc when you need to render a formula...

...

Anyway when I have some spare time I can try to convert all 600 pages of docs in asciidoc to see how it comes out...

I don't know can I speak for a whole community, but we are welcome any help. It would be nice to have ability to convert latex manual into asciidoc.

Well, lets discuss this when (and _if_) I succeed in doing that! -- Best regards, Marco Ciampa I know a joke about UDP, but you might not get it. ------------------------ GNU/Linux User #78271 FSFE fellow #364 ------------------------

Hi Andrea, The table is OK for me too. Please continue that you are doing.

When I have finished entering the data I will provide the sample pdf, so that everyone can give suggestions to improve the aesthetics. You are right we can add some aesthetics later.

вс, 27 окт. 2019 г. в 12:38, Andrea paz <[email protected]>:

Hi, Andrey. I continued to study the tables and in the end I came to a simplified version but that satisfies me. I would like your opinion and suggestions. I have privileged the practical side of reading over the aesthetics. When I have finished entering the data I will provide the sample pdf, so that everyone can give suggestions to improve the aesthetics. For now I leave this scheme if it suits you.

\begin{center} \small \begin{longtable}{ >{\bfseries}c l l p{6cm}} %\caption{Main menu pulldowns} %\label{tabular:main_menu} \\ \toprule \multirow{2}*{MAIN} & 01/19/2019 & update & \\ \noalign{\smallskip} \cline{2-4} \noalign{\smallskip} (Pulldowns) & ITEMS & SHORTCUTS & DESCRIPTION\\ \hline \hline \endhead % here the common page header

File & xxxxx1 & yyyyyy1 & zzzzz1 \\ \midrule & xxxxx2 & yyyyyy2 & zzzzz2 \\ \midrule & xxxxx3 & yyyyyy3 & zzzzz3 \\

\bottomrule

\end{longtable} \end{center} -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin

Andrea, The table looks really good! Later today, gg will replace the current CinelerraGG_manual_WIP.pdf on the website with your latest. You are getting really close to full LaTex conversion -- I can hardly wait to get my hands on it. Thanks, gg/Phyllis On Tue, Oct 29, 2019 at 8:54 AM Andrea paz <[email protected]> wrote:

Added chapter 15 with large shortcut tables. @Andrey: If I put caption and labels to the tables I get an error that I do not understand and I do not compile the pdf. @All If you have any suggestions for improving the tables please let me know. For a preview of the pdf: https://www.dropbox.com/s/0js49r47s0qu621/CinelerraGG_Manual.pdf?dl=0 -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin

Hi, Andrey. Olaf has proposed changes to the structure of the Latex manual. Since he is not a member of the mailing list, I enclose his attachments here too.

Thanks! Sergio El 18/11/2019 a las 10:36, Andrea paz escribió:

I'm sorry: the link: https://www.cinelerra-gg.org/bugtracker/view.php?id=77#c2466

Il giorno lun 18 nov 2019 alle ore 09:32 Andrea paz <[email protected]> ha scritto:

...

Hi, Andrey. Olaf has proposed changes to the structure of the Latex manual. Since he is not a member of the mailing list, I enclose his attachments here too.

Add chapter 16. Pdf at: https://www.dropbox.com/s/0js49r47s0qu621/CinelerraGG_Manual.pdf?dl=0

GG's response to Glenn in the forum seems (https://www.cinelerra-gg.org/forum/help-video/hotkey-to-deselect-all-groups/...) so clear and interesting to me that I propose to include it in the latex manual: GG on selection's method: [at the end of paragraph 5.5; as a final summary. then becomes a new paragraph 5.6 and the following are moved to 5.7, ... etc. I'd like to name the section: "Good Guy speaks:"] There are several "selections" method. First, in the olden days, there was the column oriented timeline drag selection. That manifests in 1 of 3 ways. a highlighed vertical column, a single flashing line, or the blue line region between the [in and ]out marker labels. When the drag column is in use, it has the highest precedence and is used for selection. When the column is a single line, then the fall back selection is the [in/out] marker region, if they are set. When they are not set, and the cursor is flashing, then the selection start=end and the selection is empty, but it does have a position on the timeline which can be used for editing. This is input for the vertical style cut/paste drag/drop editing. Now, in the new "group" world, there are "edit" selections. These are created by using the drag/drop cursor and clicking edits to toggle select/deselection. These are input to a different (more modern) set of cut/paste/overwrite drag/drop editing. These are the set of operations you see when you click an edit with the middle mouse button, and are available using the hot keys which are more like text editor, ^x=cut, ^c=copy, ^v=paste, and so on... The delete key is not hooked to these operations. It is hooked to the cursor selection region. If there are In/Out points, they enter the selection priority queue between the column selection and the cursor only. You can see the region selection blue line across the timebar. This means that when the cursor selection is empty, the in/out selection will be used.

I've added the new section 5.6 and I enclose you editing.tex But are you sure GG will accept the title I put up? I can't believe it! :-)

Hi, @Andrea Thank you for your kind words. Let's start from your last question. There a several ways to do that. 1. Use Writer2Latex. In debian it in libreoffice-writer2latex package. Create table in Writer, select it, then go to Export... click the Selection checkbox and select LaTeX 2e from drop-down menu. After that the hude menu will appear. Select Ultraclean Article, Pdf (pdfTeX) and Unicode (UTF8) from drop-down menu, untick all other option, end click Export. Save new file and open it with Texstudio. Scroll down to the table. Note that Writer2Latex use supertabular package (but I don't like to use it). You can copy the entire table or copy only content. I prefer to create table header independently, to ensure the best results. One caveat, don't use any formatting in Write, except cell merging/splitting. 2. Use Calc2Latex extension for LibreOffice, it's old but still usable. Can be found here: https://sourceforge.net/projects/calc2latex/ Open any spreadsheet and select the rows/columns you want to appear in your table. Go to "Extras / Execute Macro / My Macros/Calc2Latex". Click on "Main" in the right side and "execute". Then you can copy entire table or only a content. I used that extension for a long time, then moved to the next method. 3. Script for Texstudio. Can be found here https://sourceforge.net/p/texstudio/wiki/Scripts/#paste-as-latex-table Copy entire script, open Texstudio and go to Macros -> Edit Macros -> Add. Paste entire script into text field LaTeX Content, tick script mark. Then copy table or cells from calc, go to Texstudio and use the script. 4. Online table generators. https://www.tablesgenerator.com/ or similar. Can't say anything about them. The first question. Give me some time and I'll create the header for that table. It's OK if I'll paste it in mail message, not in repo? Thu, Oct 10, 2019 at 02:55:48PM +0200, Andrea paz написал:

@Andrey

Despite the praise I've given you above, I'm too ignorant to be able to make a table for the Shortcuts :-) I've tried to study and adapt your examples, but I don't get usable results. I would need a structure like the one I show in the attached image (slightly modified from the table in the manual, because it contains errors). Another important question: [we talked about it some time ago, but I'm afraid I need detailed explanations] Come can I enter the huge amount of data in the libreoffice table as automatically as possible, instead of writing cell by cell? I tried to save the table in CSV, but I don't know how to do it.

@Phyllis

There is no hurry to have images or anything else; we can insert them easily when they are ready.

-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin

Best regards