View Issue Details

ID Project Category View Status Date Submitted Last Update 0000363 Cinelerra-GG [All Projects] Feature public 2020-01-15 22:54 2020-02-21 11:28 PhyllisSmith PhyllisSmith normal minor N/A assigned open 0000363: Manual tips, contributions and improvements. As a result of completion of the CinelerraGG_Manual.pdf conversion from .odt to LaTeX by Andrey/Andrea + ... now we are ready for tips, update to include new features, contributions, and improvements. Refer to BT 0000077 for running original commentary and lots of how to hints from Andrey. There are 2 git areas that may or may not be in sync due to hopefully rapid changes and fixes:    https://github.com/einhander/cin-manual-latex    https://git.cinelerra-gg.org/git/?p=goodguy/cin-manual-latex.git;a=summary since it is easiest for me, probably the gg one will have the latest changes as I add gg new features as they are programmed in. MatN has recently added formatting fixes and reference fixes to Introduction, Tips, Developer, Translation (not checked in yet), and Installation. Phyllis has updated Shortcuts to add the new 18 or so since April 1, 2019. Mat seems to enjoy fixing formatting, which I do not because I would rather work on the wording. Some items for discussion: 1) the chapter #'s seems too big to me 2) although the "book" format is nice, when viewing the pdf from page to page, it joggles left and right and so not smooth 3) is it worthwhile to make changes so that the images are right next to the most relevant description or is it better to let LaTeX put them where they fit? it would be more work to line them up Some things I noted that need to be addressed in case anyone wants to fix these: 1) in Editing, Inter-View mode section 5.6, there is too much space between "clicking on the top white or black" and "click on a location", etc. 2) new plugins need to be added of: Alpha, Compressormulti (I am working on some words for only this one), Foreground, Flanger, Chorus, Tremolo, Sketcher plugins addition of Scale/Rotate and the help button, Crop & Position (IgorB plugin), and Tracer. Some of these are obvious and may need no description. 3) missing Transcode feature that I will work on along with fixes for Proxy in 19.3 of Tips. 4) still a lot of ? (actual question marks) in Configuration of stuff I just did not know what they were but maybe no one does. Please add more and if you start working on something, drop a note here so no one duplicates effort. No tags attached.

Activities

 2020-02-21 11:28 reporter   ~0002825 What I like about the current "Secrets of Cinelerra.html"file is that is it a single file. I think that is the full current manual were to be converted to html we might have many files. The current PDF is much larger that the previous one created from LibreOffice. However, it can be reduced significantly by using GhostScript: gs -dCompatibilityLevel=1.5 -dPrinted=false -dPDFSETTINGS=/ebook -dAutoRotatePages=/None -dQUIET -sDEVICE=pdfwrite -o CinSmall.pdf CinelerraGG_Manual.pdf . This takes it from 36 M to 12 M, and at a first glance, looks the same to me. Would 12 M be acceptable to be included in the distribution? 2020-02-21 03:55 manager   ~0002824 Checked into GIT, Andrea's cleanup of Configuration.tex. Continuing work on Windows.tex as I proofread and change the wording to not be exact copy of other manuals. Also, replacing any non-Cakewalk/non-png images as I go along. FYI note: MatN mentioned that the Cinelerra release still includes the Secrets of Cinelerra in html format. The rationale for leaving this was so that user's who did not leave a network up, could still get some help, even if so far outdated. In the future, either a Help ke (saving "h" shortcut for this) or the new manual will have an html version. 2020-02-18 20:03 manager   ~0002818 Checked into GIT, Andrea's fixes to Plugins.tex concerning href to hyperref for Motion and removal of bash. Also added to Translations.tex, the translation po files and their current status (feel free to reformat this table to improve it if needed). 2020-02-18 04:35 manager   ~0002813 @MatN A few updates. MatN's: -- settings.tex: increased space between number and text for tabel of figures to avoid them running into each other (e.g. see entry 13.14 in the table of figures). -- (I changed this as recommended) Chapter 16.7 : Maybe better to change the text after the CIN_PKG entry to "used to set your text domain, that is the locale path pointing to the cin.mo language file" (Configuration.tex) -- Also changed as recommended in BT 382 the LANG / LANGUAGE confusion in Configuration.tex. BUT it looks like I will have to change it again as I just read MatN's update !! I have to update the Translations.tex file concerning the status of the other 16 po/mo files as MatN suggested and I started that but could not finish. -- Removed some "language=bash" as seen while editing and a couple of "href" that needed to be "hyperref". @Andrea_Paz -- just noticed a couple of "href" in Plugins.tex that need to be "hyperref". If you feel like fixing these, please do so as I will not get to it for a long time. Also, a couple of wording changes I made in Windows.tex and changes to Tips.tex (maybe just bash or href). 2020-02-11 02:39 manager   ~0002800 Updated into GIT, Andrea's fixes for ColorSpace plugin, morrow chapterstyle to ensure that the 2-digit chapter numbers do not get cut off, and some small corrections for the DeepL translations for missing plugins that Andrea added on about 1/27/2020 (will have to proof read more carefully later). The pdf Manual was updated on the website to include these latest changes. 2020-02-10 02:26 manager   ~0002796 Added new ColorSpace plugin documentation to Plugins.tex and checked into GIT that + start of rewording in Windows.tex. Unfortunately I did not get the time to put the new Manual pdf file on the website with the update. 2020-02-07 19:48 updater   ~0002793 I agree. Removing [language=bash] gives more uniform (better) results. 2020-02-07 19:31 manager   ~0002792 @MatN THANKS! I am taking the bash out of Installation.tex and others as needed as I go along to proofread. I guess I should have figured that out myself but then there were lines like: /usr/local where local was blue and not usr + cd was blue but not cp. @Andrea_Paz I hope this is OK because I think the users when they see the blue color will think it is a link or reference. GG likes it the way it is, but he is not going to be using those lines anyway !! 2020-02-07 10:04 reporter   ~0002788 I don't think it is a bug. The lstlisting is highlighting certain words based on the language chosen, see for instance the listing just aboven the 1.1.2 header. If you remove the "language=bash" it will not highlight it (in blue). Maybe we should reconsider whether to use language highlighting at all. Take for instance the listing line just above "With persistence, you can get results" . It reads "$./confgure --with-single-user -enable-a52dec=auto ." , and the language for this lstlisting is set to bash. So it highlights the word "enable" , which in this case is part of a string, not a bash command. What if we remove "language=bash" from all lstlistings, or indeed any such language statement? 2020-02-06 21:52 manager ~0002786 @Andrea_Paz Thanks for the tip on the chapter styles - I have looked at that now and see what can be changed. Also, @MatN I am reading through the manual in order and have checked in some wording changes just now for Installation.tex. There is some strangeness that I have not figured out why it is. Under "Setting up the Initial clone" in section 1.1.3, there is "cd$ cd //" and the color of "cd" letters is black. A few lines later under "Update an existing repo" the letters of "cd" are blue. There is strange blue colored words seemingly throughout the document, notable the word "cd", "export", "enable" for no known reason. I think it must be a bug. 2020-02-03 17:46 manager   ~0002777 Checked into GIT minor corrections of Mat and me (Introduction.tex) Mat's === packages: Commented out unneeded /duplicated packages, can go in a next iteration. Plugins: Corrected misspelled "Whell"to "Wheel", and corrected table name/caption for titler controls. Avoid duplicate "List of table entries" (and thus duplicate warnings) by commenting out same table head at new page. @Andrea_Paz Followup on previous note where you said "Tips.tex: - link in \small - add F_scale_cuda and F_yadiff_cuda (N_Body? I don't see it.)" ==== You will only see the N_Body and Mandelbrot plugins when Cinelerra is build with Cuda compiled and loaded. 2020-02-02 20:07 manager   ~0002776 Checked into GIT new revision (final) from Andrea. Uploaded the resulting pdf manual to the website. (applicable to all) - Little changes in "italic/typescript" - resize some images Introduction.tex: -update internal link Tips.tex: - link in \small - add F_scale_cuda and F_yadiff_cuda (N_Body? I don't see it.) Translation.tex: Licenses.tex: - add Cakewalk license (by Olaf). Is it right? YES IT IS. Quickstart.tex: - Put credits in \footnote Developer.tex:- Various changes in formatting text AuxiliaryPrograms.tex: - Various changes in formatting text @MatN: I'm sorry; I'm not able to resolve plugins.aux warnings! 2020-01-31 20:51 manager   ~0002761 Last edited: 2020-01-31 20:58View 2 revisions Checked Andrea's fine-tuning changes into GIT + added Windows10/Cygwin (I tried to use similar formatting as Andrea, but if not it can be ANDREA's changes: changed).(applicable to all): - Little changes in "italic/typescript" - resize some images CinelerraGG_Manual.tex: - changed "Letter" to "a4paper" for resolve a warning Packages.tex: - added "ifthen" packages to solve the problem I had. but this was not the solution (it was something wrong with Attributes.tex).  ????? Does it serve as a tocvsec2 addiction or not? Plugins.tex: - add lines \settocdepth{subsection} and \settocdepth{section} (and commented in CinelerraGG_Manual.tex ) for better TOC. Trouble.tex: - changed label in lowercase and underscore - Internal link to proxy and background rendering sections - delete \medskip - nested list in "shell cmds" I agree with this -- "it would be nicer if we could control TOC entry level from within a chapter, because e.g. not all of the effects need the subsection entry in the TOC." This is my fault -- "almost all images are type .png, but about have are not a .png internally, but jpeg. This can be seen by (from a terminal) doing "file *.png" in the images directory.What is the reason for this?" because when I created Features5, I was trying to keep it small and saved files as jpeg. Eventually the rest of these will get made in the Cakewalk theme and I especially have to do the TV and DVD ones which are pretty awful right now. We will download this latest version on the Manual this afternoon when Bill is done with the builds and downloads all of them. 2020-01-31 10:49 reporter   ~0002760 @ Andrea, the warnings indeed point you the .aux file. I usually look at the text of the warning, like "tabular:tiller" and search for in in all the source using Geany "find in files" with subdirectory recursion. But in this case the .tex module was known, so TeXstudio will find it there too. More detailed control over TOC entries is apparently a hot item. Most of what I read is that only the tocvsec2 allows changing it on the fly, it's documentation tovsec2.pdf has an overview of the issues. 2020-01-31 09:47 updater   ~0002759 @MatN, "And talking of the TOC..." thanks for the cue, see if you like it this way (after Phyllis put it on the git). The problem remains to take the numbering off the plugin titles, but keep the numbering in the TOC; any ideas on how to do it? Maybe \setsecnumdepth? I don't really understand how this works! I only found two warnings in Plugins.aux; but I can't get my hands on them. In Plugins.tex now the warning is gone. 2020-01-30 18:43 reporter   ~0002758 latexmk works only if you start it as "latexmk -pdf" . This is because LaTeX itself can only handle a very limited number of images formats, and .pdf and .png are not among them. I tried by extracting the logo from the PDF as .png. It looks that latexmk computes a checksum of each file, and stores if in a text file CinelerraGG_Manual.fdb_latexmk . This means that simply "touch" on a file, which changes the date/time, does not cause a rebuild, I tried it. And, I noticed that the first time I got it running, it made 3 passes. Interestingly, almost all images are type .png, but about have are not a .png internally, but jpeg. This can be seen by (from a terminal) doing "file *.png" in the images directory. What is the reason for this? If .png is the preferred format, shouldn't the files internally also be .png ? @Andrea, thank you for the very many updates you do, the manual looks very good. I did not have Andrea's build error either. If you build using TeXstudio, please look at the log: there's a duplicate label in Plugins @Phyllis, the default Mint PDF reader, xreader, does not allow to jump directly to a TOC entry by cmd line option. I've entered a feature request for it in their git, who knows... Have not looked at the other platforms. And talking of the TOC, it would be nicer if we could control TOC entry level from within a chapter, because e.g. not all of the effects need the subsection entry in the TOC. But it is a frequent problem, changing that. 2020-01-30 00:20 manager   ~0002757 Last edited: 2020-01-30 00:24View 2 revisions Checked in Andrea's numerous fixes to include: Applicable to all: - Little changes in "italic/typescript, - resize some images    CinelerraGG_Manual.tex, Stuff.tex, Recording.tex, DVD.tex Multi5s.tex: - Reposizioned wrapfigure 14.6 Shortcuts.tex: -insert a \newpage Configuration.tex: - add Pulseaudio item. - Add "only X11 video driver" to Scaling Equation. - Adjusted black arrows in fig 17.1 and 17.2 - Put the \url in \small @Andrea - I did not get the error that you got "CinelerraGG_manual.tex error line 13 File ended ..". What I found on the internet was a suggestion to delete the .aux files and re-run LaTeX, maybe MatN has a real solution. 2020-01-29 17:34 updater   ~0002754 Thanks to MatN for the nice solution. I have a problem: I can't build the pdf because of the following error: CinelerraGG_manual.tex error line 13 File ended while scanning use of \@@BOOKMARK. \begin{document} Do you know how to fix it? @Phyllis: from my review of CinelerraGG_Manual.tex remove the line \settocdepth{subsection}, using tocvsec2 is no longer needed. 2020-01-29 16:12 manager   ~0002752 Checked in MatN's TOC for Plugins - I LIKE IT ! What do you think Andrea? I have not attemped latexmk (einhander's note) yet. 2020-01-29 13:39 reporter   ~0002751 I cannot use latexmk (einhander's note) to build, because it stops on missing file "./images/cin-logo" which is an PDF and not a png. TeXstudio does not complain. Should there not be a cin_logo.png ? 2020-01-28 23:23 manager   ~0002748 @Andrea I forgot to check the Plugins.tex additional sentences you added that were translated by DeepL but will try to get that done today yet. @MatN There is a plan to add the "h" shortcut to Cinelerra for Help but I do not know if it can be linked to a plugin in the TOC. That would be good though. However, the Help connection is not in the foreseeable future yet. @All - some more fixes from Andrea added to GIT checkin today. Before this, the CinelerraGG_Manual.pdf was updated on the website (minus some possible wording for DeepL translated sentences yet). 2020-01-28 10:33 reporter   ~0002744 Have you looked at the tocvsec2 package? Apparently it allows close control over what is listed in the TOC. See http://www.ctex.org/documents/packages/contents/tocvsec2.pdf . Is the idea that by having an entry for the plugins in the TOC, it might become possible to link (for help) from an effect plugin directly to the PDF and the entry for the plugin? 2020-01-27 16:05 manager   ~0002743 Nice update/changes from Andrea to include have been checked into GIT: common/settings.tex: - add blue color to section titles (by Olaf). Do you like? YES, I LIKE IT !!!!!! Keyframe.tex: -add "Allow keyframe spanning" section Plugins.tex: [NOTE1: To answer to %Todo (I don't know if from Andrey or MatN); I had put each plugin title as "\subsection" (with its numbering) because I wanted the index of the manual.pdf to show the entry for each plugin. This was to make it faster and more convenient to search for a certain plugin. But in fact the plugin names do not appear in the TOC and so we need another way to put them and we can remove the use of \subsections or numbering. NOTE2: Among the audio plugins that I consider important, I left out Equalizer; Parametric Equalizer and Synthesizer. Among the video plugins that I consider important, I left out Sphere Cam; (SVG via Inkscape and ReRoute have been criticized for their working). I have not put better and more detailed descriptions for absolute lack of knowledge. NOTE3: The sentences added by me have been translated with DeepL and probably need revision.] - Little changes in "italic/typescript" - downsize/upsize some images - Add/modify audio plugins: Reverb; Compressor; Compressor Multi; Chorus; Flanger; Tremolo. - Add/modify video plugins: Alpha; Crop & Position; Foreground; Sketcher; Tracer. - Modify Interlacing options (from Resource --> Info) in Frame to Fields plugin. - Changed "c"inelerra in "C"inelerra. - Correct strange behavior with perspective plugin: \longtable (changed in \tabular) - Changed tabular in longtable (sketcher plugin) - various small changes + I checked MatN's Plugins.tex to ensure all of his changes were in and added his 180 degree fix. 2020-01-25 17:40 manager   ~0002737 Checked in MatN's changes as follows (BUT not Plugins.tex which I will merge later with Andrea's changes for the plugin additions that he is currently working on) Changed "cinelerra" to "Cinelerra" if it is used as a name in the following parts: Developer (in Developer.tex I did remove the 5.1 from Cinelerra 5.1 and eventually the other 5.1 should either be removed or changed to GG except in pathnames), DVD, Installation, Introduction, Multi5s, Recording, Rendering, Shortcuts, Stuff, Transition, Windows. Plus: Overlays: removed out-of-place UK pound sign & Recording: fixed text in Android remote control section. Last night I checked in Editing.tex in order to add "Referenced File" section. 2020-01-24 03:32 manager   ~0002736 Checked into website Latex Manual GIT a few more corrections from MatN + me. If anyone notices Cinelerra, Ubuntu, Mint and other distros spelled without the first character as a capital letter when not used as code, please change them if you think of it. Also, sometimes I might check changes in without mentioning it here if it is just "words" or missing features but will stay away from Plugins.tex. 2020-01-22 00:37 manager   ~0002735 Andrea is going to work on Plugins.tex next. I only have part of the Audio CompressorMulti done so it can wait. I did update Tips.tex to add a short description of Transcode to the Proxy section. More corrections from Andrea checked into GIT: Title.tex:- fit cover in one page Introduction.tex:\url in \small (I hopefully changed this correctly) Loadandsave.tex:- add internal link with appendix, - some words/phrases in typescript, - internal link to 8.1 and 4.3.3, - "load recent..." new option is missing. Editing.tex:, - Credits on AShuttle Pro section: eliminate broken link. - internal link to 16.1.1, - Add \item to drag groups (from BT 0000362) Rendering.tex:,- Little adjustment of "italic/typescript" FFmpeg.tex:- Little adjustment of "italic/typescript", - internal link to 4.3.3 Keyframes.tex:,- Little adjustment of "italic/typescript",- The description of the "allow keyframe spanning" button is missing. ALLOW KEYFRAME SPANNING: When you create a drag selection and you modify a value in a plugin then everything in the selection gets modified the same. It use the previous keyframe and if there is no previous keyframe, then the default keyframe in your $HOME/.bcast5 definitions is used. 2020-01-20 19:50 manager ~0002733 Checked into GIT, Andrea's numerous formatting changes in Windows.tex + ... Windows.tex:- add internals link - change words/phrases by removing quotes and putting "italic" and "typescript". - Added information on the coloured bar that appears (in the Timebar) between the In and Out points., - Change mask_window.png, - Change resource_window.png Stuff.tex: Put in graphical arrows in fig 17.1 and 17.2 Installation.tex: changes \url to \href{mailto:[email protected] }{mailing list} FFmpeg.tex: changes \url to \href{mailto:[email protected] }{mailing list} @Andrea I did Installation.tex manually as it was not in the tar.gz file so hopefully I did it correctly and I found an url in ffmpeg.tex too that I changed. 2020-01-20 13:45 updater ~0002732 Transcode It seems to me a common option for all NLEs (who allows multiple selection and batch transcoding and who one file at a time). For me putting them after the proxy section is OK. Proxy 1:1 I'm sorry, I'm incompetent about proxy. PS: I just downloaded the pdf from the website (last commit: "11 hours ago"). It contains MatN's latest interventions. No problem for me. 2020-01-19 22:17 manager ~0002728 @MatN Today checked in your latest fixups for Recording/Multi5s/Stuff/Plugins/Rendering. Also, settings.tex EXCEPT for \chapterstyle{madsen} % one of chapter header style for memoir documentclass to \chapterstyle{komalike} because looking at that versus adding to CinelerraGG_Manual.tex the line: /parskip=14pt which to me looks better for paragraphs. But I am flexible. @Andrea Just need your opinion on "Innovative New Features" -- I do not know if Transcode is innovative or not. I have added it here locally in Tips.tex after Proxy. Is this Proxy 1:1 different than other NLEs and should I mention it next to Proxy as an Innovative new feature? The manual is already starting to look more consistent which is hard to do with so many pieces being put together and my inconsistency in writing Features5. FYI: even though gg has been updating the CinelerraGG_Manual.pdf on the website every couple of days to keep it updated with your changes, it seems to download to us here in the United States an older version. 2020-01-19 20:26 reporter ~0002725 @Andrea_Paz Sorry, Andrea. I would like to do them but I am out of the games for a while, for my personal problem. For that, you needed to do a fake with Inkscape. I guess that Olaf or Sam could make it but they may be busy on their things, I think. I am so sorry. 2020-01-19 19:14 updater ~0002724 @IgorBeg, @All I was trying to put the images of the Mask tool taken from the manual-cv inside our manual-gg. But they are unusable. I tried to make some of them myself, but I get very bad results when I put in writing and arrows. Do you want/time to propose something yourself? I'd integrate them into manual-gg. I Append the various images. mask-images.tar.gz (740,173 bytes) 2020-01-19 14:52 reporter ~0002722 @Andrea, I gladly leave shooting arrows to you :-) @All, I only have \todo in plugins in the gg git clone I have. I've just mailed Phyllis an update for settings, to fix the run-in of numbers and text in the table of figures. But there are entries without caption in section 12, I'll look at those. 2020-01-19 12:35 updater ~0002720 @MatN I wasn't consistent at all, because I didn't realise until late that the edges were coming off. Now that I've started revising the manual, I'm gradually correcting the spaces between the arrows and the abuse I've made of Typescript. So leave those two things to me, so we don't do the same job twice. @All Speaking of TODO, in the chapter Windows.tex there is a "%\todo" of, I think, Andrey. But I don't understand its meaning (what is Fig 3?). 2020-01-19 11:24 reporter ~0002716 Ah, I didn't know there should be arrows in those pictures, I thought you were referring to the text. Regarding the space around the arrows, good argument about breakline. So it should be xxxxx$\rightarrow\$ yyyy everywhere ? I think it is, but I'll keep it in mind when reading the manual. 2020-01-19 10:52 updater   ~0002715 Are you referring to the TODO in figures 17.1 and 17.2? I will insert the arrows (tikz code) shortly and send the changes to Phyllis. Then we can delete the Todo. I put the space between the arrows because it doesn't give you any breaklines problem, especially if you use Typescript. Is there another solution? 2020-01-19 10:13 reporter   ~0002713 @Phyllis, your point 1. If in Settings.tex you change   \chapterstyle{madsen} % one of chapter header style for memoir documentclass to   \chapterstyle{komalike} % one of chapter header style for memoir documentclass and rebuild, is that better? I wonder if we should put page numbers in the header too, if there is no footer that saves space. And for screen reading I think that is nice. @Andrea, there is still a \todo about an arrow. I think it looks fine, so maybe it can go? Also, it would be nice if the arrows were all specified identically, regarding spaces yes/no before or after . 2020-01-18 17:19 manager   ~0002710 Last edited: 2020-01-18 17:21View 2 revisions Checked in Andrea's cleanup and help changes to GIT: packages.tex: Put options for small font size and italic in the captions package Introduction.tex: - Putting words/phrases in quotation marks in "italic"., - added item-list entry on OpenEDL,- Put in \small some \url Installation.tex:- \url in small font and "centered",- Added dependencies for Arch Linux,- Quotation marks are removed from some words/phrases and put in,"italic" or "typescript".,- removed \todo{hanging line},- solved \todo{link} by putting a link to it README.md: adding "numbers=none" option to [lstlisting]. 2020-01-18 00:30 manager   ~0002709 Checked into GIT MatN's 11.tex files that fix:   Configuration, FFmpeg, Loadandsave, Plugins, Recording, Rendering : line numbers removed.   DVD: line numbers removed, overwritten lines fixed (above picture dvd-batch01.png).   Editing: line numbers removed, fixed double defined label fig:timeline , open EDL picture lenght.png was      include twice.   Shortcuts: fix double defined labels.   Tips: fix double defined label.   Windows: line numbers removed, fixed double defined labels. Will upload the CinelerraGG_Manual.pdf built with the most recent set of changes to the website. But I think we need to have a blank line between paragraphs - how to do that? Previously each paragraph was indented about 5 spaces but I think no indentation and just a blank line looks better. @Andrea I don't know anything about GIT so I can not answer about "Isn't there a way to connect the gg repository to the branch I already have? (that clone of einhander)" but the gg GIT will probably be updated quite frequently so it would probably be better to pull from that. However, we do not want to lose any of your work so if you are most comfortable working as you have been, continue to do so and hopefully I can merge in all of your changes (we have Gmods here to do this). 2020-01-17 21:26 updater   ~0002708 If I do a "clone git" I have to make a new branch in a new directory. So I find myself a branch with the einhander git clone (which I have worked on so far) and a new branch with the gg git clone. From now on, I only have to use this last one? Isn't there a way to connect the gg repository to the branch I already have? (that clone of einhander). 2020-01-17 19:11 manager   ~0002707 @MatN The Shuttle key layout is suppose to be suggestive of the physical layout as you see in the image a few pages earlier. For example in the photo, there are 4 rectangular silver colored button towards the bottom. These are K10, K11 and K12, K13 in the Shuttle key layout and the K# names match the Cinelerra script for defining the functions of the key. Page 13 in the following url:    https://contourdesign.no/wp-content/uploads/2019/03/Trans_Shuttle-User-Guide-Mac-v3-small-.pdf would be better but you can count on me NOT to do that! 2020-01-17 18:16 reporter   ~0002706 @Andrea, To avoid double work, I am already working on your point 5, have sent updated "editing" and "windows" to Phyllis. Currently tackling "ffmpeg" . By the way, I use Geany for this, as it has wider search facilities and can build Latex too. Once done, I'll look what else I can do. Why is the Shuttle key layout presented as it is? I could get it onto a portrait page, but is a simple list like for the Cinelerra keys not more readable? 2020-01-17 17:57 reporter   ~0002705 1. If you already created a copy of the gg git by "git clone", then just a "git pull" in the directory is sufficient, the entire path is not needed. 2. On github, if you want to contribute, you (after getting an account) you create a "branch" of the main git for that product, using a unique name for that branch, clone that new branch to you local system. Then you make changes to the code, put it in your local branch, then update your remote branch. Then do a "pull request" to the main branch, so that the owner of the main branch knows there are updates waiting for the main branch. I presume the gg git could work the same way. 3. Personally, I find it easier to clone the gg and einhander latex gits in separate directories, initially copy the gg git directory to another one for myself, do mods and test there, when done, I use the program "meld" to compare with the other two (and usually find something to change). When done, the modified file(s) I mail to Phyllis for review and inclusion in the gg git if OK. 2020-01-17 14:23 manager   ~0002704 Last edited: 2020-01-17 15:33View 2 revisions How to clone the manual directory:  - In a window create a directory where you want to put the manual and move there. For example, I did a    cd /tmp; mkdir Manual  - type in: git clone git://git.cinelerra-gg.org/goodguy/cin-manual-latex.git Manual The above example is on /tmp and will be deleted when you reboot, so do not put it there. Then:  - look at README.md in that directory on how to proceed To merge into an existing git, first get into that directory and type:  - type in: git remote -v ;just displays the origin of your git  - type in: git pull git://git.cinelerra-gg.org/goodguy/cin-manual-latex.git    which will pull the later versions of files and create new ones 2020-01-17 13:59 updater   ~0002703 Forgive my stupidity; you can show me step by step how to add the cinelerra gg repository for the latex manual to my git? Then I can pull it so I can update my branch. Another question: if I make updates on my git, then send the various .tex files to Phyllis via email or Bug Tracker or are there other ways? About Phyllis' item 3, I think it's best left to Latex. That's its main feature, and when changes/additions are made to other parts there's no need for new interventions. 2020-01-16 17:54 manager   ~0002701 I checked in the settings changes as recommended by MatN and switched to oneside (and Translations.tex). Did not add Glossary yet though. 2020-01-16 16:29 reporter   ~0002700 @Andrea, regarding point 2: In settings if you change to: \usepackage{geometry} % page geometry \geometry{left=2.0cm} \geometry{right=2.0cm} \geometry{top=2.0cm} \geometry{bottom=2.0cm} \parindent=0.0cm you get the same margin left/right, and no paragraph indent (which I find confusing for short paragraphs). In addition, in the main document, if you change \documentclass to oneside, you get rid of some blank pages. two sides are irrlevant for screen reading anyway. Please see if this makes it better for you. Maybe we ought to have different build for screen reading, large and small, and also for paper (left/right side different, and nicer chapter headings.) 2020-01-16 08:44 updater   ~0002697 I will not be brief :-) The two big things to do: 1- Images: a- Make high definition images for printing. b- Using a uniform theme (by Sam, I can't remember where) c- Remove the window bar (by Olaf; BT77 #2500) d- Get low-definition images for video from high-definition ones. e- New global images at the beginning of each chapter (by Phyllis; bt77 #2498) f- Size the images so that they all have the same size lettering (by Olaf, I can't remember where) 2- Conversion to html and then: a- translate into several languages b- contact user who had proposed conversion to Asciidoc. Other things: 3- Layout changes (basically point 2 proposed by Phyllis): a- Olaf's proposals (BT77 #2466) b- proposal by MatN (BT77 #2644) c- add color to pages (by Olaf; BT77 #2470) 4- Add introduction to the Mask Tool taken from the CV manual, with related images (by IgorBeg; I can't remember where) 5- Remove numbering from [lstlisting] that does not require it. 6- Personal opinions, my obsessions, which you can tell me not to waste my time with: a- to standardize the Labels by putting them all in lower case and without blanks. b- put all commands, actions, instructions, paths and code into Monospace fonts. For point 2 of Phyllis my opinion is that you can make a second version for the video, so not a book version. With Latex it should be instantaneous.

Issue History

Date Modified Username Field Change
2020-01-15 22:54 PhyllisSmith New Issue
2020-01-15 22:54 PhyllisSmith Status new => assigned
2020-01-15 22:54 PhyllisSmith Assigned To => PhyllisSmith
2020-01-16 08:44 Andrea_Paz Note Added: 0002697
2020-01-16 16:29 MatN Note Added: 0002700
2020-01-16 17:54 PhyllisSmith Note Added: 0002701
2020-01-17 13:59 Andrea_Paz Note Added: 0002703
2020-01-17 14:23 PhyllisSmith Note Added: 0002704
2020-01-17 15:33 PhyllisSmith Note Edited: 0002704 View Revisions
2020-01-17 17:57 MatN Note Added: 0002705
2020-01-17 18:16 MatN Note Added: 0002706
2020-01-17 19:11 PhyllisSmith Note Added: 0002707
2020-01-17 21:26 Andrea_Paz Note Added: 0002708
2020-01-18 00:30 PhyllisSmith Note Added: 0002709
2020-01-18 17:19 PhyllisSmith Note Added: 0002710
2020-01-18 17:21 PhyllisSmith Note Edited: 0002710 View Revisions
2020-01-19 10:13 MatN Note Added: 0002713
2020-01-19 10:52 Andrea_Paz Note Added: 0002715
2020-01-19 11:24 MatN Note Added: 0002716
2020-01-19 12:35 Andrea_Paz Note Added: 0002720
2020-01-19 14:52 MatN Note Added: 0002722
2020-01-19 19:14 Andrea_Paz File Added: mask-images.tar.gz
2020-01-19 19:14 Andrea_Paz Note Added: 0002724
2020-01-19 20:26 IgorBeg Note Added: 0002725
2020-01-19 22:17 PhyllisSmith Note Added: 0002728
2020-01-20 13:45 Andrea_Paz Note Added: 0002732
2020-01-20 19:50 PhyllisSmith Note Added: 0002733
2020-01-22 00:37 PhyllisSmith Note Added: 0002735
2020-01-24 03:32 PhyllisSmith Note Added: 0002736
2020-01-25 17:40 PhyllisSmith Note Added: 0002737
2020-01-27 16:05 PhyllisSmith Note Added: 0002743
2020-01-28 10:33 MatN Note Added: 0002744
2020-01-28 23:23 PhyllisSmith Note Added: 0002748
2020-01-29 13:39 MatN Note Added: 0002751
2020-01-29 16:12 PhyllisSmith Note Added: 0002752
2020-01-29 17:34 Andrea_Paz Note Added: 0002754
2020-01-30 00:20 PhyllisSmith Note Added: 0002757
2020-01-30 00:24 PhyllisSmith Note Edited: 0002757 View Revisions
2020-01-30 18:43 MatN Note Added: 0002758
2020-01-31 09:47 Andrea_Paz Note Added: 0002759
2020-01-31 10:49 MatN Note Added: 0002760
2020-01-31 20:51 PhyllisSmith Note Added: 0002761
2020-01-31 20:58 PhyllisSmith Note Edited: 0002761 View Revisions
2020-02-02 20:07 PhyllisSmith Note Added: 0002776
2020-02-03 17:46 PhyllisSmith Note Added: 0002777
2020-02-06 21:52 PhyllisSmith Note Added: 0002786
2020-02-07 10:04 MatN Note Added: 0002788
2020-02-07 19:31 PhyllisSmith Note Added: 0002792
2020-02-07 19:48 Andrea_Paz Note Added: 0002793
2020-02-10 02:26 PhyllisSmith Note Added: 0002796
2020-02-11 02:39 PhyllisSmith Note Added: 0002800
2020-02-18 04:35 PhyllisSmith Note Added: 0002813
2020-02-18 20:03 PhyllisSmith Note Added: 0002818
2020-02-21 03:55 PhyllisSmith Note Added: 0002824
2020-02-21 11:28 MatN Note Added: 0002825