- Cin - Cinelerra-GG Mailing Lists

Cinelerra-GG Qt6 alpha: keyboard shortcuts can now be edited
by Sam 11 Oct '26

11 Oct '26

Cinelerra-GG Qt6 alpha: keyboard shortcuts can now be edited Hi everyone, The Cinelerra-GG Qt6 alpha AppImage of October 10 brings one change that touches everybody who works with the keyboard, so here is a short tour with pictures. * AppImage: https://download.cinelerra-gg.org/?path=qt6-alpha * Source: https://git.cinelerra-gg.org/sam/cinelerra-gg-qt6.git <https://git.cinelerra-gg.org/?p=sam/cinelerra-gg-qt6.git;a=summary> 1. A shortcut editor *Settings → Keyboard Shortcuts…* opens it, and so does the button "Edit shortcuts…" in *Preferences → Keyboard*. Shortcut editor with the drawn keyboard * All 258 commands are in one list, grouped by area: the menus of the main window, the panels (Viewer, Compositor, Resources), and the context menus of the timeline and of the Resources window. * Every command can have two keys. The column "Default" shows what Cinelerra-GG uses out of the box, and the arrow at the end of a row puts that back. * A click on a key field records a new key. Esc cancels, Del clears. * The search field finds a command by name, or, switched to "Key", by the key you press. In the picture below four commands use Space, one in each area. * The built-in set "Cinelerra-GG" stays as it is. Your first change starts a set "Custom". "Reset set…" goes back to the defaults. Search by key: four commands use Space 2. A drawn keyboard The button "Keyboard" shows a keyboard above the list. Keys with a command are blue, free keys are grey. Hold Ctrl, Shift or Alt and the picture changes to the keys taken with that modifier. Point at a key to read its command, click it to filter the list. German and US layout can be chosen. The drawn keyboard with Ctrl held 3. Conflicts are shown before they happen If the key you record already belongs to another command, the editor says which one and asks. "Assign" moves the key, the other command loses it. Nothing is overwritten silently. The editor reports a key conflict 4. Keys follow the active panel The same key can mean different things in the Viewer, the Compositor and the timeline. The panel you clicked last gets the keys, and a thin blue frame marks it. In the picture it is the Compositor at the top right: Space plays there, not on the timeline. The blue frame marks the active panel, here the Compositor Preferences → Keyboard has a switch "Panel under the mouse pointer takes the keys" for those who prefer that. Preferences, page Keyboard 5. Context keys on the timeline and in the Resources window The commands of the right-click menus can be run by key. The clip, track, effect, transition or keyframe you clicked last is marked and is the target: Del removes exactly that object, Ctrl+X cuts it, and so on. 60 timeline commands are in the editor under "Timeline context". Most of them have no key yet, so you can give them the ones you like. The context menus of the Resources window work the same way. The clicked clip is marked as the target of the keys What I would like to hear from you * Keys that do nothing, or do the wrong thing in one panel. * Menu keys that differ from the stable Cinelerra-GG. They should be the same, and a difference is a bug. * Commands you miss in the list. Please report in the bug tracker at https://bug.cinelerra-gg.org with the category *Qt6 Alpha*. This is an alpha, please do not use it for real projects. It shares the settings folder |~/.bcast5| with the stable version, so copy that folder before the first start. The editor pictures show an example set in which "Toggle label" was moved from L to K.

1 1

Silly question
by Andrea paz 01 Oct '26

01 Oct '26

Foreword: My friends have been telling me enthusiastically about a CAD program for Linux that’s on par with AutoCAD and uses AutoCAD’s standard file formats. According to its author, this program—OpenCAD Studio ( https://github.com/HakanSeven12/OpenCADStudio)—was developed primarily using AI (Claude). Silly question: Can AI be used for some development in CinGG? It's a silly question because I don't know anything about programming or AI, but I'm curious about it.

10 22

Info on vaapi failure at ffmpeg 9.0.2
by Phyllis Smith 29 Sep '26

29 Sep '26

The error I am getting when I render a hardware vaapi loaded video with audio using h264_vaapi.mp4 is: > Assertion pic->display_order == pic->encode_order failed at > libavcodec/vaapi_encode_h264.c:421 > The code in libavcodec/vaapi_encode_h264.c is exactly the same for 8.1 as 9.0.2. I am continuing to investigate. The errors Andrew reported are: > RenderFarmClient::main_loop: client started > [AVHWFramesContext @ 0xafddc0c0] Unsupported format: vaapi. > Failed to initialize HW frame context. > err: Invalid argument > [h264_vaapi @ 0xa7ddaf00] A hardware frames reference is required to > associate the encoding device. > FFMPEG::open_encoder err: Invalid argument > int FFMPEG::open_encoder(const char*, const char*): > open failed h264_vaapi:/dev/shm/dnxhd.mkv > Render::render_single: Session finished. > Render::render_single: Session finished. > ** rendered 1 frames in 2.310 secs, 0.433 fps > FFMPEG::open_decoder: some stre > >

2 1

patching ffmpeg 9.0.2
by Andrew Randrianasulu 26 Sep '26

26 Sep '26

--log-- guest@slax:/dev/shm/ffmpeg-9.0.2$ cat ../new-git/cinelerra/cinelerra-5.1/thirdparty/src/ffmpeg-8.1.patch1 | patch -p1 patching file fftools/cmdutils.c guest@slax:/dev/shm/ffmpeg-9.0.2$ cat ../new-git/cinelerra/cinelerra-5.1/thirdparty/src/ffmpeg-8.1.patch2 | patch -p1 patching file libavformat/mpegtsenc.c Hunk #16 succeeded at 1893 with fuzz 1. Hunk #17 succeeded at 1912 (offset -2 lines). Hunk #18 succeeded at 2381 (offset -2 lines). Hunk #19 succeeded at 2410 (offset -2 lines). patching file libavformat/mpegts.h patching file libavformat/bluray.c Hunk #1 succeeded at 28 (offset 1 line). patching file doc/muxers.texi Hunk #1 succeeded at 3174 (offset 20 lines). guest@slax:/dev/shm/ffmpeg-9.0.2$ cat ../new-git/cinelerra/cinelerra-5.1/thirdparty/src/ffmpeg-8.1.patch3 | patch -p1 patching file libavformat/avformat.h Hunk #1 FAILED at 495. Hunk #2 FAILED at 558. 2 out of 2 hunks FAILED -- saving rejects to file libavformat/avformat.h.rej patching file libavformat/dv.c patching file libavformat/matroskadec.c Hunk #1 succeeded at 5024 (offset 174 lines). Hunk #2 succeeded at 5037 (offset 174 lines). patching file libavformat/seek.c guest@slax:/dev/shm/ffmpeg-9.0.2$ cat ../new-git/cinelerra/cinelerra-5.1/thirdparty/src/ffmpeg-8.1.patch4 | patch -p1 patching file libavformat/avidec.c Hunk #1 succeeded at 2039 (offset 8 lines). guest@slax:/dev/shm/ffmpeg-9.0.2$ cat ../new-git/cinelerra/cinelerra-5.1/thirdparty/src/ffmpeg-8.1.patch | patch -p1 ffmpeg-8.1.patch1 ffmpeg-8.1.patch14 ffmpeg-8.1.patch5 ffmpeg-8.1.patchC ffmpeg-8.1.patch10 ffmpeg-8.1.patch2 ffmpeg-8.1.patch7 ffmpeg-8.1.patchD ffmpeg-8.1.patch11 ffmpeg-8.1.patch3 ffmpeg-8.1.patch9 ffmpeg-8.1.patchZ1 ffmpeg-8.1.patch12 ffmpeg-8.1.patch4 ffmpeg-8.1.patchB ffmpeg-8.1.patchZ2 guest@slax:/dev/shm/ffmpeg-9.0.2$ cat ../new-git/cinelerra/cinelerra-5.1/thirdparty/src/ffmpeg-8.1.patch | patch -p1 ffmpeg-8.1.patch1 ffmpeg-8.1.patch14 ffmpeg-8.1.patch5 ffmpeg-8.1.patchC ffmpeg-8.1.patch10 ffmpeg-8.1.patch2 ffmpeg-8.1.patch7 ffmpeg-8.1.patchD ffmpeg-8.1.patch11 ffmpeg-8.1.patch3 ffmpeg-8.1.patch9 ffmpeg-8.1.patchZ1 ffmpeg-8.1.patch12 ffmpeg-8.1.patch4 ffmpeg-8.1.patchB ffmpeg-8.1.patchZ2 guest@slax:/dev/shm/ffmpeg-9.0.2$ cat ../new-git/cinelerra/cinelerra-5.1/thirdparty/src/ffmpeg-8.1.patch5 | patch -p1 patching file libavfilter/formats.c Hunk #1 succeeded at 112 (offset 1 line). Hunk #2 succeeded at 127 (offset 1 line). guest@slax:/dev/shm/ffmpeg-9.0.2$ cat ../new-git/cinelerra/cinelerra-5.1/thirdparty/src/ffmpeg-8.1.patch7 | patch -p1 patching file libavcodec/vdpau_mpeg12.c guest@slax:/dev/shm/ffmpeg-9.0.2$ cat ../new-git/cinelerra/cinelerra-5.1/thirdparty/src/ffmpeg-8.1.patch8 | patch -p1 cat: ../new-git/cinelerra/cinelerra-5.1/thirdparty/src/ffmpeg-8.1.patch8: No such file or directoryguest@slax:/dev/shm/ffmpeg-9.0.2$ cat ../new-git/cinelerra/cinelerra-5.1/thirdparty/src/ffmpeg-8.1.patch9 | patch -p1 patching file libavformat/mpegenc.c Hunk #1 succeeded at 1000 (offset 11 lines). guest@slax:/dev/shm/ffmpeg-9.0.2$ cat ../new-git/cinelerra/cinelerra-5.1/thirdparty/src/ffmpeg-8.1.patch10 | patch -p1 patching file libavutil/hwcontext_cuda.c Hunk #1 succeeded at 374 (offset 2 lines). guest@slax:/dev/shm/ffmpeg-9.0.2$ cat ../new-git/cinelerra/cinelerra-5.1/thirdparty/src/ffmpeg-8.1.patch11 | patch -p1 patching file libavcodec/hevc/hevcdec.c Hunk #1 succeeded at 698 (offset -14 lines). guest@slax:/dev/shm/ffmpeg-9.0.2$ cat ../new-git/cinelerra/cinelerra-5.1/thirdparty/src/ffmpeg-8.1.patch12 | patch -p1 patching file libavcodec/hevc/ps.c Reversed (or previously applied) patch detected! Assume -R? [n] n Apply anyway? [n] n Skipping patch. 3 out of 3 hunks ignored -- saving rejects to file libavcodec/hevc/ps.c.rej guest@slax:/dev/shm/ffmpeg-9.0.2$ cat ../new-git/cinelerra/cinelerra-5.1/thirdparty/src/ffmpeg-8.1.patch1 | patch -p1 ffmpeg-8.1.patch1 ffmpeg-8.1.patch11 ffmpeg-8.1.patch14 ffmpeg-8.1.patch10 ffmpeg-8.1.patch12 guest@slax:/dev/shm/ffmpeg-9.0.2$ cat ../new-git/cinelerra/cinelerra-5.1/thirdparty/src/ffmpeg-8.1.patch14 | patch -p1 patching file libavcodec/hevc/refs.c Hunk #1 succeeded at 191 (offset 2 lines). Hunk #2 FAILED at 463. 1 out of 2 hunks FAILED -- saving rejects to file libavcodec/hevc/refs.c.rej guest@slax:/dev/shm/ffmpeg-9.0.2$ cat ../new-git/cinelerra/cinelerra-5.1/thirdparty/src/ffmpeg-8.1.patch | patch -p1 ffmpeg-8.1.patch1 ffmpeg-8.1.patch14 ffmpeg-8.1.patch5 ffmpeg-8.1.patchC ffmpeg-8.1.patch10 ffmpeg-8.1.patch2 ffmpeg-8.1.patch7 ffmpeg-8.1.patchD ffmpeg-8.1.patch11 ffmpeg-8.1.patch3 ffmpeg-8.1.patch9 ffmpeg-8.1.patchZ1 ffmpeg-8.1.patch12 ffmpeg-8.1.patch4 ffmpeg-8.1.patchB ffmpeg-8.1.patchZ2 guest@slax:/dev/shm/ffmpeg-9.0.2$ cat ../new-git/cinelerra/cinelerra-5.1/thirdparty/src/ffmpeg-8.1.patch | patch -p1 ffmpeg-8.1.patch1 ffmpeg-8.1.patch14 ffmpeg-8.1.patch5 ffmpeg-8.1.patchC ffmpeg-8.1.patch10 ffmpeg-8.1.patch2 ffmpeg-8.1.patch7 ffmpeg-8.1.patchD ffmpeg-8.1.patch11 ffmpeg-8.1.patch3 ffmpeg-8.1.patch9 ffmpeg-8.1.patchZ1 ffmpeg-8.1.patch12 ffmpeg-8.1.patch4 ffmpeg-8.1.patchB ffmpeg-8.1.patchZ2 guest@slax:/dev/shm/ffmpeg-9.0.2$ cat ../new-git/cinelerra/cinelerra-5.1/thirdparty/src/ffmpeg-8.1.patchB | patch -p1 patching file libavutil/hwcontext_vdpau.c guest@slax:/dev/shm/ffmpeg-9.0.2$ cat ../new-git/cinelerra/cinelerra-5.1/thirdparty/src/ffmpeg-8.1.patchC | patch -p1 patching file libavcodec/encode.c Hunk #1 succeeded at 357 (offset 52 lines). Hunk #2 succeeded at 377 (offset 52 lines). Hunk #3 succeeded at 554 (offset 53 lines). guest@slax:/dev/shm/ffmpeg-9.0.2$ cat ../new-git/cinelerra/cinelerra-5.1/thirdparty/src/ffmpeg-8.1.patchD | patch -p1 patching file libavcodec/pcm-dvdenc.c Hunk #2 succeeded at 187 (offset -1 lines). guest@slax:/dev/shm/ffmpeg-9.0.2$ cat ../new-git/cinelerra/cinelerra-5.1/thirdparty/src/ffmpeg-8.1.patchZ1 | patch -p1 patching file libavcodec/wrapped_avframe.c guest@slax:/dev/shm/ffmpeg-9.0.2$ cat ../new-git/cinelerra/cinelerra-5.1/thirdparty/src/ffmpeg-8.1.patchZ2 | patch -p1 patching file libavformat/yuv4mpegenc.c so basically only patch3, patches 12 and 14 failed. Everything else seems to be applicable.

1 0

Few more patches for cingg on Linux/ppc
by Andrew Randrianasulu 05 Sep '26

05 Sep '26

As promised long ago I tried to make adding -latomic and disabling vsx in our x264 for case where it does not work (older PPC processors) automatic. I think I hit problem with our lv2 (lilv/suil) not picked up if system ones do not present at compile time, but this is another problem I'll try to solve. For now can you test attached four patches and make sure they do not break anything else (x86/amd64)? I tried them on Termux/aarch64 and here they seems to be harmless.

3 2

OT: whisper.cpp works on powermac G5!
by Andrew Randrianasulu 03 Sep '26

03 Sep '26

I was trying to find any use for those large language models and found whole site with autotranscribed WWDC videos. I looked into whisper.cpp and after some bugreporting it installs and works even on 20 years old processor! https://files.mastodon.online/media_attachments/files/117/206/767/104/645/6… I used base model: wget https://huggingface.co/ggerganov/whisper.cpp/resolve/main/ggml-base.en.bin\… and "jfk.mp3" sample (real classic!): wget https://github.com/ggml-org/whisper.cpp/raw/refs/heads/master/samples/jfk.m… I think in my case without any acceleration and just 2 2GHZ cores it processed 11 seconds in 126 or so seconds,so def. not realtime, but a) there are turbo variants of model b) usually people have more powerful machines with gpu, so may be it can be used for auto-transcribing some long lecture or somesuch. This speech-to-text was promised LONG ago and I guess only now, after serious sacrifices in terms of energy and other damages by Big Bro Tech, actually becoming usable ... :/ But I figured if I used OCR for all those 25 years I can use this STT engine too, at least for testing.

2 1

Video editor on browser with AI
by Andrea paz 02 Sep '26

02 Sep '26

If anyone is interested in trying out a browser-based video editor that uses AI: https://github.com/MartinDelophy/ai-video-editor I don't think it's very reliable when it comes to privacy...

2 1

Updated AppImages for minor Bluray fix and 3 thirdparty libraries
by Phyllis Smith 31 Aug '26

31 Aug '26

There are new AppImages on the website with just minor updates, but I like to keep the thirdparty libraries updated so there is no big surprise further down the line. *** GIT for Cinelerra-GG has the following changes from 07/01/2026-08/31/2026 *** Updated libraries include: tiff from 4.7.0 to 4.7.2 dav1d from 1.5.3 to 1.5.4 libvpx from 1.14.1 to 1.17.0 Fix for bluray disc creation which was resulting in an incomplete BDMV structure. This occurred at some version of an FFmpeg update, but was not preventing actual creation of the disc and the two test bluray players tolerated the incomplete structure anyway.

1 0

Updated 2 libraries + bluray fix
by Phyllis Smith 18 Aug '26

18 Aug '26

Checked in to GIT updates to tiff (4.7.2) and dav1d (1.3.4) libraries. And a fix was provided to bluray creation where the BDMV tree is now correct/complete. At some time when FFmpeg was upgraded to a new version the structure was incomplete and there was an error that was only seen at a high loglevel. In ffmpeg/format/bluray sdt_period=-1 was a value that is now out of range so fix is to use sdt_period=1000000. The option was changed from a plain int where -1 meant "off" to a duration instead. I always test bluray creation when installing a new FFmpeg version by creating bluray disc media and viewing on 2 different bluray devices connected to the TV. Both worked which just means the bluray players are fairly tolerant of whatever is thrown at them and at least these 2 did not seem to care that the BDMV tree structure was not right. P.S. Tested update to libjpeg-turbo to the latest 3.2.0 version but unfortunately, it has a cmake version requirement of 3.15 and Ubuntu 16 is at 3.5.1 so no go. Ditto on libaom to 3.14.1 which requires cmake of 3.16.

1 0

Someone put whole WWDC (apple's dev conference) trancript (autogenerated) online
by Andrew Randrianasulu 13 Aug '26

13 Aug '26

Of course I descended directly on Final Cut's internals ;) https://nonstrict.eu/wwdcindex/wwdc2003/005/

1 0