May 2020 - Cin - Cinelerra-GG Mailing Lists

Fwd: Re: [Libav-user] NV12->RGB24 vs YUV420P->RGB24
by Andrew Randrianasulu 21 May '20

21 May '20

Is there anything relevant for Cin's internal working (in case when hw decoder is used)? ---------- Пересланное сообщение ---------- Тема: Re: [Libav-user] NV12->RGB24 vs YUV420P->RGB24 Дата: Четверг 21 мая 2020 Отправитель: Alex Agranovsky <alex(a)sighthound.com> Получатель: libav-user(a)ffmpeg.org Going NV12->YUV420P->RGB24 instead of NV12->RGB24 made a material difference, thanks! On 5/20/20 3:10 PM, Carl Eugen Hoyos wrote: > Am Mi., 20. Mai 2020 um 20:36 Uhr schrieb Alex <alex(a)sighthound.com>: >> I've been working on implementing hardware decoder integration. While >> things generally are working, there's not much gain: the color >> conversion from NV12 seems to be dramatically more expensive than from >> the YUV420P in case of software decoder. >> >> When profiling, I'm seeing YUV420P->RGB24 using yuv420_rgb24_mmxext >> (which barely registers in profiler), while NV12->RGB24 using >> yuv2rgb24_X_c, which takes a fairly dramatic amount of time. >> >> Is that something that is expected? A known problem? Or perhaps >> something is wrong on my side of things? > Very, very generally, hardware decoding is very useful if you want to > display on the same gpu where the decoding takes place and if you > want to encode on the same gpu where decoding happens. > > If you have to download the decoded frame from graphics memory > to cpu memory, some of the possible gains are always lost. > If you - in addition - need a colour space conversion (in your case, a > conversion that rarely happens when using a software decoder which > is therefore not so well accelerated), even more time is lost. > > That being said: Did you try to first convert nv12->yuv420p > using ff_nv12ToUV_avx, then using above yuv420_rgb24_mmxext ? > I would have expected nv12ToUV to be much faster than any yuv2rgb > conversion. > > Carl Eugen > _______________________________________________ > Libav-user mailing list > Libav-user(a)ffmpeg.org > https://ffmpeg.org/mailman/listinfo/libav-user > > To unsubscribe, visit link above, or email > libav-user-request(a)ffmpeg.org with subject "unsubscribe". _______________________________________________ Libav-user mailing list Libav-user(a)ffmpeg.org https://ffmpeg.org/mailman/listinfo/libav-user To unsubscribe, visit link above, or email libav-user-request(a)ffmpeg.org with subject "unsubscribe". -------------------------------------------------------

2 5

Tracking (or tracer?) control points
by preobraz＠gmail.com 20 May '20

20 May '20

Hi all! In the video (watch from 1:13): https://www.youtube.com/watch?v=3kzKhedIX1o shows how a clip is inserted into a chromakey area. I looked at the Tracer effect in Cinelerra-gg, but I still did not understand whether it was possible to perform a similar task with it. If there are no such instruments in Cinelerra-gg - maybe try to adapt the Motion effect to the task? I think solving this issue will add cinelerra-gg even more professionalism. For information: in Adobe After Effects,Screen Replacement & Motion Tracking solves this problem. Example: https://www.youtube.com/watch?v=JJmvrNmso5Y -- Ugin

6 20

Linux GUI on Windows
by mat 20 May '20

20 May '20

According to https://www.theregister.co.uk/2020/05/19/wsl2_gui_linux_apps_windows/, Windows10 will get a WSL2 which support Linux GUI applications. Maybe this allows Cinelerra-GG to run under Windows. MatN

3 2

question about Ubuntu 20.04
by Dragonfly 19 May '20

19 May '20

Hello, I'm not sure if I should ask here or in the forum. I need to know if there will be a Cinelerra package for Ubuntu 20.04. I am using Ubuntu Studio 18.04, but I have had a few issues with it and they also advise to upgrade to Ubuntu Studio 20.04. I have a video project to work on shortly and ideally would prefer to upgrade first. At the moment, you have a specific package for Ubuntu 18.04 but not 20.04. Will there be one for 20.04 soon? You do seem to have a single user build for 20.04 but will I encounter any issues if I install this? Finally if I am using an AMD quadcore cpu can Cinelerra be set up to use more than a single core? Thankyou, Tanya

5 4

Valgrind
by Andrea paz 17 May '20

17 May '20

To thank GG, I offer a Valgrind made with the new release, with the modifiability of the audio track height. PS1: I also tried to run CinGG with gdb (# gdb ./cin) but it opens the gdb shell waiting for commands and does not start CinGG. How to do it? PS2: I also take this opportunity to thank Sergio for the optimizations and improvements he makes to the manual.

3 8

SUV theme
by Igor BEGHETTO 17 May '20

17 May '20

Hi! Working on my personal theme I updated some icons, made by me time ago for the community, for consistency with the SUV theme. I added a compressed file with the icons. They only affect the background icons. If you think they are better, you can overwrite the old ones. Thanks! IgorBeg

1 0

Manual update
by Andrea paz 10 May '20

10 May '20

Yet another review of the scopes.

2 3

April monthly tars and pkgs are now available ...
by Phyllis Smith 01 May '20

01 May '20

April monthly tars and pkgs are now available at the usual place on the website: https://cinelerra-gg.org/download/tars https://cinelerra-gg.org/download/pkgs We installed both the Mint 19.3 package and the new Ubuntu 20 package to make sure Cin came up. Both Arch and Tweed (Tumbleweed) distros were updated yesterday before the build. And if you have not already seen, the *beginning of the Spanish translation of the manual by Sergio*: https://cinelerra-gg.org/download/CinelerraGG_Manual_Spanish.pdf (I did not get the update from Andrea and the fixes from Sergio in the English manual yet but will try to get that updated by the end of today.) *Newly added Ubuntu 20* is available with only minimal testing. Ubuntu 19 static tar is available this month yet but will be retired next month unless the demand is still there. *Fedora 32 was newly added* also. --------------------------------- *Text copy of releasenotes.pdf (also on website*) ------------------------- Cinelerra-GG (Version Infinity) Release Notes for 04/01/2020-04/30/2020 for builds Thanks to *RafaMar* for a lot of work testing this month, reporting bugs, providing instructive youtube videos and tutorials, plus more Spanish translations. A partially translated Spanish version of the Manual is being gradually worked by *Sergio*. This is very much appreciated. It is at: https://cinelerra-gg.org/download/CinelerraGG_Manual_Spanish.pdf 1. Four *potential performance modifications* have been made to speed up some places, to include: 1) Speed improvements for *line drawing* using Bresenham’s line algorithm implemented now in (motivated by LFOM forum notes). 2) Performance enhancements on the time line for *video/audio re-draws* has been implemented. 3) *Threading on loads* so that Audio and Video can be loaded using multiple cpu-s. Previously the video load to the timeline would have to complete before the audio would start loading. 4) *Hardware acceleration using vdpau* for files of type yuvj420p were reverting to software decoding on the load due to rejection by ffmpeg. Another ffmpeg patch (patchA) was added to allow this type (used by GoPro cameras) to be decoded successfully on GPU graphics cards that support CONSTRAINED_BASELINE (*Ig0r in the forum pursued this* to a fix). 2. *Videoscope *additional improvements to ease use in Compositor and Viewer and as a plugin. - Smoothed vectorscope so no longer uses fast pixmap but instead software (Sam aesthetics suggestion). - Added VectorWheel overlay options – none, All, Hue, IQ (with I for skin tones and Q for grass?), and user generated allowance by adding to CinPath/plugins/scopes as a png file (Andrea and IgorBeg provided initial quality graticules). - Modifications were made to layout to improve looks & usage (as recommended by IgorBeg/Sam). - Switched the Hue and Saturation values from the top line to a popup instead. - Added a “*Refresh on Stop*” button so that the scopes are only updated when you actually stop the play. This makes it play at full speed (Sam suggestion). Works only for Compositor/Viewer. 3. A *long standing serious bug* which has been undetected for years is resolved (thanks to RafaMar analysis of exact steps to reproduce.) For details refer to BT #71, note 3228 +. 4. *Usability Improvements:* Switched from png to 90% jpg for *ShapeWipe transitions* to save binary file size for the monthly builds in order to lessen amount of time to download. Writing software to perform the jpeg translation was necessary to do so. This also makes additional 17 shapes available (RafaMar). If user needs to use a png version of a ShapeWipe instead, the manual states how to do so. Added to *BoxBlur *plugin, a way to define a rectangular area for blurring just that spot (Andrea). *Drag box ungrab for plugins* like Title will now automatically turn on the Drag and turn off the Drag owned by any other plugin (RafaMar suggestion). *Collect and Paste effects *options are now available as well as saving a stack to the Clip folder (Sam suggestion BT #84). MMB on a track to see. More work is to be done to complete this next month. Updated Spanish translation and tips (by RafaMar). 5. *Bugs/Issues fixed:* Problem of Title plugin with long lines or using png with the menu has been fixed (Rafa reported). Camera and Projector “expand X,Y,Z ranges” have been fixed and changed to work a little differently but more work needs to be completed (Andrea reported problems). Button bars on Compositor and Viewer are now more aesthetically correct and the “meters” icon has been moved to the end for a better placement of a non-edit option (Olaf and IgorBeg notes). Some problems with BoxBlur to include edge case segv have been fixed (IgorBeg). Scaling problems for xinerama case of a screen that is 2560x1080 will now work correctly (RafaMar user reported). Fixed booby lock problem in ChromaKey plugin. Negative value vdpau/vaapi hardware fallback fix. *With vaapi enabled, some png’s and jpg’s would not default to loading with software*. Most of these will now do so (*LFOM report *in the forum). A bug has been fixed in theora configure.ac (as provided by Andrew). Bug in using the next keyframe with the shortcut of “k” was not working if effects not at the beginning but is now fixed (RafaMar found). Color Wheel Hue up/down toggle needed to be float as was not working quite right. Removed “commercials” linking due to lack of use and in particular for the monthly builds which will speed up the process. If building your own, you can put it back in. Added requirement to “build prepare” script for Python. This was found necessary for Ubuntu 20. Fixed capture device needed for Recording operations. This was a dropped line. Colorpicker Hue correction has been made in 2 different places (GG found one and IgorBeg). Correct alignment for Cakewalk and different themes for BoxBlur contributed by programmer.

2 1