Page MenuHomeSolus

Update Cinelerra-GG to 5.1.2019.09.30
ClosedPublic

Authored by Jacek on Sat, Oct 5, 7:44 PM.

Details

Summary

System (non-static) builds are finally fixed, which means it now uses more system libraries instead of static ones.
Added Crop & Position plugin
Vaapi acceleration fixed
A whole lot of UI improvements and bugfixes
Full changelog here: https://cinelerra-gg.org/download/releasenotes.pdf

Test Plan

Edited a short video and played around with effects.
Tried rendering to multiple formats.
Tested vaapi acceleration.

Diff Detail

Repository
R4773 cinelerra-gg
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

Jacek created this revision.Sat, Oct 5, 7:44 PM
Jacek requested review of this revision.Sat, Oct 5, 7:44 PM
Jacek added a comment.Sat, Oct 5, 8:02 PM

So this is first time since I started packaging that it correctly does system builds. By default it uses almost all system libraries, apart from A52, FFMPEG and its reverse dependencies.
This is the first time that I can actually force it to use system libraries even for those, but I don't know if this would be the right way. They are key components and there probably is a reason the devs forced them to remain static even for system builds. We are often in front or behind with FFMPEG compared to what they are shipping (currently 4.2, us 4.2.1), and they have to blacklist specific effects that aren't compatible with each new version of FFMPEG.
Should I try to force more system libraries, which will mean more testing and possible problems when FFMPEG gets updated, or should I stick with what we currently have?

JoshStrobl accepted this revision.Fri, Oct 11, 2:41 PM
JoshStrobl added a subscriber: JoshStrobl.
In D7326#116341, @Jacek wrote:

We are often in front or behind with FFMPEG compared to what they are shipping (currently 4.2, us 4.2.1), and they have to blacklist specific effects that aren't compatible with each new version of FFMPEG.
Should I try to force more system libraries, which will mean more testing and possible problems when FFMPEG gets updated, or should I stick with what we currently have?

Given they're blacklisting specific effects, I'd say no and to keep cinelerra using a static ffmpeg.

This revision is now accepted and ready to land.Fri, Oct 11, 2:41 PM
This revision was automatically updated to reflect the committed changes.