July 2020 - Cin - Cinelerra-GG Mailing Lists

Just a mailing list test 2
by Sam 09 Jul '20

09 Jul '20

You can ignore this email, we are doing some tests on Mailman and Gmail. Sam

1 0

Just a mailing list test
by Sam 09 Jul '20

09 Jul '20

You can ignore this email, we are doing some tests on Mailman and Gmail. Sam

1 0

New monthly pkgs and tars available on the website
by Phyllis Smith 08 Jul '20

08 Jul '20

https://cinelerra-gg.org/download/pkgs/ https://cinelerra-gg.org/download/tars/ https://cinelerra-gg.org/download/CinelerraGG_Manual.pdf The "gang modes" (to include DAW-like audio channel mash) is very minimally tested and some improvements have already been suggested and are planned for next month. Andrea has converted from pdf to latex and added to the manual with some quite helpful images in section 5.2.1. As usual, if you have problems, please report them and remember you can always back out to last month's build in old_pkgs or old_tars directory. A copy of the release notes, also available on the website is below. GG/Phyllis *********************************** *Cinelerra-GG (Version Infinity) Release Notes for 06/01/2020-06/30/2020 for builds* Cinelerra’s *youtube channel* can be accessed from the website *as set up by Sam*. The link is under the Support header - https://www.youtube.com/channel/UCW97mOMN_tAqVCn8k4Euf1w/ An update for the* Italian wikipedia by MatN and Andrea *is now live. The *Elive distro by Thanatermesis* has been routinely including Cinelerra for years and so Sam has added a link as a choice for users (BT# 453). 1. Add master/armed_gang track *operations for closer to DAW-like editing*. A method has been implemented to treat multiple audio channels as one so that the edits made to the master channel are automatically duplicated for each channel (BT 433 / Glen of AVLinux). For usage details refer to the updated manual on the website, section 5.2.1. This feature is not limited to this purpose as more usage scenarios are likely to be quite useful and additionally free up monitor display space. 2. *IMPORTANT - Changed Behavior*: A minor change to “move up” and “move down” tracks was implemented to correct what was an exchange on the top track or bottom track instead of a move. 3. *Usability Improvements*: The *Perspective *plugin has added visible 1-4 numbers on each of the 4 points for ease of use and the number of the point is shown next to the X box in the menu (MatN request, BT #443). The *Rotate plugin* has been modernized with improvements by a Contributor. A minimum Speed auto value is now used for the update instead of the zero value causing problem. FFmpeg will show a “seek retry limit message” for information purposes. An easy method to reopen a closed mini-viewer mixer is now in the Window pulldown which displays each of the media that occupied a mini-viewer window. Minor improvement in Settings→Preferences, Appearance tab to better accommodate languages and for aesthetics (MatN contribution). The Spanish translations have been improved some more (RafaMar) and minor RU/FR (by MatN). Setting and changing Audio or Video track height has been slightly modified and Shift-rmb resets to the original configuration default. 4. *Bugs/Issues fixed:* A patch for the commercials feature was generated and applied (contributed by mehw BT#458). The “clear frame” was not working in Tracer as a result of background color, but now fixed. Keyframe Spanning was not working for Sketcher, Tracer, and CriKey due to their unique multiple points/curves setup. This was quite a difficult/involved fix (RafaMar BT #441). Rework of the plugin presets was completed plus Text was changed to Data for spanning keyframes. Some additional code cleanup was performed as usual. Embedded object fix – looking for open delimiter followed by closing delimiter. Deadlock fix by opening files one at a time. Fixed hang caused by an extra lock (Andrew found). Reset caches were crashing on vicon drawing, but this has been corrected (Andrew diagnosed). SEGV for reset cache fixed as found (in dmp file provided by Skinkie). Vicon checkout fix + fixed vicon video/cache errors + address delays created by vicon drawings. Cache checkout tweak to remove_all/delete_oldest rework. Extract name Valgrind bug fix. Fixed some show window deadlocks and X10 remote control memory error. An old bug just found, where removing a shared plugin worked incorrectly, is now fixed. Collect proxy/nested clips fixes (BT #427 by IgorBeg). A new environment variable, BC_TRACE_XERROR will dump the stack on this type of error, thus aiding in analyzing any of these types of crashes.

7 27

Cinelerra-GG Mailing List & Gmail bounces
by Sam 05 Jul '20

05 Jul '20

Hi Cinelerra-GG friends, Yesterday, Google unfortunately blocked our Cinelerra-GG mailing list for a short time because too many mails were sent to Gmail from our mailing list. We have many users who use Gmail. Mailman automatically stops sending emails when there are too many bounces. Gmail seems to be very sensitive about too many emails. However, there is a workaround and some work on the server is necessary. It will take another two to three days, after that everything will work as usual for Gmail users. Other users are not affected. Sam Cinelerra-GG.org

1 0

New suggestions
by Andrea paz 03 Jul '20

03 Jul '20

>From the new Cinelerra-CV website I found the updates of Cinelerra-CVE: 1- new one-line internal api for error messages (macros errormsg and errorbox) 2- implemented pts based timing on video and audio making possible projects without constant framerate 3- improved synchronization with Alsa output: no jumping around on playback 4- removed playback direction dependancy from core rendering 5- replaced samplerate based timing with clock based timing 6- implemented new API and support macros of all plugins, removed old API 7- implemented pts in renderfarm 8- removed broken plugins including plugins importing from devices 9- all configured ALSA PCM devices are selectable 10- replaced all decoding and encoding with AVlibs (ffmpeg libraries) 11- program may be linked to external (system) AVlibs 12- AVlibs from ffmpeg 2.8 to 3.4 are supported 13- new GuideLines system for plugins 14- optimized EDL internal manipulation (EDL structures are now permanent - never removed) 15- rewritten Crop feature - it is now a normal keyframable effect (only 16bit color models are supported) 16- implemented master track idea 17- automatic backup is configurable, can be turned off I don't quite understand, but I find the points: 2; 4; 5; 14 and 15 interesting. Can you explain them to me? Is there anything you can get for CinGG?

2 1

Problems with Camera Automation?
by John Coppens 03 Jul '20

03 Jul '20

I had this problem with camera automation yesterday when trying to do the following: - I have a full-screen take of a talking person's face and wanted to reduce the size and move the image to the lower right corner when other contents had to appear. - Moving the cursor in the Camera animation only move the image very slightly (maybe 10% of the screen size). - First scaling the Z-axis reduced the image Ok, but still almost no X or Y movement. - Dragging the image on the screen worked, but the X and Y parameters became huge (1000's). And the animation algorithm was completely confused - on play, the image disappeared way out of screen and then reappeared. The position was not exactly the one 'edited'. Any way to accomplish this? John

5 9

Thanks and suggestions.
by Rafa Mar Multimedia en Gnu\Linux 02 Jul '20

02 Jul '20

First of all I want to thank you for improving the Rotate Effect. Cinelerra has gone from having an effect that was a bit stressful to use it to having a wonderful rotation effect. So thank you very much to this collaborator for his time. I know the suggestions are not new and I apologize for being repetitive (or a heavy person) The wizard for loading project files (xml) and media files is quite puzzling to new users. The logical thing is to have a wizard to load .xml project files and another one for multimedia media, videos, images and audios. Cinelerra does NOT have an effect for changing the speed of individual clips, this today makes Cinelerra a little off the hook for professional applications. The ideal and normal thing today is to have an effect capable of manipulating the speed of a single clip and automatically also change the duration of the audio associated with this clip while maintaining the pitch (timestretch). Being an ignorant of programming I thought that this would be easy to implement, since open source Audacity has an excellent Timestretch effect, and I thought that the code could be reused and adapted to Cinelerra. The line to modify the speed, although it has been improved a little, continues to cause errors that make it difficult to use, as it does not respect the entry and exit points defined in a clip. This error occurs when we insert a clip into a track with the changed velocity values. I made some videos to try to explain this error. https://streamable.com/ehnhj9 https://streamable.com/q72zfq Another thing that confuses new users a lot is the default settings for the sliders on the camera and projector wizards. These are set to only 100 px in both X and Y. Is it very difficult to define these X and Y values to the px of the project? for example if I am working on a 1920x1080 project the maximum and minimum of X should be -1920 +1920 and in Y -1080 +1080. Although I still think that the ideal would be to work with percentages, where 0 is the default point, -100% the clip completely off the screen from the left or from below, and 100% clip was from the right or up. Perhaps this point is the most irrelevant when it is discovered that this can be configured in the values below the timeline and even manipulated from the screen itself, the slider is very secondary. If I knew how to program apart from the aforementioned, there are two things I would do with these assistants, include the option to rotate and some axes on the screen so that when you rest your mouse on them and move, you can only do it from the selected axis. But I understand that these things a programmer will only do when he is bored at home, because they are not important either. [image: image.png] If someone has had the holy patience to read this far, thanks and regards.

2 1

Rendering multi-threads
by Andrea paz 01 Jul '20

01 Jul '20

I have a CPU 8 cores / 16 threads, but the final rendering uses only one core. I tried with mp4/h264-5; webm/VP9; mkv/h264-5 e Prores. A 45 min video takes 3h 30m. I tried adding the parameters "threads=15", "wpp" which should be active by default and "frame-threads=3"; but the result is the same. On average I do 15 fps. Using h264-5 with nvenc takes 1h20m; but the CPU still uses only one core. On average I make 115 fps. Using an external engine (handbrake, which uses ffmpeg) you can use both the Cpu and the GPU; the rendering will take 10m! (but with lower quality). Since I'm compiling CinGG (note: all threads are used for compiling), maybe I need to enable some flags or something like that? Are there any customizations to do? Or should I set something in the operating system? Another question: How do you configure the render farm to use only the local CPU cores?

3 13