- Cin - Cinelerra-GG Mailing Lists

Cinelerra-GG Qt6 alpha 2026-11-01: new effect panels, please test; scene catalog; fixes
by Sam 07 Nov '26

07 Nov '26

Hi everyone, a new Qt6 alpha is online, built on 2026-11-01. The main thing this time is a request: ten more effects have new native panels, and I would like you to test them thoroughly. It also brings a scene catalog and the fixes for what you reported since the last alpha. Download (sorted by date, the newest on top): download.cinelerra-gg.org <https://download.cinelerra-gg.org/?path=qt6-alpha&sort=date_desc> * CinGG-qt6-alpha-20261101-x86_64.AppImage <https://download.cinelerra-gg.org/files/qt6-alpha/CinGG-qt6-alpha-20261101-…>, sha256 |89fd92809b97d77e6250d5485ce68fd60bda2545cc1278410faf5a67e1696f7b| * CinGG-qt6-alpha-20261101-anylinux-x86_64.AppImage <https://download.cinelerra-gg.org/files/qt6-alpha/CinGG-qt6-alpha-20261101-…> for older systems (it brings its own glibc), sha256 |b7baa004878e8781ba2207bed49536aeb55094bd378f7716d74711845f3a8ab3| The source is public: git.cinelerra-gg.org <https://git.cinelerra-gg.org/?p=sam/cinelerra-gg-qt6.git;a=summary>, branch main. 1. New effect panels: please test them thoroughly The controls of these ten effects now live in the Effect Inspector, with no extra window: BoxBlur, FindObj, Perspective, Chroma key, Chroma key (HSV), Chroma key (Avid), Motion, Color 3 Way, Histogram and Histogram Bezier. Sketcher, CriKey and Tracer came earlier in the same style, and nineteen effects such as Blur, Sharpen and Wave have a common layout with sliders and number fields. That makes 32 video effects with native panels. The others still show their old controls. Video, 1:56, English with subtitles: the effect panels and what to check <https://download.cinelerra-gg.org/files/qt6-alpha/videos/cinelerra-qt6-effe…> Video, 1:56, English with subtitles: the effect panels and what to check <https://download.cinelerra-gg.org/files/qt6-alpha/videos/cinelerra-qt6-effe…> The automatic tests run the real program, but they can't replace your eye and your own footage. Please check above all: * Every control: does it do what it did in the old window? * Old projects with these effects: do they open and look the same? * Keyframes, undo, playback and rendering, also with several effects on one track. To compare, the old window of these ten effects is still there. Start the AppImage with a variable, for example |CIN_PERSPECTIVE_LEGACY_WINDOW=1|. The others are |CIN_BOXBLUR_LEGACY_WINDOW|, |CIN_FINDOBJ_LEGACY_WINDOW|, |CIN_CHROMAKEY_LEGACY_WINDOW|, |CIN_CHROMAKEYHSV_LEGACY_WINDOW|, |CIN_CHROMAKEYAVID_LEGACY_WINDOW|, |CIN_MOTION_LEGACY_WINDOW|, |CIN_COLOR3WAY_LEGACY_WINDOW|, |CIN_HISTOGRAM_LEGACY_WINDOW| and |CIN_HISTOGRAM_BEZIER_LEGACY_WINDOW|. When you find something, please tell me which effect, what you did and what you saw. Already known, no need to report: * Perspective: when the picture fills the compositor, the corner handles sit on its edge. Press on the inner half of a handle. A handle on the divider to the meters can move the divider instead, so make the compositor a little wider. * After Attach Effect the clock in the main window can show a wrong time. The clock of the compositor is right. 2. Scene catalog Right-click a file in Resources and choose Detect Scenes. Cinelerra looks for hard cuts, and Create clips makes one clip for each checked scene. Nothing is copied or rendered, a clip only points to its part of the file. In the video, the twelve minutes of Tears of Steel gave 138 scenes in 42 seconds. Every clip has a card with categories, role, shot size, keywords and the transcript, if the file was transcribed. Classify fills these fields on your own computer: people, animals, interior, exterior, shot size and a short description. What you set by hand stays. The models are not part of Cinelerra. The first time, a dialog shows the size, the source and the licence of each one, and nothing is downloaded until you say so. It's 2.5 GB, once. The run took between four and five seconds for each scene on 16 cores. It does make mistakes: in the video it calls a robot an animal, and one click on the card fixes that. It finds hard cuts only, not fades or dissolves, and the descriptions are in English only. The catalog is also open to AI assistants through the remote control. The video ends with a real run of Claude Code, which picked scenes from the descriptions alone and says so. Video, 4:30, English with subtitles: scenes, catalog, classifying, an AI edit <https://download.cinelerra-gg.org/files/qt6-alpha/videos/cinelerra-qt6-scen…> Video, 4:30, English with subtitles: scenes, catalog, classifying, an AI edit <https://download.cinelerra-gg.org/files/qt6-alpha/videos/cinelerra-qt6-scen…> Also new: the OpenCV ObjectMask effect has a Download model button for a newer model, and a short clip on the timeline can always be dragged at its middle, with its trim modes on a bar outside the clip. The film in both videos is Tears of Steel, (CC) Blender Foundation, mango.blender.org, licensed CC BY 3.0. All videos with .srt subtitles: qt6-alpha/videos <https://download.cinelerra-gg.org/?path=qt6-alpha%2Fvideos>. 3. Fixes from your reports Igor: * Proxy: the project kept its size when a proxy was switched on, and switching it off afterwards doubled the size, 720x576 became 1440x1152. The P button did nothing at all, and Off in the dialog left the proxy files in the edits. Now 1/2 turns 720x576 into 360x288, and the P button, Ctrl+R and Off in the dialog all bring back 720x576 with the original files. This also holds for a project saved with the proxy on and loaded again. * One visible change: a scale the project size does not divide by is now grey. 1080/16 would come back as 1088 instead of 1080. On a 1920x1080 YUV project that leaves 1/2 and 1/4, the same rule the classic dialog uses for its list. * Mixer Viewer: the Mx button had no function yet. Now Shift+M opens an empty mixer, Mx on a video track links the track, and the mixer comes to the front with the picture. It follows the transport and the link is saved with the project. I tested this with one mixer and one video track, not with a real multi camera project, so please tell me what you find there. Andrea: * Dragging from the floating Resources window under Wayland: a program does not know where its windows are there, so the drag could not find the timeline from another window. In that case it now goes through the display server. In a nested KWin session, an effect reached the track in both modes of Floating panels. I only tested on KWin, so please check it on your desktop. * av1_vaapi and vp9_vaapi: this is not a bug in Cinelerra. As far as I can find, your RX 5700 XT has VCN 2.0, which encodes only H.264 and HEVC. VP9 is decode only, and AV1 encoding arrived with VCN 4.0. "No usable encoding profile" is what the driver answers in that case. Also: the anylinux AppImage starts on native Wayland now. Before, it stopped at the start when Display platform was set to Wayland. Cheers, Sam

5 7

Anon found note about cinelerra-gg on Mastadon
by Andrew Randrianasulu 07 Nov '26

07 Nov '26

https://mastodon.social/@unfa/117271785764375381 well, its short. ;)

2 1

Build troubleshooting on openSUSE Leap 16.1: plugin index permission crash
by Terje J. Hanssen 04 Nov '26

04 Nov '26

Hi team, I have successfully compiled Cinelerra-GG from source on openSUSE Leap 16.1, using a configuration set to single-use without third-party and dynamically linked. However, I ran into a persistent startup crash related to writing plugin indexes: MWindow::init_plugins: can't create plugin index: /home/terje/.bcast5/Cinelerra_plugins Interestingly, the exact same source build runs and behaves seemingly fine on openSUSE Tumbleweed-Slowroll, but on Leap 16.1 the locally built binary in ./bin/cin encounters permission or I/O errors when attempting to write to the configuration directory during initialization unless heavily overridden. Troubleshooting steps taken so far: - The .bcast5 configuration directory has been deleted and recreated multiple times, but Cingg still crashes during startup. - Three different CinGG AppImages have also been tested on the same system without startup issues. Has anyone experienced similar path or permission issues when running a fresh source build alongside pre-existing environment configs? Terje

3 16

Great work Sam!
by info＠bandshed.net 01 Nov '26

01 Nov '26

Hi Cin friends! I just got a brief opportunity to look at the new QT6 alpha and for an alpha it seems incredible full-featured, kudos to Sam for even with AI help this must be a very time consuming project. I will try a few editing projects soon but in the meantime I just wanted to shout out some thanks. This is a very exciting development and the UI work is very impressive so far. Keep up the terrific work! --

2 2

Traditional CinGG AppImages newly available
by Phyllis Smith 31 Oct '26

31 Oct '26

With FFmpeg updated to 9.0.2, there are new AppImages now available for download. Release notes of what has changed is below. ***************** GIT for Cinelerra-GG has the following changes from 09/01/2026-10/31/2026 *FFmpeg* has been updated from 8.1 to 9.0.2. It was discovered since version 8.x, a new requirement that in addition to the "-hwaccel_device" option, the "-vaapi_device" option has to also be included. So pending ongoing analysis, rendering using any of the “vaapi” video formats will give an error message. Any formats that have been known to crash were temporarily removed. The previously deprecated AVCodec pix_fmts, sample_fmt, and supported_framesrates was removed from ffmpeg/libavcodec requiring fixes to fileac3, fileffmpeg, and ffmpeg.C at 9.x. Updated ffmpeg.git.patch# files for building with git to check out current non-released ffmpeg code. Added -latomic and disabled vsx in x264 for case where it does not work on older PPC processors so it is now automatic. Mods provided by *Andrew-R*. Patch submitted by *Tarceri* (Mesa drivers support person) partial fix now frees gl fb cfgs pointers correctly on destruction.

1 0

Cinelerra-GG Qt6 alpha 2026-10-29: zoom grips, AI remote control, fixes from your reports
by Sam 31 Oct '26

31 Oct '26

Hi everyone, a new Qt6 alpha is online, built on 2026-10-29. It brings zoom grips on the timeline scrollbars, hints in the footer, a first version of remote control for AI assistants, and the fixes for what you reported since the alpha of 2026-10-27. Thank you, Terje, Andrea, Rob and Andrew, for testing and for the detailed reports. Download (sorted by date, the newest on top): download.cinelerra-gg.org <https://download.cinelerra-gg.org/?path=qt6-alpha&sort=date_desc> * CinGG-qt6-alpha-20261029-x86_64.AppImage <https://download.cinelerra-gg.org/files/qt6-alpha/CinGG-qt6-alpha-20261029-…>, sha256 |bbc89ef9e26b38468addb30775339b79aeb332d40a60d2fec7395620bc8b7912| * CinGG-qt6-alpha-20261029-anylinux-x86_64.AppImage <https://download.cinelerra-gg.org/files/qt6-alpha/CinGG-qt6-alpha-20261029-…> for older systems (it brings its own glibc), sha256 |0b41d7b0144449d76e9a78b14839fdd236a7b82094779352eec56c71c34006e8| The source is public: git.cinelerra-gg.org <https://git.cinelerra-gg.org/?p=sam/cinelerra-gg-qt6.git;a=summary>, branch main, 59 commits since the alpha of 2026-10-27. 1. Zoom grips on the timeline scrollbars Premiere, Kdenlive and VEGAS let you zoom right on the timeline scrollbar, and Cinelerra can do that now, too. Each end of the scrollbar thumb has a round grip. Drag a grip and the view zooms smoothly, while the other end stays where it is. When you let go, the grip stays under the mouse. Drag the middle to scroll as before, and a double-click shows the whole project. The vertical scrollbar beside the tracks has the same grips. There a grip changes the height of all tracks at once, audio and video alike, and a double-click fits all tracks into the window. The footer now tells you what the mouse can do: over a clip, over the time ruler, over a scrollbar. While you drag a clip, it says what the drop will do, move it, or with Shift, overwrite. If you don't want the hints, a right click on the footer turns them off. The E key toggles the editing mode again. Video, 1:32, English with subtitles: zoom grips and footer hints <https://download.cinelerra-gg.org/files/qt6-alpha/videos/cinelerra-qt6-zoom…> Video, 1:32, English with subtitles: zoom grips and footer hints <https://download.cinelerra-gg.org/files/qt6-alpha/videos/cinelerra-qt6-zoom…> 2. Remote control for AI assistants (MCP), an early version Professional editors are adding a way for AI assistants to work in the edit. DaVinci Resolve Studio has a built-in MCP server for this. Adobe has an official connector for quick video jobs in the cloud, while control of the Premiere Pro or Final Cut Pro timeline still takes add-ons from the community. Cinelerra now has its own MCP server, built into the program, free and open source. It is off by default. Turn it on in Settings, Preferences: search for remote control and tick Allow AI tools and scripts to control Cinelerra (local socket). Cinelerra then opens a socket in a private directory, only for your user. Every call is written to api.log in the configuration folder, and every change is one undo step. Then register Cinelerra with your assistant. For Claude Code that is one line: |claude mcp add cinelerra -- /path/to/CinGG-qt6-alpha-20261029-x86_64.AppImage --mcp| Codex works the same way, with an entry in ~/.codex/config.toml. The README in the repository has both setups. The video shows a very simple example, just to see what it can do: load a clip, cut out two ranges, add Brightness/Contrast and look at the frames on both sides of the cut. The terminal on the left is re-enacted, the Cinelerra on the right is the real program, driven through the socket with the same calls a real session made. The assistant can do a lot more: * Effects: add, remove, move, switch on and off, set single parameters, apply and save presets, reset, open and steer the Effect Inspector. * Project: list tracks, clips and media, select clips, arm tracks, save the project under a new name. * Timeline: read and set the position, select ranges, and through the command table jump to edits and labels, set in and out points and much more. * Seeing and events: a frame of the compositor at any point, and a notice of every change to the project. * In all there are 45 verbs, and over 300 commands of the command table can be run. Prepared, but not available yet: rendering, inserting, moving and trimming clips, and automatic editing. Scene detection comes next. This is the first step, and more will follow. Video, 2:46, English with subtitles: remote control for AI assistants <https://download.cinelerra-gg.org/files/qt6-alpha/videos/cinelerra-qt6-ai-c…> Video, 2:46, English with subtitles: remote control for AI assistants <https://download.cinelerra-gg.org/files/qt6-alpha/videos/cinelerra-qt6-ai-c…> The film in both videos is Tears of Steel, (CC) Blender Foundation, mango.blender.org, licensed CC BY 3.0. All videos with .srt subtitles: qt6-alpha/videos <https://download.cinelerra-gg.org/?path=qt6-alpha%2Fvideos>. 3. Fixes from your reports Terje (GNOME): * A floating Compositor stayed above the main window, and the main window could not be brought in front of it. Settings, Preferences, Appearance has a new row Floating panels: Stay above the main window (the default, as before) or Separate windows, where every panel is a window of its own. * Interface Scale could only be set for the platform that was running. Both rows, X11 and Wayland, are shown now, and the one in use is marked. Andrea: * VAAPI did not start in either AppImage (no function __vaDriverInit_1_0). The cause is not your graphics card: the AppImage brought libva 2.20, which cannot load the VAAPI drivers of newer distributions. The normal AppImage now takes libva from your system and keeps its own copy only as a fallback. The anylinux AppImage is unchanged for now. Rob (Debian 13, openbox, two screens): * The waveform of a clip was incomplete on the first load. It is complete now as soon as the index of the clip is built. * Dragging a floating panel by its title bar often resized it instead. Only the top 4 px of the title bar resize now, the corners keep their wider grip. * With Separate windows, the window manager moves a floating panel, so it can go to your second screen without docking on the way. A double-click on its title bar docks it again. * Dialogs did not stand out from the main window without a compositing window manager. Every dialog now has its own background and a thin frame. Found in our own tests: * The mouse wheel changed number fields and lists while you scrolled a page, for example the channels in the Info panel. On scrolling pages, a field now takes the wheel only after you clicked it. The effect panels keep the wheel as before, there it is wanted. * Keys of the classic main window that did nothing in the Qt6 build so far work again. They run through the command table and can be changed in the keyboard editor. Andrew, Terje: VAAPI with ffmpeg 9 is still open. I will come back to you with a test build. How this is made As before, the code is written with Claude. What I rely on is testing: automated tests that run the real program, code reviews of each larger change, and my own check of every feature before it is pushed. That does not make it free of bugs, so please keep the reports coming: bug.cinelerra-gg.org <https://bug.cinelerra-gg.org> or this list. Sam

4 3

OT: Capture 576i50 analog S-video with v4l2 and PCIe Magewell Pro Capture AIO in 10-bit 4:2:2?
by terjejhanssen＠gmail.com 30 Oct '26

30 Oct '26

It's been quite a while since my last post, but I've been keeping up a bit in the background ....... In the past, we had some posts about capture devices, some few standalone or pcie based, but most usb of course. After earlier S-video to DV capturing (which was in 8bit 4:2:0 using Datavideo DN300), my plan has been to recapture all my S-video tapes to 10bit 4:2:2 in Prores LT for the final archive. In fact I tested this 10 years ago for 5 Hi8 tapes (which still work using ffmpeg) using a Blackmagic Analog to SDI mini-converter and a Hyperdeck Shuttle-2 SSD recorder. Some months ago I tried to resume this capture project, but had to conclude that the BMD converter didn't work. I ordered a new one, 2nd gen (EOS), but unfortunately its new chips seemingly require a studio-quality video signal. The Shuttle-2 didn't get a valid signal to record, even though it works perfectly fine when recording HD video from my HDV camcorder via HDMI. So at last I had to give up on this BMD analog route. And I don't wont to trust Blackmagic Design Intensity Pro 4K on Linux -- a card I previously mentioned in an old post https://tinyurl.com/2nuj7hfk There is however another option, —costly, yes—for Linux that I was not aware of and therefore didn't mention in my old post above Magewell Pro Capture Aio - One-channel HD capture card But I have yet to find user posts confirming it is capable to record SD video in 10bit 4:2:2 with v4l2, and especially on openSUSE Tumbleweed-Slowroll. Any tip or thoughts about how risky this Magewell option may be with regards to success or failure ? Here follows just my collections of Magewell urls: https://www.magewell.com/products/pro-capture-aio https://www.magewell.com/kb/detail/000020047/pro-capture https://www.magewell.com/kb/pro-capture?page=1 https://www.magewell.com/downloads/pro-capture https://www.vision-dimension.com/en/blog/video-capture/magewell/magewell-is…

4 3

future of cinGG UI?
by Rob Prowel 29 Oct '26

29 Oct '26

I've been away for a while dealing with family stuff but I noted that the last AppImage of the traditional UI cinGG is from august and more recently the app has a Qt interface. I hope we are not seeing a switch from the traditional UI semantics, without continuing the power user functionality that existed for so long. For a long time I considered that a UI based on a popular toolset was a good idea but abandonned that goal after looking at how heavily the old UI was embedded into the code. Qt was an obvious choice. So don't get me wrong, I congratulate the author's update, but would like to point out a few issues that should be addressed. * The traditional UI accepted immediate mode commands entered from the keybord. While possible in Qt, it seems that operational mode is not active in the current Qt version. When I type (q) on the timeline I want to see the "quit" dialog. Likewise, <shift>R should immediately pop up the render dialog. * I understand the current popular "wayland" position that apps should each be managed by a single top level window and that somehow IPC between windows is a "cough cough" security bug...but! The workflow of content creation in a single window UI is greatly crippled by cramming everything in a single top level window. I contend that each major function: timeline, compositor, and asset-management should have their own independent top level window. I use a dual monitor configuration and need to be able to place function windows on independent monitors to space things out. * color themes need to be better considered. The default theme is fine, but when you introduce a popup like the global settings over top of the full screen app window, the content gets lost in the haze. I'd contend that popups should use a different background color so their content becomes more ovbious. * the new Qt UI is polished and very pretty. PLEASE, don't favor pretty fluff over power user functionality though. having to click a series of pulldown menus to reach a frequently used function is unpleasant. Sometimes keyboard commands are "better" than point and click. * a bug that seems to be prevalent in cinGG is that upon opening a clip, the default timeline doesn't fully render the audio tracks, but only for about half of the visible clip. The full rendering doesn't take place unless I zoom in or out on the timeline time range. Truth is that I am impressed with the Qt UI, but we need to maintain a aire of power user friendliness so that productivity doesn't take a backseat to asthetics. I've always maintained that WYSIWYG is a bad concept and I prefer, "you aksed for it, you got it!" For now I'm hoping the traditional UI app continues to be the main dev branch and receives ALL fixes and enhancements for the foreseeable future. On a final note I recently pulled down the full git repo and tried to do a default build (use cinGG 3rd party libs) but the "build install" fails with a recurve out of memory error when trying to install certain plugins: I think ladspa stuff? -Rob

4 5

Cinelerra-GG Qt6 alpha 2026-10-27: patchbay and footer styles, fixes from your reports
by Sam 29 Oct '26

29 Oct '26

Hi everyone, a new Qt6 alpha is online, built on 2026-10-27. It brings two new features, the patchbay styles and the footer styles, and the fixes for what you reported since the alpha of 2026-10-22. Thank you, Terje, Igor, Andrea and Thomas, for testing and for the detailed reports, videos and screenshots. Download (sorted by date, the newest on top): download.cinelerra-gg.org <https://download.cinelerra-gg.org/?path=qt6-alpha&sort=date_desc> * CinGG-qt6-alpha-20261027-x86_64.AppImage <https://download.cinelerra-gg.org/files/qt6-alpha/CinGG-qt6-alpha-20261027-…>, sha256 |fdd3de0172e3f2712aad0ff674d5c33a52034697b4e5143e4fd413b7a4b8377a| * CinGG-qt6-alpha-20261027-anylinux-x86_64.AppImage <https://download.cinelerra-gg.org/files/qt6-alpha/CinGG-qt6-alpha-20261027-…> for older systems (it brings its own glibc), sha256 |8465fa6e4a8dfcf976954e74198ee73660f778efac004ab96be9c9d3c7f206b6| The source is public: git.cinelerra-gg.org <https://git.cinelerra-gg.org/?p=sam/cinelerra-gg-qt6.git;a=summary>, branch main, 69 commits since the alpha of 2026-10-22. 1. Patchbay styles The patchbay can now be set up the way you like it: like DaVinci Resolve, like Kdenlive, like Premiere or Avid, or entirely your own. A right click below the tracks lists the styles: Classic, Compact and Single row. The patchbay also adapts to its width: drag it wider and the faders and fields grow, drag it narrower and it hides what no longer fits, step by step. In the Patchbay Styles window you build your own styles by dragging elements: the track label as a column over the full height, short (V1, A1) and upright; a new row for gang and master; a fader and a level meter standing upright at the right edge. A preview shows the style on a low, a default and a tall track. There are also new elements: a vertical fader, the fader value, a Solo switch (plays and renders only the soloed tracks) and an effects switch that turns all effects of a track off and on again. Video, 2:17, English with subtitles: the patchbay styles and the style editor <https://download.cinelerra-gg.org/files/qt6-alpha/videos/cinelerra-qt6-patc…> Video, 2:17, English with subtitles: the patchbay styles and the style editor <https://download.cinelerra-gg.org/files/qt6-alpha/videos/cinelerra-qt6-patc…> 2. Footer under the timeline, and its styles The footer below the timeline is one row now: the selection fields (start, length, end), the zoom, the curve range and a message slot on the right. Messages fade out after a while, errors are counted, and a click shows the history. The Display button opens a small window for the track heights, the waveform, the title bars and the curve ranges, where a click on a curve's colour mark picks its colour. The Up and Down keys zoom again, with Ctrl the waveform, with Alt the curve range. Like the patchbay, the footer has styles. Classic shows it as in the old Cinelerra: duration, waveform, track heights, curve range and the selection fields. Modern is the new default. In the Footer Styles window you make a copy and drag the elements into the order you need. A right click on a free spot of the footer switches between the styles. Video, 1:35, English with subtitles: Classic, Modern and the Footer Styles editor <https://download.cinelerra-gg.org/files/qt6-alpha/videos/cinelerra-qt6-foot…> Video, 1:35, English with subtitles: Classic, Modern and the Footer Styles editor <https://download.cinelerra-gg.org/files/qt6-alpha/videos/cinelerra-qt6-foot…> The film in both videos is Tears of Steel, (CC) Blender Foundation, mango.blender.org, licensed CC BY 3.0. All videos with .srt subtitles: qt6-alpha/videos <https://download.cinelerra-gg.org/?path=qt6-alpha%2Fvideos>. 3. Fixes from your reports Terje (GNOME, native Wayland): * The interface was too small on a 27-inch WQHD screen. Settings, Preferences, Appearance has a new row Interface Scale, one value for X11 and one for Wayland. Terje, set Interface Scale (Wayland) to 1.40, that is what QT_SCALE_FACTOR=1.4 did for you. It applies after a restart, which Cinelerra offers. * The X in the title bar of a floating window (Compositor and the other docks) closes it again. * A docked window dragged by its title bar comes loose on Wayland. This is tested on KDE only. Terje, could you try it on GNOME? * Window, Show Compositor and the other Show entries carry a check mark while the window is shown. Igor: * A drop from the Resources panel onto the Viewer or the Compositor works. * Draw media in the patchbay hides the media of the clips. * A track that is not armed keeps its keyframes, the mouse no longer adds or moves them there. * The pointer shows the I-beam over the timeline in Cut and Paste mode. * The transport buttons: Settings, Preferences, Appearance, Icon size sets their size. Thomas (video of 2026-10-20, private email): after a click on a patchbay switch, moving the mouse over the same switch of another track switched it as well. The switches now act on the press, and dragging across tracks only works while the button is held. Andrea: * The knobs of plugins such as Motion: the needle sat off centre and turned strangely with the theme images. Needle, blue arc and the drag angle now take the centre of the knob. * The reset button that every effect has in its header in the Effect Inspector (the circular arrow) works now. It sets the effect back to the plugin's factory defaults at the current keyframe, as one undo step. If an effect cannot be reset, the footer says so. * QT_QPA_PLATFORM=wayland always gave X11: that is on purpose while an X11 display is there, the variable for Cinelerra is CIN_QPA_PLATFORM=wayland. The log now says so. Easier still: see the new setting below. * h264_vaapi crash (Assertion pic->nb_dpb_pics < 16): the AppImage uses ffmpeg 7.1, and that assertion is in line 62 of hw_base_encode.c only from ffmpeg 8 on. Which build did you use, and what does ffmpeg -version say? * The fontconfig warnings of the anylinux AppImage: could you send the exact lines? 4. Two new settings for everyone * Display platform: Settings, Preferences, Appearance has a row Display platform with Automatic, X11 and Wayland. Automatic is the default and behaves as before (X11 when there is an X11 display, also XWayland). It applies after a restart. CIN_QPA_PLATFORM still wins when you set it. * Own configuration folder: the AppImages now keep their settings in ~/.bcast5-qt6, so an installed Cinelerra keeps ~/.bcast5 to itself. On the first start the AppImage copies your ~/.bcast5 there, without the index files of your media. Nothing is lost, and the two programs no longer read each other's plugin index. This came from Thomas, who wrote a start script for exactly this. Set CIN_CONFIG if you want another folder. 5. VAAPI with ffmpeg 9 Andrew, thank you for all the work you put into ffmpeg in Cinelerra over the years. You wrote that you hope AI assistants can help here. I would like to try exactly that. The part that burned you out, chasing every API change of ffmpeg, is the part an AI does tirelessly. What it cannot do is know where Cinelerra's ffmpeg code hides its traps, and that knowledge is yours. So if you ever feel like it, no pressure and no deadline: a look at a patch, or a one-line hint like the MLT patch you pointed us to, already helps a lot. Phyllis, I would like to help with VAAPI and ffmpeg 9. One thing I noticed: the MLT patch fixes a hwupload/buffersink filter graph, and Cinelerra does not use that graph for encoding. It sets up the hardware frames itself (ffmpeg.C, av_hwframe_ctx_alloc and av_hwframe_transfer_data), so the fix will probably look different. The catch: I have no hardware for VAAPI encoding, only an NVIDIA card, so I cannot test it myself. Terje, your Arc A750 encodes h264_vaapi and hevc_vaapi with ffmpeg 9.0.2. Your test shows that the driver and ffmpeg 9 work on your system. It goes through the hwupload filter, though, and Cinelerra takes another way to the GPU, so only a Cinelerra build can show whether its encoding works. Would you run test builds if I prepare a patch? Anyone else with an Intel or AMD GPU is welcome too. How this is made As before, the code is written with Claude (every commit carries the Co-Authored-By line). What I rely on is testing: automated tests that run the real program, code reviews of each larger change, and my own check of every feature before it is pushed. That does not make it free of bugs, so please keep the reports coming: bug.cinelerra-gg.org <https://bug.cinelerra-gg.org> or this list. Cheers, Sam

5 5

reference patch in MLT tree for ffmpeg 9
by Andrew Randrianasulu 26 Oct '26

26 Oct '26

https://github.com/mltframework/mlt/pull/1281/changes/68bceba12a3c3278ce690… of course ffmpeg devs invented yet another way to get supported sample/pixel formats out of codec internals .... Will try to make mplayer work first, then may be cinelerra.

5 19