January 2021 - Cin - Cinelerra-GG Mailing Lists

*Broken* patch - reset some parameters in Titler (crashes Cin!)
by Andrew Randrianasulu 23 Jan '21

23 Jan '21

So, I tried to implement resetting of most numerical parameters in Titler gui. Yet, my attempt crashes at Titler window close/Cin exit :( So, DEFINITELY not for merging, but only as my current state of hacking

3 3

Re: [Cin] two more english tips?
by Rafa Mar Multimedia en Gnu\Linux 22 Jan '21

22 Jan '21

> There might be typo at very last line ("manual inline.") > Do you mean "online manual" ? Yes, I sent just written without reviewing, you are absolutely right, I have corrected this and some other little things, I am forwarding you the corrected version. It really still needs to be corrected by Phyllis. Do you think a "help" button in the wizard to open this guide is a good idea? This would make the use of this tool very easy for any new user. This button could be at the bottom, next to the close button and its text could be a simple "?" Icon. The files I have written with LibreOffice 6.0.7.3. I notice that Google Docs does not respect layout very well. I will try to do an automatic translation in Russian, and I will send you the result, so it will only be necessary to correct a few small questions. Greetings and thanks for your excellent work with Cinelerra GG. Quik start batch render (en).pdf <https://drive.google.com/file/d/18NnTeZXmYn9_GJ8_SxcTZknh33v9AuwE/view?usp=…> Quik start batch render (en).odt <https://drive.google.com/file/d/1EjRmiM0_Dms-fs-J19_7MEWPhthOa-Jd/view?usp=…> El vie, 22 ene 2021 a las 11:26, Rafa Mar Multimedia en Gnu\Linux (< rafamar.mm.ig(a)gmail.com>) escribió: > Sorry the previous shipments are not correct, now I make sure I have sent > you the correct ones. > > El vie, 22 ene 2021 a las 11:23, Rafa Mar Multimedia en Gnu\Linux (< > rafamar.mm.ig(a)gmail.com>) escribió: > >> > There might be typo at very last line ("manual inline.") >> > Do you mean "online manual" ? >> >> Yes, I sent just written without reviewing, you are absolutely right, I >> have corrected this and some other little things, I am forwarding you the >> corrected version. >> >> Do you think a "help" button in the wizard to open this guide is a good >> idea? This would make the use of this tool very easy for any new user. >> This button could be at the bottom, next to the close button and its text >> could be a simple "?" Icon. >> >> The files I have written with LibreOffice 6.0.7.3. I notice that Google >> Docs does not respect layout very well. >> >> I will try to do an automatic translation in Russian, and I will send you >> the result, so it will only be necessary to correct a few small questions. Greetings >> and thanks for your excellent work with Cinelerra GG. >> >> >> >> El vie, 22 ene 2021 a las 10:54, Andrew Randrianasulu via Cin (< >> cin(a)lists.cinelerra-gg.org>) escribió: >> >>> В сообщении от Friday 22 January 2021 12:41:18 Rafa Mar Multimedia en >>> Gnu\Linux via Cin написал(а): >>> > > I think problem may be exactly in this - we see selection, but no >>> > specific >>> > > signal (generated when we *change* selection) sent yet, so whole >>> function >>> > send >>> > > down empty string, and ffmpeg class not prepared for this .... >>> > >>> > I am useless for the code, I am sorry I cannot help, I can only think >>> of >>> > the option that the first time FFMPEG is chosen the extension box is >>> empty, >>> > that the user sees it empty, without content, this will force him to >>> choose >>> > the extension, or at least the error will not reference the .mp4 file. >>> > >>> > Another solution I can think of is to change mp4 to an extension that >>> is >>> > not usual today, simply to force the user to change it. >>> >>> I think this may affect normal rendering too (because they use same >>> code!) >>> But something to test more .... >>> >>> > >>> > Anyway, in the guide that I have written to facilitate the >>> understanding of >>> > the tool, I recommend clicking on mp4 the first time the wizard is >>> used to >>> > avoid this error. I sent it to you in case you want to translate in >>> > Russian. I would love to know Russian, it is a language that has always >>> > been pleasant to the ear. >>> >>> Sorry, I'm very bad at translating even few pages of documentation :{ >>> >>> I think you did excellent work on making this document, >>> THANK YOU A TON! >>> >>> There might be typo at very last line ("manual inline.") >>> Do you mean "online manual" ? >>> >>> > >>> > El vie, 22 ene 2021 a las 8:51, Andrew Randrianasulu via Cin (< >>> > cin(a)lists.cinelerra-gg.org>) escribió: >>> > >>> > > В сообщении от Friday 22 January 2021 05:42:55 Rafa Mar Multimedia en >>> > > Gnu\Linux via Cin написал(а): >>> > > > > I saw this error, and tried to combat it ... no results so far :/ >>> > > > >>> > > > the extension box empty, to force the user to put the desired >>> extension >>> > > > there? >>> > > >>> > > I think problem may be exactly in this - we see selection, but no >>> specific >>> > > signal (generated when we *change* selection) sent yet, so whole >>> function >>> > > send >>> > > down empty string, and ffmpeg class not prepared for this .... >>> > > >>> > > Again, a lot of functions (re)used in different places, so fixing >>> this a >>> > > bit harder than >>> > > just sticking one value in one file. >>> > > Or at least this file might be not that one ... >>> > > >>> > > > ---- >>> > > > Quik start batch render (en). >>> > > > >>> > > > El jue, 21 ene 2021 a las 23:44, Andrew Randrianasulu via Cin (< >>> > > > cin(a)lists.cinelerra-gg.org>) escribió: >>> > > > >>> > > > > В сообщении от Thursday 21 January 2021 23:48:55 Rafa Mar >>> Multimedia en >>> > > > > Gnu\Linux via Cin написал(а): >>> > > > > > I was referring to a "first steps" guide in English, you call >>> it >>> > > "Quick >>> > > > > > Start". Today the time that I allot every day to write >>> Cinelerra >>> > > > > tutorials >>> > > > > > I am going to dedicate to making an example of what I mean. The >>> > > manual is >>> > > > > > very good, but there are people who when they see so much text >>> get >>> > > > > scared. >>> > > > > > :-D >>> > > > > > >>> > > > > > I do not know if you saw the error that I reported about the >>> first >>> > > time >>> > > > > it >>> > > > > > is used and it is intended to export in mp4. Perhaps the >>> solution >>> > > would >>> > > > > be >>> > > > > > as simple as choosing FFMPEG that the extension box is empty, >>> to >>> > > force >>> > > > > the >>> > > > > > user to put the desired extension there. >>> > > > > >>> > > > > I saw this error, and tried to combat it ... no results so far :/ >>> > > > > >>> > > > > > >>> > > > > > I am going to make this example pdf and send it to you in an >>> email, >>> > > along >>> > > > > > with the .odt file. >>> > > > > > >>> > > > > > Also the es.po file in which I had to make an exception in >>> using >>> > > > > lowercase >>> > > > > > of a term, because people are used to seeing the shortcuts in >>> > > uppercase >>> > > > > and >>> > > > > > a user has notified me that accessing the tags was not working >>> and >>> > > that >>> > > > > it >>> > > > > > was opening a clips window... and this is because he confused >>> the ( >>> > > l ) >>> > > > > > (lowercase letter L) with the ( I ) (uppercase i). >>> > > > > > >>> > > > > > El jue, 21 ene 2021 a las 21:10, Phyllis Smith via Cin (< >>> > > > > > cin(a)lists.cinelerra-gg.org>) escribió: >>> > > > > > >>> > > > > > > I have reworded these tips and hope to check them in today >>> (+ the >>> > > > > > > transition fixes of Andrew). >>> > > > > > > >>> > > > > > > I keep thinking, is it possible to add a button (Help) that >>> opens a >>> > > > > short >>> > > > > > >> pdf about the use of this tool? >>> > > > > > >> I could make this pdf, with very little text and explicit >>> images >>> > > on >>> > > > > how >>> > > > > > >> to use it. It really is very unintuitive, but I think that >>> any >>> > > user >>> > > > > with a >>> > > > > > >> few lines is going to take advantage of this tool. >>> > > > > > >> >>> > > > > > >> A future goal was to hook up the HTML form of the manual >>> for help >>> > > via >>> > > > > > > the "h" key. That would take you right to: >>> > > > > > > >>> > > > > > > >>> > > > > >>> > > >>> https://cinelerra-gg.org/download/CinelerraGG_Manual/Batch_Rendering.html >>> > > > > > > -- >>> > > > > > > Cin mailing list >>> > > > > > > Cin(a)lists.cinelerra-gg.org >>> > > > > > > https://lists.cinelerra-gg.org/mailman/listinfo/cin >>> > > > > > > >>> > > > > > >>> > > > > >>> > > > > >>> > > > > -- >>> > > > > Cin mailing list >>> > > > > Cin(a)lists.cinelerra-gg.org >>> > > > > https://lists.cinelerra-gg.org/mailman/listinfo/cin >>> > > > > >>> > > > >>> > > >>> > > >>> > > -- >>> > > Cin mailing list >>> > > Cin(a)lists.cinelerra-gg.org >>> > > https://lists.cinelerra-gg.org/mailman/listinfo/cin >>> > > >>> > >>> >>> >>> -- >>> Cin mailing list >>> Cin(a)lists.cinelerra-gg.org >>> https://lists.cinelerra-gg.org/mailman/listinfo/cin >>> >>

1 0

two more english tips?
by Andrew Randrianasulu 22 Jan '21

22 Jan '21

Because this part of Cinelerra(GG) also not intuitive for modern users - what about adding two more lines in tips.en? diff --git a/cinelerra-5.1/tips/tips.en b/cinelerra-5.1/tips/tips.en index 781df953..8b2dc4fc 100644 --- a/cinelerra-5.1/tips/tips.en +++ b/cinelerra-5.1/tips/tips.en @@ -26,6 +26,12 @@ Use the +/- keys in the Compositor window to zoom in and out. Pressing Alt while clicking in the cropping window causes translation of all 4 points. +Batch jobs in batchrender respect their saved playhead position, so set it at +very beginning if you want whole project to be rendered. + +You can batchrender only region of project by defining selection with mouse +highlight or setting in/out points before saving it as EDL (Shift-S). + Pressing Tab over a track toggles the Record status. Pressing Shift-Tab over a track toggles the Record status of all the other tracks. If you think wording is OK - may be active translators (incl. me) should add the same to their tip files. (I tried this procedure with mouse highlight and in-out points by saving same proj four times with different selection and then making batch out of them) Project files also attached. media file should be at https://cloud.mail.ru/public/KKY8/o86j62p2z (quite a captivity propaganda translated to russian, from my point of life, but quick enough for testing something)

3 8

From depth of time ... Cinelerra + midi control!
by Andrew Randrianasulu 21 Jan '21

21 Jan '21

Sorry if you already saw this, i was re-reading some older Cinelerra documentation and mail list ... And found THIS: https://lists.skolelinux.org/pipermail/cinelerra/2008-March/013607.html YT video still around ….. https://www.youtube.com/watch?v=ruJVAiUYf7g and patch too :} http://www.jockusch.de/dm2/ I haven't tried to forwardport this to CinGG but anyway I like this concept ......

3 4

[PATCH] There is git-rebased xml check patch for batchrender ...
by Andrew Randrianasulu 21 Jan '21

21 Jan '21

Should protect against project (or anyfile) overwrite with just 'cin -r my_super_important_file' Try it out? WITH CAUTION! It still probably will *overwrite* some valid XML files, so do not let 'cin -r' run loose .... Not complie-tested yet ....

3 4

My current hack on batchrender I/O points .....
by Andrew Randrianasulu 21 Jan '21

21 Jan '21

It still doesn't work, resize event missing, and probably I must do i/o points just like labels - per job? Also, interested parties can change BatchRenderJob::get_strategy for returning RANGE_PROJECT and not RANGE_SELECTION ... Not sure if we should make this GUI-configurable .....

3 7

Batchrender update diff
by Andrew Randrianasulu 20 Jan '21

20 Jan '21

Generated by diff -u -w -B /home/guest/botva/src/cinelerra-git/cin-5/new-git/cinelerra/cinelerra-5.1/cinelerra/batchrender.C batchrender.C > /home/guest/botva/src/cinelerra-git/cin-5/batchrender_post_merge_raw_fix.diff (a lot of options because I wanted patch without empty lines added) and hand-editing header. probably should be applied from within cinelerra-5.1/cinelerra folder. should fix clonsole rendering and also fix -r file.xml overwriting in case it was not batchrender.xml AND should also NOT abort on GUI loading of same project file as batchrender job file .... (my previous patch introduced new crash because I used exit(1) even when GUI was running ..)

6 24

Suggestion for improving the BathRender window
by Rafa Mar Multimedia en Gnu\Linux 19 Jan '21

19 Jan '21

1- I think that the batch render assistant should not remember the last job, after closing the session, and always open blank. We precisely have the save and load button if we want to save the batch render list. I don't see much sense to the ~/.cast5/batchrender.rc file It would be more useful to improve the "Save jobs" option, showing the location of the xml file and if it already exists, simply when saving does not reopen the explorer window, a warning to overwrite, and simply pressing Load jobs will load it if it is in the box. The latter saved file if it could be remembered. 2- Is it possible that the batch render does not take into account the position of the playhead? This lacks any logic in batch processing. Typically, the entire project is rendered regardless of where the playhead was left. 3- Just a suggestion. Is it possible to add the option to render the area marked with the in and out points? For example, in a project I mark an area and by means of a button I indicate that in the new line of the project loaded in EDL Path only this area is rendered, if later I create a new line and modify the in and out points, I can add this to this new line and then the batch render will export these fragments to me, from the same or several projects. [image: Idea.png] In this way it would even be better than in many professional applications. You just have to explain the importance of creating a new line before changing data. It is the only thing that is not intuitive, but once it is known it is no longer a problem. I'm sticking with the idea of removing the Save to EDL button and the job/session match option, but this could go on as Andrew-R has done.

2 3

[PATCH] batchrender postmerge fix - git version
by Andrew Randrianasulu 19 Jan '21

19 Jan '21

Try this patch - should be valid git patch (previous patch was correct too, I hope, just you need to apply it from within cinelerra directory ... root@slax:/dev/shm/tmp/cinelerra-goodguy-20210119/cinelerra-5.1/cinelerra# cat /home/guest/botva/src/cinelerra-git/cin-5/batchrender_post_merge_raw_fix.diff | patch -p0 patching file batchrender.C I remade diff with git diff batchrender.C > /home/guest/botva/src/cinelerra-git/cin-5/batchrender_post_merge_raw_fix_git.diff now it compiles ..... will take some time (I applied all my patches via slackbuild, so soon I'll eat my own dog food ..:} * ) * - well, my dog Grey died last december ..so I have a lot of time ..:/

2 2

batchrender!!!!!
by Andrew Randrianasulu 19 Jan '21

19 Jan '21

WARNING, DATA LOSS!!!!!! If I run naively ../bin/cin -r /dev/shm/1.xml wher 1.xml IS my project file, NOT another batchrender.rc it will overwrite it with just <?xml version="1.0"?> <JOBS> </JOBS> I'm working on a fix .....

2 1