- Cin - Cinelerra-GG Mailing Lists

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

Main.C - two options undocumented in usage?
by Andrew Randrianasulu 19 Jan '21

19 Jan '21

I see those handled in code: else if( !strcmp(argv[i], "-z") ) { start_remote_control = 1; } but i don't have remote for testing this .... else if( !strcmp(argv[i], "-b") ) { operation = DO_BRENDER; if( i > argc - 2 ) { fprintf(stderr, _("-b may not be used by the user.\n")); exit(1); } else strcpy(deamon_path, argv[i + 1]); I think this one start background render mode? Apparently, it want socket, so I can run it like /bin/cin -b /tmp/cinelerra.01e3ad92-6020-4d7c-b862-a8fa9d9d8917 but of course it will show nothing in gui, just: ../bin/cin -b /tmp/cinelerra.01e3ad92-6020-4d7c-b862-a8fa9d9d8917 RenderFarmClient::main_loop: client started ^Csignal_entry: got SIGINT my pid=17867 execution table size=0: signal_entry: lock table size=1 lock_items: 0 lock_frees: 1 SigHandler::signal_handler total files=0 Аварийный останов I CTRL_C it .... not sure if this specific option actually *that* interesting for end-users ... But one about starting in remote control mode (?) might be useful? ...time to look into this remote android protocol submodule . may be it can be extended for allowing save operation from remote device, so periodic backups can be triggered externally (just idea at this moment ) .....

2 1

Re-created and checked in cin.po +
by Phyllis Smith 18 Jan '21

18 Jan '21

A few hours ago, I created a new cin.po as Andrew had suggested since it was over 1.5 years old and I checked it into GIT. Also, checked in the following small fixes: 1) the warn = 0 instead of 1 in batchrender.C (I missed this and should have found it in yesterday's test) 2) added 1 more tooltip on Dangerous flag setting in appearanceprefs.C and slight re-wording on other one 3) removed the sample/display/interlace printf statements from ffmpeg.C and fileffmpeg.C (I hope that is OK)

2 2

[PATCH] UnsafeGUI toggle, tooltips, file overwrite warning for batchrender.c
by Andrew Randrianasulu 18 Jan '21

18 Jan '21

This time I tried to add user confirmation on project (EDL) file overwrite, _in addition_ to gui toggle hiding this button. Rafa Mar, I saw your letter, just tracking _where exactly_ this function writes file() turned out to be harder than just adding warning. For now.

4 18

Perpetual session question
by Andrew Randrianasulu 17 Jan '21

17 Jan '21

If I read manual (from Jan, 15, 2021) correcty, it says: ==== Perpetual session is very useful for working on a project over many days so you can just quit before shutting down and the next time you start up CINELERRA-GG you will be right back where you left off. You will retain all of your undo’s and redo’s. The binary ﬁle name is $HOME/.bcast5/perpetual.dat and as long as Settings → Preferences, the Appearance tab has the Flag Perpetual session set this capability takes effect. It is very important to understand that this is not the same as the continuously editing- operation-updated backup.xml ﬁle. The perpetual.dat ﬁle is only updated when you Quit CINELERRA-GG in the normal manner. Which means if you interrupt the program, or kill it, or there is a segv or system crash, the perpetual.dat ﬁle will only reﬂect the state of your project from when you last started CINELERRA-GG, and none of the editing/undo’s/redo’s you executed during the current session which was not ended normally. • the ﬁles backup.xml and backup.prev will operate the same as before so that if there is a crash, you will want to use File → Load backup in order to continue where you were interrupted. ==== So, I take this as IF my CinGG instance crashed with Perpetual Session turned on, I should start program again, load Backup, and then quit normally. So, on next load everything will by synced again. I am correct? Is there any pressure for making this Perpetual Session data also user-saveable? (I am thinking about another item in main menu, hidden if perpetual session turned off) Still thinking on automatic crash detection .... CinGG already know how to dump .dmp files so same function handle_dump() in guicast/bcsignals.C can be used to put crash file in ~/.bcast5, but this may become more complex with two or more instances .....

2 1

New proposal for "Save to EDL Path" in Batch Render
by Rafa Mar Multimedia en Gnu\Linux 16 Jan '21

16 Jan '21

*Hi Andrew*, I see that you know programming, To try to keep the "Save to EDL Path" option in the batchrender.C file Would it be possible that when this option is pressed, instead of overwriting the file loaded in EDL Path with the project that is now loaded in Cinelerra, if the precaution has not been taken to rename it, what it does is create a new file with the same name plus an incremental number or the current date? And in this situation that in EDL Path the name is updated with this new name? I mean if the file exists don't overwrite it, but create a copy with the same name plus a current number or date with the new project status. For example, I have my project: project.xml I hit the "Save to EDL Path" button and a new project_001.xml file is created, if I hit again project_002.xml, and this name is also updated in the EDL path. --------------------------------------------- Another option would be that if the file name exists, a backup copy of it with the date or an incremental number is created, so even if this button is pressed several times by mistake, there will always be a copy that will save the state of our project before play with this option. For example, I have my project: project.xml I click the "Save to EDL Path" button and a backup file is created with the current content of the xml of the EDL path called project_bk001.xml, if I click again project_bk002.xml etc ... In this way, this button would stop being dangerous, since we would never overwrite our original file. ------------------------ In both cases this would happen if the file loaded in the EDL path already exists on the disk, to avoid writing it. If, on the contrary, the user has taken the precaution of changing the name, its operation will be like the current onea new file will be created with the current state of the project. A programmer has told me that this is done by creating a function that in case the file already exists will not overwrite it, but will make a copy with an incremental number or the current date. I don't know how to do this, if I knew I would be happy to do it. I am still in favor of eliminating this option, because of how dangerous it is currently, and because this is not normally done from a batch render window, but from the project itself with the save as option. But I observe that there are people who want this option. And I think that in this way that I indicate it would be even easier to use avoiding loss of projects. The "Warn if jobs ...." option would be left as my friend did, if the user activates so it it will remain during the current session, but whenever Cinelerra is started this option will be disabled by default and in the xml it will always 0, in this way if the render is done from the terminal there will be no problems of matching versions. *Phyllis*, what do you think of this possibility? I apologize for the time I steal from you with this theme, but the goal is to perfect these little details of Cinelerra and prevent someone from losing their work in such a sadly easy way.

1 0