- Cin - Cinelerra-GG Mailing Lists

Qt6 Alpha 2026-10-22 ready for testing, native Wayland included
by Sam 26 Oct '26

26 Oct '26

Hi everyone, A new Qt6 alpha build is up, dated 2026-10-22. It is ready for you to test. Download (two AppImages, pick one): https://download.cinelerra-gg.org/?path=qt6-alpha&sort=date_desc - CinGG-qt6-alpha-20261022-x86_64.AppImage: for current distributions (glibc 2.38 or newer, e.g. Fedora 40+, Ubuntu 24.04+). - CinGG-qt6-alpha-20261022-anylinux-x86_64.AppImage: brings its own glibc and runs on older systems as well (tested on Ubuntu 16.04, 22.04 and Debian 12). A .sha256 file sits next to each. Help → About should show "built: Oct 22 2026". What's new since 2026-10-19: - Native Wayland support. This is the main thing we'd like you to try. - Mirror effect: no more garbage when the reflection center is near 50 %. - Sketcher and plugin parameter panels: one line per parameter, no horizontal scroll bar, theme accent colours. - Floating docks can be docked again from their title bar menu. How to test native Wayland: By default Cinelerra still starts through XWayland, even in a Wayland session. To run natively, start it like this: CIN_QPA_PLATFORM=wayland ./CinGG-qt6-alpha-20261022-x86_64.AppImage The terminal prints which platform was chosen. Please tell us which desktop you used, e.g. KDE Plasma, GNOME, Sway or Hyprland. So far we have only tested under KWin, so the others matter most to us. Things worth trying under Wayland: - dragging clips from Resources to the timeline, the viewer and the bins - floating docks: detach, move, re-dock, restart - dialogs and popup menus: do they open in the right place and stay in front? - Alt+T drag box, colour picker, right-click menus in older plugin windows - fullscreen Known issues, no need to report them: - Screen capture does not work under native Wayland yet. - On exit under Wayland, cin may print a "core dumped" message. - A floating dock can flicker once at startup. - Once the mixer window is behind the main window, there is no menu entry to bring it back. Please report bugs in the "Qt6 Alpha" category of the bug tracker: https://bug.cinelerra-gg.org Please include your distribution, your desktop, whether you ran native Wayland or X11, and the terminal output if something goes wrong. Thanks a lot for testing! Sam

4 4

Re: QT6 AppImage feedback discussion
by Sam 20 Oct '26

20 Oct '26

Hi Andrea, hi Igor, hi Andrew, this time one mail for both threads, so nothing gets lost in between. The new AppImages of 2026-10-19 are online, and the source in the git repository is at the same state: |https://download.cinelerra-gg.org/?path=qt6-alpha&sort=date_desc| Andrea, your reports of the last days led to five fixes, and all of them are in these AppImages. Mirror: two things came together. The sliders and number fields of the Reflection Center only work while "Enable Reflection Center" is checked. That is the same in CinGG 5.1, but in the Qt6 build a disabled slider still looked active. Disabled sliders are grey now, in every plugin. The second one was a real bug: digits typed into a number field of a plugin went to the main menu, so "2" or "7" switched views of the timeline instead of changing the value. Now the field gets them, Ctrl+A included. One thing remains, and it is the same code as in 5.1: Mirror rewrites its field after every key, so a number typed digit by digit can come out wrong. The mouse wheel over the field and the slider work fine. Window sizes: you found a bug. The program saved the sizes on exit but lost them at the next start, because it restored the layout before the main window had its final size. Now the sizes come back after a restart, and each workspace keeps its own. With "Save Layout..." you can also store a layout that "Reset to Saved Layout" brings back at any time. Tool bar of the timeline (Mantis #679): when the Compositor takes the space, the buttons that don't fit move behind the » button at the right end of the bar. On the dark theme that button was nearly invisible. Now you can see it, and a click shows the hidden buttons, Drag and Drop and Cut and Paste among them. A second row of buttons I have not done. Sketcher: it works in the Qt6 build now and is in the new AppImage. Chroma Key: I have noted your suggestion. Wayland: you were running on XWayland. The AppImage always starts on X11, also in a Wayland session, and it ignores QT_QPA_PLATFORM on purpose, because native Wayland is not tested enough yet. To try native Wayland, start it like this: |CIN_QPA_PLATFORM=wayland ./CinGG-qt6-alpha-20261019-x86_64.AppImage| One way to tell the difference: run xprop in a terminal and click into the Cinelerra window. On XWayland it prints the properties of the window. A native Wayland window it cannot pick, so nothing happens. Older systems (Igor's Ubuntu Studio 16.04, and Andrea's idea of a Flatpak): we went the Anylinux way that Andrew suggested. There is now a second AppImage that brings its own glibc and all libraries, so it does not depend on the libraries of the system: |CinGG-qt6-alpha-20261019-anylinux-x86_64.AppImage| In containers it starts, loads all plugins and renders on Ubuntu 16.04, Ubuntu 22.04, Debian 12, Fedora rawhide and Ubuntu 26.04. A real Ubuntu 16.04 machine with its old kernel I could not test. Igor, if you like to try it, I would be glad to hear whether it starts on your system. Andrea, so there is no need to build a Flatpak yourself. Now to the patches for the stable version, from the thread "Cherry-pick from cinelerra-qt6?". Andrew, thank you for applying them to master and testing them in your VM, and for showing Andrea how to apply them with git am. About MPEG I have to correct my last mail. I wrote that 1280x720 on 4 processors should break. That is only true for progressive frames. By default the encoder works interlaced, and then 720 lines become 46 macroblock rows, which split into 4 bands of 12 without a gap. So your file would have been fine without the patch too. I checked it here: 1280x720 in 4:2:2, with and without the patch, on 4 and 16 processors (a small shim made the encoder see 4), interlaced and progressive. Only one of the eight files is broken, the progressive one without the patch on 4 processors: ffmpeg reports 149 errors ("overread", "MVs not available"). With the patch the same file is clean. By the formula, 352x288 and 176x144 on 8 processors and 720x576 on 5 or 7 break in both modes, so those make better tests. Every progressive file, with and without the patch, also gets "interlaced frame in progressive sequence, ignoring" from ffmpeg. That is an older problem and has nothing to do with the patch. The index-related errors I could not reproduce. CinGG 5.1 and the Qt6 build loaded all eight files without a single error message, through FFmpeg and through libmpeg3. Could you send me the exact lines? Then I can look where they come from. Andrea, thank you for building with the patches, that helps a lot. MPEG 4:2:2 working on your machine is good news. DPX: the error comes from the FFmpeg preset DPX.dpx, not from the patch. That preset writes a sequence of images and needs a numbered file name, as its own comment says, for example: |/home/paz/puppa/aereo_test%05d.dpx| The patch is for Cinelerra's own DPX writer. To test it, choose "DPX Sequence" as the file format in the render dialog instead of FFMPEG. GIF: the same applies here. gif.gif is an FFmpeg preset, and FFmpeg writes that GIF itself, so the patch is not used. To test it, choose "GIF" as the file format instead of FFMPEG. Opened in a browser, the GIF should then play at the speed of the project and loop. Without the patch it runs too fast or shows only the first image. Sam

3 2

Cinelerra-GG Qt6 alpha: Sketcher now draws right in the Compositor
by Sam 19 Oct '26

19 Oct '26

Hi everyone, Sketcher, the drawing effect of Cinelerra-GG, works quite differently in the Qt6 alpha now. You draw and edit right in the Compositor, the way you would in a drawing program, and all settings sit in one panel of the Effect Inspector. Here is a short tour with pictures. The AppImages of 2026-10-19 have it: |https://download.cinelerra-gg.org/?path=qt6-alpha&sort=date_desc| The film in the pictures is the Sintel trailer, © copyright Blender Foundation | durian.blender.org, licensed CC BY 3.0. 1. Getting started Put Sketcher on a video track like any other effect and open it in the Effect Inspector. The Compositor then shows a green *Sketcher* button and the Sketcher tool bar. A click on the green button pauses Sketcher, so the other Compositor tools get the mouse again. The switch *Edited in compositor* at the top of the panel does the same. The main window: Sketcher on the timeline, three curves in the Compositor, the Sketcher panel in the Effect Inspector For this picture I used the FX workspace and made the right column a little wider. Everything is docked. 2. The tool bar The green Sketcher button and the Sketcher tool bar of the Compositor From left to right: *Select (V)*, *Pen (P)*, *Freehand (B)*, *Rectangle (R)*, *Ellipse (E)* and *Arrow (A)*. The letters work while the pointer is over the Compositor. Then come the two modes of the pen, the buttons that show the handles and the box, and colour and width. Colour and width change the selected curve. With nothing selected they are the defaults for the next new curve. The second row holds smoothing and stabilizer for Freehand. 3. Drawing * *Pen:* a click sets a corner, a drag pulls out handles, a click on the first point closes the shape. Enter, Escape, a double click or a right click finishes the curve, Backspace takes the last point back. In the mode *Auto* every click sets a point that rounds itself. * *Freehand:* just draw. The stroke comes out smooth, and ending near the start closes it. * *Rectangle, Ellipse, Arrow:* drag to draw. Shift gives a square, a circle or a 45° line. A plain click makes a shape of default size. After a curve is finished, the Select tool is active again. The pen draws a curve: one corner, one point with handles pulled out, a dashed preview up to the pointer The line at the bottom of the Compositor always tells you what a click or a drag does right now. 4. Editing Point at something and it reacts: a point grows, and the hint line names what a click, a drag or a double click will do. The pointer over a point of the ellipse, the point has grown, the hint line explains the mouse buttons * Drag a point to move it, drag a handle to shape the curve. * Drag an edge to bend it. Shift + drag moves the edge parallel. * A double click on an edge inserts a point and leaves the shape as it is. A double click on a point switches between a sharp corner and an automatic round point. * Drag a frame around several points to select them. A box with 8 handles appears: a handle scales, just outside a corner you rotate, inside the box you move. The cross in the middle is the pivot, and you can move it. * Arrow keys move the selected points, Shift + arrow in steps of 10. Delete removes them, Escape deselects. * Ctrl+D duplicates the selected curve. * Every finished action is exactly one Ctrl+Z step. Three points of the ellipse selected with a frame, the box with its 8 handles and the pivot The handles show the point type: a corner is a diamond, smooth is a square, symmetric is a square with a dot, automatic is a circle. If you find them too small, Settings → Handles in the panel has Large and Very large. A right click on a point opens a menu with everything for the point and its curve: The right click menu: point type, round corner, delete point, closed, fill, arrowhead, duplicate, order, hide, lock, delete curve 5. The panel The Sketcher panel in the Effect Inspector with the groups Layers, Selection, Curve, Track motion, Point list and Settings * *Keyframe row:* jump to the previous or next keyframe. The diamond sets a keyframe at the playhead. * *Layers:* one row per curve, the top row is in front. Drag a row to change the order. The eye hides a curve, the lock protects it, a double click renames it. A click on a row selects the curve in the Compositor, and the other way round. * *Selection:* buttons for the point type and for straight or curved edges, plus insert, delete, break and join. The line below explains the button under the pointer. Position X and Y place a point exactly, Round corners rounds a corner. * *Curve:* colour (with an eyedropper that takes the colour from the picture), opacity, width, the tip of the line, open or closed, fill, arrowhead and write-on. With nothing selected this group is called "Defaults for new curves". * *Track motion:* follows the selected points through the picture and writes keyframes, either on every frame or reduced. One run is one undo step. * *Point list:* the old table of points, folded away. A click on a row selects the point. * *Settings:* anti-aliasing and the size of the handles. Both apply to all curves. 6. Animating with write-on Write-on draws a curve bit by bit. Set a keyframe where the drawing should start and pull "to" down to 0 %. Set a second keyframe where it should be complete and put "to" at 100 %. In between, Cinelerra draws the curve step by step, and the arrowhead travels with the tip. The arrow half drawn at 0:00:01:18 and complete at 0:00:02:00 And this is what the render looks like, without any handles: A rendered frame: a yellow arrow points at the young dragon, a red ellipse around it, a white line below 7. Old projects Projects with Sketcher from CinGG 5.1 load and look exactly as before. There is one intended change: three or more automatic points exactly on one line now give a straight line instead of a small bulge. Closed shapes, fill, arrowheads and the round tip are new. How an older CinGG shows a project that uses them has not been tried yet. Known things * The mouse wheel over the picture steps frames as before. Zoom with the zoom control. * While Sketcher edits and the pointer is over the Compositor, V and B pick Select and Freehand. Splice and Overwrite don't react to them there. * Wide translucent lines look almost opaque, the same as in CinGG 5.1. * So far it has been tested on virtual X displays. Real desktops and HiDPI screens are where your help counts most. If something behaves differently from what I describe here, please tell me what you did, what you expected and what happened. A screenshot helps a lot, and so do your distribution and desktop. Sam

1 0

QT6 AppImage feedback discussion
by Phyllis Smith 19 Oct '26

19 Oct '26

Starting new queue for QT6 discussion (so ii does not end up under "Silly Question" que!). Downloaded the AppImage and really enjoy how moving the windows works. Played my standard test video/audio all the way with no issues. It looks and feels so much more flashy and not as stodgy. More to follow. THANKS SO MUCH to Sam for all of his current work and there is probably a much longer way to go!

8 32

SGI O2 machine got NVME, edits video!
by Andrew Randrianasulu 19 Oct '26

19 Oct '26

https://m.youtube.com/watch?v=46wxttvq9qY "VCF Southwest 2026, But Edited on Silicon Graphics for ’90s TV" More semi-offtopic, but I never saw this specific NLE/Compositor in action, so now you too can "waste" 30 minutes of your life ;)

1 0

OT question (KDE/X11)
by Andrea paz 18 Oct '26

18 Oct '26

KDE 6.8 is coming out next week, and it removes XOrg, keeping only Wayland and XWayland. I wanted to keep both graphics servers so I could switch between them whenever I wanted. I found SonicDE (https://sonicde.org/) which is a KDE fork that keeps X11 and removes Wayland. However, as I understand it, it removes the KDE login manager (plasmalogin.service) and replaces it with Sonic Manager (soniclogin.service). So, I think I’d lose KDE/Wayland. Is it possible to keep both so that, when I start up my PC, I can choose which desktop environment to boot into?

3 4

Cherry-pick from cinelerra-qt6?
by Andrew Randrianasulu 17 Oct '26

17 Oct '26

https://git.cinelerra-gg.org/?p=sam/cinelerra-gg-qt6.git;a=commit;h=f6f2f02… "MPEG 4:2:2: encode every macroblock row on any processor count" Yes, this is AI (Claude) assisted but I think we can trust Sam? I do not have this big host to test (may be -smp 16 will work with kvm, it worked with 8)

4 9

Going down the video editing CPU ladder ...
by Andrew Randrianasulu 16 Oct '26

16 Oct '26

https://68kmla.org/bb/threads/58-year-old-risks-life-unicycling-to-prove-35… I guess I can only wish Good Health at any age for all of us ... Unfortunately, I myself probably will not risk riding even bi-cycle!

3 2

Anylinux appimages
by Andrew Randrianasulu 15 Oct '26

15 Oct '26

Hello, all! I was re-visiting those anylinux appimages suggested some time ago, and I made test appimage from qemu-system-ppc64 fork (you probably need -L to point it to keymaps and such, and -bios to point it to openbios-ppc build,specific to this fork) https://drive.google.com/drive/folders/1IBj91aP-mqZ8O2Hwjh6QjkBOGFhoYBFt?us… I wonder if Andrea,as our long time Arch user can make experimental Appimage of classic cingg, so we can test it on variety of systems? https://github.com/pkgforge-dev/Anylinux-AppImages/blob/main/HOW-TO-MAKE-TH… Of course if you have time/desire to test-run this workflow. My uneasiness comes from fact scrip downloads some prebuild libs and runtimes and appimagetool, too. May be run it in chroot/container/VM? I ran it in not so important chroot from flash drive ...

3 9

Cinelerra-GG Qt6 port: alpha AppImage and source are online
by Phyllis Smith 12 Oct '26

12 Oct '26

Hi everyone, as you have already heard, Sam is porting Cinelerra-GG from its own X11 toolkit to Qt6. An alpha AppImage and the source are now on the Cinelerra-GG server: AppImage: https://download.cinelerra-gg.org/?path=qt6-alpha Source: https://git.cinelerra-gg.org/sam/cinelerra-gg-qt6.git Overview: https://www.cinelerra-gg.org/en/download Please read this first: - This is an alpha. Please do not use it for real projects. - The stable Cinelerra-GG continues as before. The port is developed in parallel and replaces nothing. - It uses the same settings folder as your normal Cinelerra (~/.bcast5). Make a copy of that folder before you start it. To start it: chmod +x CinGG-qt6-alpha-20261010-x86_64.AppImage ./CinGG-qt6-alpha-20261010-x86_64.AppImage Reports are very welcome. Please use the bug tracker at https://bug.cinelerra-gg.org and pick the category "Qt6 Alpha", so that reports about the port stay apart from reports about the stable version. A screenshot and the name of your distribution help a lot.

1 0