Andrea, I have checked into GIT your Recording.tex and Plugins.tex (for Motion by SGE) and fixed and checked into GIT only changes up to the ***********. Also, checked in some of MatN's changes dated 09/15. Also, I think those are typos (misplaced space):

"Figure 16.4: Shows the Cakewalk theme (courtesy Olaf )on Preferences window with list of themes"

p. 516

should be

"Figure 16.4: Shows the Cakewalk theme (courtesy Olaf) on Preferences window with list of themes"

"8.1 Automation Keyframes,/ Autos"

at p. 213 and in Index should be

"8.1 Automation Keyframes / Autos"

also, I think line under illustartion 10.4 at p. 243 is worng

it says "Figure 10.4: Screencast of the native Video plugins in the default Cinfinity icon set." but same text was for fig 10.1 on page 240

*************************************** Above only are fixed ****************************************************************************************

also, i think fig 10.8 ("Figure 10.8: Remove Deinterlace-CV plugin") on p.248 can be moved up a bit, so it will be visually inside same section

also, fig Figure 10.11: , = expander; "-" = options at p. 253 ..

I think something wrong with template: a lot of those illustrations are just visually in next section, and not where they should be (page vs section anchor?)

p. 369 Figure 10.76: Before and after YUVShift adjusting is in section "10.9.90 Zoom Blur" as opposed to its own section "10.9.89 YUVShift"

at p. 470 "Figure 14.9: Subtitles on timeline" invaded section "14.4 Dvd Interlaced Chroma"

at p. 504 "Figure 16.2: Multi-screen Playback example useful for watching CINELERRA-GG run on the big screen" is visually in section "16.1.1 Audio Out section"

at p. 544 you probably should mention "Figure 18.1: Some windows used to manipulate Shell Commands scripts" somewhere in section text ?

at p. 563, I thing saying "(Fig 19.2)" somewhere at the end of paragraph ====== 19.7.2 Camera supplied LUTs A LUT, acronym for Look-Up Table, is a mathematically precise way of taking spe- cific RGB image values from a source image and modifying them to new RGB val- ues by changing the hue, saturation and brightness values of that source image. In other words, LUTs are used to map one color space to another. Some high-end cameras supply a .cube file to use as input. There are several different ffmpeg plugins included with CinGG for using Lut’s. These are: =====

will help? (image right after it, but with all this unwanted illustration wandering around ...)

May be all those will be autofixed by attached by Andrea .tex file, but I know no way to test it without TeX installed ....

I mean, may be it was design choice, but I prefer illustrations to be literally on the same page or in same section as txt referencing them, if possible .... -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin

В сообщении от Saturday 19 September 2020 17:59:38 Andrea paz via Cin написал(а):

...

I mean, may be it was design choice, but I prefer illustrations to be literally on the same page or in same section as txt referencing them, if possible ....

Something can be done, but sometimes it lacks the space to let an image enter its section and the same page. This is the case of fig. 10.8 and 16.2, which I cannot fix. Latex works like this: we can give indications of where we want an image, but then it takes care of finding the best layout. It is one of the great advantages and convenience of Latex, but often the solution it finds is not good. Moreover, when you change or add something over time, the structure changes again every time you build the pdf. For example, I have arranged the figures you pointed out, but nothing prevents latex from changing their position again in the future. I have learned that the best solution is to intervene as little as possible, even if in truth I always find myself fixing something and then again and again. Keep reporting every issue, when you notice them: this finishing work is important.

https://tex.stackexchange.com/questions/32598/force-latex-image-to-appear-in... ===== If you want the figure to float, but not passing a \section command. you can use the placeins package and its \FloatBarrier command beyond which floats may not pass. A package option allows you to declare that floats may not pass a \section command, but you can place \FloatBarriers wherever you choose. ====== may this link help?

Andrea, 2 things -- 1 - I integrated these changes BUT have not checked into GIT yet 2 -- I prefer them on the same page too but it makes the manual even longer On Sat, Sep 19, 2020 at 1:38 PM Andrea paz via Cin < [email protected]> wrote:

The problem is when there is no physical space on the page to hold the image (in the position we indicated); so it happens especially with large images -smaller images can often be fixed. The choice is whether to leave a blank space in a page with the image moving to the beginning of the next page (where it is located), but always within the same section, as Andrew prefers; or to let Latex fill the blank space with the next section and put the image at the beginning of the next page. I've let Latex do it so far, but if others prefer Andrew's idea, it's not difficult to fix it. What do you think? Andrey, what do you think? -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin

The little addendum for Andrew. You can setup the github repo for manual clone the cinelerra's git and bound it to sharelatex.com. The sharelatex provides full functional latex editor for web browser. The only limitation on free account I found for myself is compile time. But you can easily overcome this by use \includeonly command in latex. Sat, Sep 19, 2020 at 04:05:16AM +0300, Andrew Randrianasulu via Cin написал:

May be all those will be autofixed by attached by Andrea .tex file, but I know no way to test it without TeX installed ....

-- Andrey