- Cin - Cinelerra-GG Mailing Lists

Keyframe Adjustments Not Seen in Render
by Mark Goldberg 29 Jan '22

29 Jan '22

I've added a couple keyframes to adjust the curves in Histogram Bezier at the end of a clip. When I play in the compositor I see the change (lower highlights as I pan into a scene lit by the sun) as expected. When I render, either background rendering or a full render for output, it seems the changes are ignored and the curves don't change with time. Am I missing something? Regards, Mark

2 8

Fwd: Webpage Translation into Spanish
by Rafa Mar Multimedia en Gnu\Linux 28 Jan '22

28 Jan '22

Hi dear Phyllis Spanish translation of the terms of the appearance tab of the configuration: Autosave continous backups = *Copia de seguridad continua* The tip in Spanish = *Cuando cierre Cinelerra se guardarán unicamente las últimas 50 copias de seguridad. Si trabaja durante mucho tiempo sin reiniciar Cinelerra, corre el riesgo de ocupar mucho espacio con las continuas copias de seguridad.* Greetings!!

4 7

Feature discussion for linear editing
by Stefan de Konink 28 Jan '22

28 Jan '22

Recently I found a very nice introduction on linear editing for multi-cam. I finally understood how it should work in Cinelerra GG. But it is not intuitive, I would like to propose two things that could make multi-cam editing much more user friendly. <https://www.youtube.com/watch?v=rOMKP4Jgzw8> 1. As you can see from the video, multi-cam works by clicking on a Mixer. Completely counter intuitive towards anyone that works with a switcher (atem and likes) it adds video from the undecided point up to the current position when clicked on the mixer. This would be a feature request that I wonder why nobody asked for this: implement this in the opposite way. You click on a mixer A, then the timeline gets filled with that mixer (visible, or underwater). If you click on mixer B, the timeline is computed with the part 0 to timeline current position with Mixer A, and having Mixer B as start position. 2. Now you have set up your rough cut. What you would actually want is the ability to fine tune. I would like to have a drag handle functionality that would be able to modify the cut position. It should be able to move to left or right. The limits of this operation are bound by the source videos. One can move to the left beyond the left video, but only up to the point that the right video has data. The same goes for the move towards right. At this moment you can never get this right with trimming or extending, especially not when there is an audio track to match it below. Hence I think this function would benefit every editor. (feature-mouse.png) -- Stefan

4 10

Video Transitions not locking into track?
by Stefan de Konink 27 Jan '22

27 Jan '22

I am using a recent git version of Cinelerra, and I notice that I cannot drop a video transition between two pasted clips anymore. So I do see the white square as placement, but the icon after it does not follow. Neither is the transition visually applied between the two clips. (I have also seen the case where the icon isn't there, but the transition happens, but not today.) -- Stefan

3 5

Ligature rendering in the title effect
by Stefan de Konink 26 Jan '22

26 Jan '22

Within Cinelerra the Title effect does not seem to have the same result for the same font. The rendering backend within Inkscape gives ligatures and cursive connections of the Parisienne in an ideal way. Cinelerra does not join the letters. The font used; <https://fonts.google.com/specimen/Parisienne> The individual renderings, notice the broken connection between the 'a' and 'n'. -- Stefan

3 9

Again bugs in alignment
by Stefan de Konink 24 Jan '22

24 Jan '22

In the attached screenshot you can visually see where the original cut has to start at 00.720, while it appears at the rendered version at a little more than 0.200. Yes, I had to introduce this silence to prevent the audio being cut off from the beginning. The source material of this project can be made available in full. -- Stefan

4 9

Re: [Cin] Crash on playback
by Phyllis Smith 21 Jan '22

21 Jan '22

Mark, > > It does not crash when using X11 OpenGL, only X11. X11 with direct render > does not seem to be faster when using vdpau, so I think I have a workable > solution that does not require extra tracks. > Curiouser and curiouser. I checked and I was using X11 and not OpenGL. I have created a multibit AppImage on my Fedora 29 computer(which is an HP/Intel/Broadwell graphics board) and have uploaded it. When I tested this AppImage moved to an AMD Ryzen-7 (with a Radeon graphics board) vdpau worked for me on tutorial.mp4 file. It did not work with DSCF0220.MOV though probably due to limitations of my board. When you have time and the inclination, you should see if it works for you by downloading: https://cinelerra-gg.org/download/testing/cin-x86_older-distros_multibit.Ap…

2 3

Re: [Cin] Crash on playback
by Phyllis Smith 21 Jan '22

21 Jan '22

Mark, > If you get vdpau working, could you build a multibit version appimage for > older systems? That would cover all my use cases. > Yes, that would be easy IF I get vdpau working. > > I shared a sample file. You should be able to download the original file > from this link also: > As expected, no crash while playing on Fedora 29 (with same glibc and kernel version level). Maybe I will try installing RHEL8 out of curiosity). Trying to fix something when I can not reproduce it, is impossible. Also, when booting my old Fedora 29, I noticed there is another partition labeled Fedora 29 - Cuda development so that should prove helpful. > >

1 0

Re: [Cin] Crash on playback
by Phyllis Smith 19 Jan '22

19 Jan '22

Mark, Now that you have found a workaround, I do not know if you want to continue to work on resolving this. If so, don't bother reading the rest of this. Or how much more time to test you want to do. Depending on your goal: ?? do you want to build yourself (if so, I have Fedora 29 on a partition and am compiling my latest CinGG tar there right now to see if I can reproduce the error you are getting. It has the same kernel of 4.18 as RHEL8 and glibc of 2.28 as you mentioned - Fedora 28 is earlier than that). I could also try to download RHEL8 as a developer for free but I don't know how far I would get with that and reproducing the error. ?? OR would you prefer to just use AppImage if vdpau worked? (if so, I can work on trying to figure out a solution because others have the same issue). ?? have you tried this easy test of using the default configuration file to make sure indexes are rebuilt and there is nothing strange in your cinelerra_rc file? ,.e. CIN_CONFIG-/tmp/bcast1 ./bin/cin About: > compiled it. It worked for a while but now it crashes with the following > when I hit the play button. There were some system updates installed in the > interim. > ?? is it possible that the system updates included a technology called pre-linking, which supposedly "speed up a start of a binary which uses dynamically loaded libraries by linking these libraries in advance ("prelinking" the executable file) using the 'relocating' technique. This basically means that each time the binary is run, the shared libraries are loaded to a randomly chosen memory addresses, which may sometimes interfere with the addresses at which the program shared memory segments are to be attached." The reason I ask is because when I look up the error message you first reported of "could not attach shared memory" it talks about this error and a solution as follows: Per the internet, you can disable prelink by editing /etc/sysconfig/prelink (set PRELINKING=no), then run /etc/cron.daily/prelink so the prelinking of the libraries in the system will be disabled. Fedora and Red Hat Enterprise Linux (RHEL) supposedly enable pre-linking by default which means I have been using it that way for years without a known problem. But I do not see a file called /etc/sysconfig/prelink on my Fedora 32. RHEL8 uses glibc 2.28, kind of annoying they stayed there as many newer > things want a later version. They have a habit of backporting things > though, including kernel changes, such that the conditional compile based > on versions sometimes fails and a special case for a Redhat kernel needs to > be added. Who knows if they backported something in glibc? > > >> If I set the compiled version to not use any hardware accel, it still >>> crashes. I don't think the vdpau issue and the crash are related. The crash >>> is my big concern obviously, as any work not saved is lost. >>> >> > Why would it not crash if there is another video on the timeline below > what I am playing? At least that is a workaround. It can be another copy of > the same track. > Good question! > > Thanks for taking up the mantle of the open source Cinelerra gg. I was > very peripherally involved with Cinelerra CV in 2011. I provided a patch > for SOWT audio and communicated with Einar at that time. I see that is now > handled by ffmpeg. > We just want to make sure Cinelerra lives on and stays relevant after all of the hard work you and many, many others have done !

1 0

Colors [was: Crash on playback]
by Andrea paz 18 Jan '22

18 Jan '22

@Andrew > @Andrea, for some reason I can't download attaches from forum (because I have no login there?), can you add CMS.txt as attachment to email (again)? I'm opening a new email because color has nothing to do with the Vdpau/Vaapi issues. It was just an attempt to put together all the information on how CinGG treats color. Lately I found emails from Hermann Vosseler that are very indicative. However, the fact remains that each plugins of CinGG treats the color in its own way, so we should find a way to understand how all the native plugins act, one by one (if I'm not mistaken, the plugins of ffmpeg clip everything to 8-bit and sRGB). Only with this information can we reconstruct a chain of steps that accounts for color transformations and, perhaps, keep them under control. Sorry, I've been pushing too much color lately, it's best to let it go. Hermann already knew in 2012 that it was not possible to treat it in CinCV and that's also why he went for Lumiera.

3 3