Thank you Andrea :) ## About the Fontconfig ## warnings: as you noticed, they don't cause problems. Up to the AppImage of 1 October, Cinelerra carried its own copy of fontconfig (version 2.14). Newer distributions ship fontconfig 2.18, and its config file 48-guessfamily.conf uses entries that 2.14 does not understand, so the old copy printed about 45 warnings at every start. Since the AppImage of 2 October (CinGG-qt6-20261002), Cinelerra uses the fontconfig and freetype of your system instead. In our test on Fedora rawhide with fontconfig 2.18 the warnings are gone. The same AppImage also shows sub-bins nested under their parent bin. ## Global bins ## A normal bin belongs to one project. It is saved in the project file, and you only see it while that project is open. A global bin belongs to you instead of a project. Cinelerra keeps it in its config folder (~/.bcast5/global_bins.xml) and shows it in the Resources window of every project you open. It is meant for material you use again and again: logos, intros and outros, lower thirds, music beds, sound effects. How to use them - Open the bin list with the "Bins & Filter" button in the Resources toolbar. - Create a global bin with the "Global" button above the bin list. The "Bin" button next to it creates a normal project bin. - Add media in one of three ways: drag clips from the Resources list onto the global bin, right-click a clip and choose "Add to Global Bin...", or right-click the global bin and choose "Import Files..." to pick files from disk. - Right-click the global bin to rename or delete it. - Use its clips like any others, for example by dragging them to the timeline. What is saved where - A global bin only stores the file paths. Your media stays where it is. Nothing is copied. - A clip you use from a global bin is saved in the project like any other media, so the project also opens on a computer without your global bins. Clips you did not use are not written into the project. - If files in a global bin were moved or deleted, Cinelerra lists them at start-up and offers "Relink...", "Remove" or "Ignore". ## View ## View→ Fade: The menu entry does switch the setting and the check mark changes, but the timeline is not redrawn. The fade line only disappears once something else redraws the timeline. This affects all automation entries in the View menu (Fade, Mute, Overlay Mode, Pan, Plugins, Mask, Speed, Camera/Projector X/Y/Z). Assets, Titles and Transitions work. Until the next build, please use Window → Show Overlays (Ctrl+0). The toggles there redraw the timeline right away. ## Mask ## Mask: New projects use the color model RGBA-8 Bit. With that model, the Compositor draws the mask outline but shows the image unmasked. The rendered file is masked correctly. If you switch to RGB-8 Bit (Settings → Format… → Color Model), the Compositor shows the mask. We are still tracking down the exact spot. We also found two smaller problems. The old "Cinelerra: Mask" window can open next to the new mask panel. And in a small Compositor the points are hard to grab: a click slightly off a corner adds a new point instead of moving it. Zooming the Compositor in helps. Was one of these what you ran into? If not, could you tell me what you clicked, what you expected and what happened? Thanks Sam Am 01.10.26 um 23:29 schrieb Andrea paz via Cin:

So far, I've just been exploring the interface, and I'm really excited about it. Thanks, Sam! When I run the AppImage from the console, I get a long list of warnings about fonts (which don't seem to cause any problems):

[...] Fontconfig warning: "/usr/share/fontconfig/conf.avail/48-guessfamily.conf", line 172: invalid constant used : ui-serif Fontconfig warning: "/usr/share/fontconfig/conf.avail/48-guessfamily.conf", line 180: invalid attribute 'xsi:nil' [...]

In Resources, you can create subfolders within custom folders. I've been wanting this feature for a long time. Visually, the subfolders aren't nested under their parent. They all look like similar bins. Speaking of bins, I have a question: what are global bins? The Smart Bins window and how they work are fantastic.

I really like the ability to save and export my custom configuration from Settings --> Preferences. That way, I can load it into new installations without having to access the hidden .bcast5 folder.

I really like how the Deliver tab is organized (with the most important presets right in plain sight). I tried rendering from H.264 to ProRes 444, and everything worked fine. It also seems pretty fast to me, but I need to compare it with CinGG/guicast.

The “View” menu doesn't seem to be working properly (I couldn't turn off the fade), and neither does the “Mask” tool, but I only did some quick tests and need to look into it further.

I'll try it out more thoroughly tomorrow.

Thanks for this new version, Sam. If I use Ctrl-O to add a video, then in the "load files" window, if I shift the boundary between Size and Type to the right, the boundary between Name and Size shifts to the left, starting to cut off file names. That looks weird, and is the opposite of what I expected and wanted to do (more space for the file names). MatN

Hi Sam, Here is my first feedback from just testing startup and File>Load recent with the latest Qt6 AppImage build (CinGG-qt6-20261001-x86_64.AppImage): System Environment OS: openSUSE Tumbleweed-Slowroll Kernel: 6.18.54-1-longterm Desktop Environment: GNOME Shell 50.5 (Wayland / XWayland) What Works Well Stability & Launch: The AppImage starts up without any segmentation faults or critical crashes. Media Handling: Successfully loaded a .m2t transport stream file via File > Load Recent without issues (EditJournal: done: load). FFmpeg / Libav Integration: The bundled Lavc61.19.101 decodes the transport stream properly. Menu / UI Observations Shortcut Collision: On startup, the Qt6 menu bar reports a shortcut conflict: CinelerraMenuBar: "Save Session" wanted Ctrl+S, already taken -- no shortcut Terminal / Console Output Warnings LV2 Plugin Scanner: During the initial plugin index build (/usr/bin/plugins), the scanner throws an invalid URI error: error: attempt to map invalid URI `(null)` [lv2 @ 0x562f44ae54c0] Invalid plugin URI <(null)> PluginFFilter::new_ffilter(lv2) err: Invalid argument GVFS / GLib Symbol Error: /usr/lib64/gvfs/libgvfscommon.so: undefined symbol: g_once_init_leave_pointer Failed to load module: /usr/lib64/gio/modules/libgvfsdbus.so Fontconfig Warnings: Standard XML attribute warnings against local rolling-release font configs (harmless, but visible in terminal). Overall, my first impression is that the AppImage runs surprisingly well for a early test build! Terje

Sorry, my fault above. Of course Cinelerra needs to be loaded before verification with ~> xlsclients localhost.localdomain ibus-x11 localhost.localdomain cin localhost.localdomain mutter-x11-frames That is checking active clients via xlsclients confirms that cin is currently running under the XWayland compatibility layer by default on a Wayland GNOME session. It looks like this is standard behavior for Qt apps on Linux, unless the program or environment variables explicitly ask for the Wayland platform (QT_QPA_PLATFORM=wayland). Terje

Hi Terje, thank you for looking into the package. You are right: the AppImage carries only the X11 platform plugin of Qt, the Wayland plugins are not in it. There is a second half that your search could not show. The start script inside the AppImage (|AppRun|) sets |QT_QPA_PLATFORM=xcb| itself and so overrides what you set. Even with the plugins in the package you would still have ended up on XWayland. Both come from my build script, not from an accident in one build, and the new alpha AppImage of October 10 behaves the same. I will try to add Wayland as an opt-in:   - The build script packs the Wayland plugins of Qt as well.   - X11 stays the default, so nothing changes for anyone who just starts the AppImage.   - If you set |QT_QPA_PLATFORM=wayland| before the start, the program uses Wayland. One honest warning: the port has only ever been tested on X11, and all my scripted tests run there. I expect rough edges under native Wayland, most likely with the floating panels, window positions and the keyboard handling of panels. That is why it will be opt-in and not the default for now. I will write here when an AppImage with the switch is online. If you then try it, reports about what breaks would help me a lot. The bug tracker at https://bug.cinelerra-gg.org has a category *Qt6 Alpha* for this. Your compositor and distribution in the report would be useful. Sam Am 09.10.26 um 22:56 schrieb Terje J. Hanssen via Cin:

Hi again,

Following up on my previous test above: Because forcing QT_QPA_PLATFORM=wayland still resulted in Cinelerra running under XWayland (xlsclients confirmed cin), I decided to have a look at the internal contents of the AppImage (CinGG-qt6-20261001-x86_64.AppImage).

After extracting the package (--appimage-extract), I ran a search for the Qt6 Wayland platform plugins (*wayland*.so). The search returned no matches, confirming that the Wayland QPA plugins are currently omitted from this build bundle.

Because these plugins are missing from the package, Qt6 has no choice but to fall back to XWayland, even if the environment variable is explicitly set.

Just wanted to share this finding in case it's helpful for possibly adjusting the build scripts/recipes for later releases!

Terje _______________________________________________ Cin mailing list --cin@lists.cinelerra-gg.org To unsubscribe send an email tocin-leave@lists.cinelerra-gg.org

On 12.10.2026 04:43, Andrew Randrianasulu via Cin wrote:

https://mastodon.online/@Andrew_R/117425642798597682

I can't find Compositor Fullscreen option?

Me neither. I am able to click and drag the down-left corner and frames to extend the Compositor window. Then I wasn't able to get the main window in focus and front again (possibly there is a shortcut for this).

On Sat, Oct 10, 2026 at 10:38 PM Sam via Cin <cin@lists.cinelerra-gg.org> wrote:

...

Hi Terje,

thank you for looking into the package. You are right: the AppImage carries only the X11 platform plugin of Qt, the Wayland plugins are not in it.

There is a second half that your search could not show. The start script inside the AppImage (AppRun) sets QT_QPA_PLATFORM=xcb itself and so overrides what you set. Even with the plugins in the package you would still have ended up on XWayland. Both come from my build script, not from an accident in one build, and the new alpha AppImage of October 10 behaves the same.

I will try to add Wayland as an opt-in:

- The build script packs the Wayland plugins of Qt as well. - X11 stays the default, so nothing changes for anyone who just starts the AppImage. - If you set QT_QPA_PLATFORM=wayland before the start, the program uses Wayland.

One honest warning: the port has only ever been tested on X11, and all my scripted tests run there. I expect rough edges under native Wayland, most likely with the floating panels, window positions and the keyboard handling of panels. That is why it will be opt-in and not the default for now.

I will write here when an AppImage with the switch is online. If you then try it, reports about what breaks would help me a lot. The bug tracker at https://bug.cinelerra-gg.org has a category Qt6 Alpha for this. Your compositor and distribution in the report would be useful.

Sam

Am 09.10.26 um 22:56 schrieb Terje J. Hanssen via Cin:

Hi again,

Following up on my previous test above: Because forcing QT_QPA_PLATFORM=wayland still resulted in Cinelerra running under XWayland (xlsclients confirmed cin), I decided to have a look at the internal contents of the AppImage (CinGG-qt6-20261001-x86_64.AppImage).

After extracting the package (--appimage-extract), I ran a search for the Qt6 Wayland platform plugins (*wayland*.so). The search returned no matches, confirming that the Wayland QPA plugins are currently omitted from this build bundle.

Because these plugins are missing from the package, Qt6 has no choice but to fall back to XWayland, even if the environment variable is explicitly set.

Just wanted to share this finding in case it's helpful for possibly adjusting the build scripts/recipes for later releases!

Terje _______________________________________________ Cin mailing list -- cin@lists.cinelerra-gg.org To unsubscribe send an email to cin-leave@lists.cinelerra-gg.org

_______________________________________________ Cin mailing list -- cin@lists.cinelerra-gg.org To unsubscribe send an email to cin-leave@lists.cinelerra-gg.org

---

Cin mailing list -- cin@lists.cinelerra-gg.org To unsubscribe send an email to cin-leave@lists.cinelerra-gg.org

Thanks, Sam. Your AppImage amazes me more and more. To compile from source, can I follow the same steps I use for CinGG, or do I need to adjust them? - The Overlay filter doesn't seem to be working, while the overlay from the patchbay works fine. Just out of curiosity: are these the same algorithms as CinGG's, or are they different? - The ability to choose the type of trimming along the edge of the asset is brilliant, even if you have to zoom in on the track to be more precise. - I see some OpenCV filters; are these your new implementations? - There isn't the Sketcher plugin, do you plan to add it? - Speaking of “Color,” is it no longer possible to open Videoscopes from the ‘Viewer’ (not important) and “Compositor” windows? The Videoscope plugin configuration window can't be enlarged and is too small to be useful. - The drop-down menus in the Inspector and in the plugin's configuration window have a very saturated red background when expanded to show all values. - Sorry, I can't find the “QT6 Alpha” category in MantisBT.

Hi Andrea, (This should be the right thread now.) thanks for testing so thoroughly, this is exactly the kind of feedback I need. *Building from source:* the steps differ from CinGG. The Qt6 version builds with CMake, there is no autogen.sh, no configure and no thirdparty build. FFmpeg and the other libraries come from your system. To make it easy I added a build script. It checks what is needed, tells you which development packages are missing, then configures and compiles: |git clone https://git.cinelerra-gg.org/sam/cinelerra-gg-qt6.git| |cd cinelerra-gg-qt6| |cinelerra-5.1/tools/build_qt6.sh| |cinelerra-5.1/build/cinelerra/cin| Run it with --check first if you only want to see what is missing. You need GCC 13 or newer, CMake 3.22 or newer, Qt 6.8 and FFmpeg 7. If your Qt is not the one of the system, put QT_DIR=/path/to/Qt in front of the command. The program runs from the build directory, there is no install step. After a git pull just run the script again. The "Build" section of the README.md has the details. *Overlay filter:* I could not reproduce this one. The plugin code is CinGG's, unchanged. In my test it works when two video tracks share it: Overlay attached to the upper track, the same effect attached to the lower track as a shared effect, then "Multiply" or "Addition" in the Mode list. The Compositor picture changes right away. On a single track it does nothing, because the plugin needs two layers. Could you tell me how you set it up? How many tracks, attached as a shared effect or separately, and which mode? Then I can test exactly your case. *Trimming:* glad you like it. I noted that the grab zone at the edge is too narrow without zooming in. *OpenCV filters:* yes, these are new. Scene detection, temporal denoise, stabilize, face tracking, auto reframe, retimer and object mask. Treat them as experimental. *Sketcher:* it is planned. Sketcher, Crikey and Tracer read X11 events directly and have to be ported first. Titler is still missing too. Oil painting, Polar, Whirl, YUV and GreyCStoration were missing in your build and are back in the current one (CinGG-qt6-alpha-20261013). *Videoscope:* you are right, the button was missing in the new Viewer and Compositor. The current build has a scope panel instead: Window → Show Scopes, or "Scopes" in the context menu of the Viewer and the Compositor. It shows waveform, RGB parade, vectorscope and histograms, and you can dock it anywhere or put each scope into a panel of its own. The window of the Videoscope plugin that cannot be enlarged is still on my list. *Red drop-down lists:* found and fixed. The drop-down lists of the older plugin windows took a marker colour of the theme instead of the menu background. The current build has the fix. If you still see a red list somewhere, please tell me in which window. Sam Am 12.10.26 um 13:56 schrieb Andrea paz via Cin:

Thanks, Sam. Your AppImage amazes me more and more. To compile from source, can I follow the same steps I use for CinGG, or do I need to adjust them?

- The Overlay filter doesn't seem to be working, while the overlay from the patchbay works fine. Just out of curiosity: are these the same algorithms as CinGG's, or are they different?

- The ability to choose the type of trimming along the edge of the asset is brilliant, even if you have to zoom in on the track to be more precise.

- I see some OpenCV filters; are these your new implementations?

- There isn't the Sketcher plugin, do you plan to add it?

- Speaking of “Color,” is it no longer possible to open Videoscopes from the ‘Viewer’ (not important) and “Compositor” windows? The Videoscope plugin configuration window can't be enlarged and is too small to be useful.

- The drop-down menus in the Inspector and in the plugin's configuration window have a very saturated red background when expanded to show all values.

- Sorry, I can't find the “QT6 Alpha” category in MantisBT.

_______________________________________________ Cin mailing list --cin@lists.cinelerra-gg.org To unsubscribe send an email tocin-leave@lists.cinelerra-gg.org

Andrea, You can get past the "CMake Error at CMakeLists.txt:65 (pkg_check_modules): Unknown CMake command "pkg_check_modules"." by adding this line in cinelerra-5.1/CMakeLists.txt find_package(PkgConfig REQUIRED) before line 65 which reads: pkg_check_modules(X11 REQUIRED IMPORTED_TARGET x11) I will make note of this in the Bug Tracker qt6 category now that I know it is just not my problem. However, I next get this error which I have not diagnosed yet: make[2]: *** [cinelerra/CMakeFiles/cin.dir/build.make:7479: cinelerra/CMakeFiles/cin.dir/transcribe_engine.C.o] Error 1 Please let me know if you get this same error further along on your next attempt so I know it is just not me. Thank you, Phyllis On Wed, Oct 14, 2026 at 1:39 PM Andrea paz via Cin < cin@lists.cinelerra-gg.org> wrote:

I tried to build it using your commands, but I'm getting a CMake error. I'm attaching the terminal output and the `configure.log` file.

Anyway, don't waste your time trying to help me—I don't know anything about compiling, and I was only able to compile the classic CinGG because I copied and pasted the commands. It's up to you whether it's worth trying to figure out my problem or just letting it go.

Regarding the tests:

Overlay plugin: Sorry, it's my fault. I had forgotten that the “overlay plugin” is a shared effect, and I had placed it only on the top track.

Videoscopes: It's amazing! I don't know how to thank you.

Drop-down list: All OK, thanks.

PS: I tried launching CinGG-QT6 with `QT_QPA_PLATFORM=wayland`, and it seems to be working. But I'm not sure if I'm running on Wayland or XWayland. _______________________________________________ Cin mailing list -- cin@lists.cinelerra-gg.org To unsubscribe send an email to cin-leave@lists.cinelerra-gg.org

The line you added worked. But I stopped further along at a point that isn't the same one you found. I'm attaching the configure.log file.

You're right—the PATH was missing. After adding it to /usr/include, the compilation started. It stopped after 1–2 minutes with the following message: 1052:/home/paz/cinelerra-gg-qt6/cinelerra-5.1/guicast/errorbox.h:35:14: note: by ‘void ErrorBox::create_objects(const char*)’ Looking at .../cinelerra-5.1/guicast/errorbox.h on line 35, I find the following line: void create_objects(const char *text); But I don't know how to proceed from here. I'm attaching the build.log file. https://paste.c-net.org/TurksKeith

Andrea, NEVER MIND the last email -- Sam already fixed this so just "git clone" the latest QT6 version. On Thu, Oct 15, 2026 at 6:27 PM Phyllis Smith <phylsmith2017@gmail.com> wrote:

Andrea, the message you pointed out is just a warning, i.e. the one below:

...

1052:/home/paz/cinelerra-gg-qt6/cinelerra-5.1/guicast/errorbox.h:35:14: note: by ‘void ErrorBox::create_objects(const char*)’

several of these warnings are also in what Andrew is referring to as the "classic Cinelerra" (gg 5.1).

Looking for "Error " and "error:" in the log instead shows:

...

make[2]: *** [cinelerra/CMakeFiles/cin.dir/build.make:2621: cinelerra/CMakeFiles/cin.dir/ffmpeg.C.o] *Error* 1

...

/home/paz/cinelerra-gg-qt6/cinelerra-5.1/cinelerra/ffmpeg.C:1991:31:

...

*error:* ‘const AVCodec’ {aka ‘const struct AVCodec’} has no member named ‘supported_samplerates’ 1991 | const int *p = codec->supported_samplerates; | ^~~~~~~~~~~~~~~~~~~~~

It looks like you must be running FFmpeg 9.x which is good but the modifications needed for the deletion of the deprecated "const AVCodec" have to be propagated to cinelerra/ffmpeg.C, cinelerra/fileffmpeg.C, and cinelerra/fileac3.C (although I did not see a fileac3.C error message in your build log).

Modifications needed to correct the "error:" messages and hopefully get you further along can be found in:

...

https://git.cinelerra-gg.org/?p=goodguy/cinelerra.git;a=commit;h=e0902d80ebf...

but I will add a Mantis Bug report for this and provide a patch there if I can get it done tonight yet.

Thank you for providing the log file and Please keep them coming!

On Thu, Oct 15, 2026 at 1:11 PM Andrea paz via Cin < cin@lists.cinelerra-gg.org> wrote:

...

You're right—the PATH was missing. After adding it to /usr/include, the compilation started. It stopped after 1–2 minutes with the following message:

1052:/home/paz/cinelerra-gg-qt6/cinelerra-5.1/guicast/errorbox.h:35:14: note: by ‘void ErrorBox::create_objects(const char*)’

Looking at .../cinelerra-5.1/guicast/errorbox.h on line 35, I find the following line:

void create_objects(const char *text);

But I don't know how to proceed from here. I'm attaching the build.log file. https://paste.c-net.org/TurksKeith _______________________________________________ Cin mailing list -- cin@lists.cinelerra-gg.org To unsubscribe send an email to cin-leave@lists.cinelerra-gg.org

Hi everyone, thank you for testing the Qt6 AppImage of October 1 and for writing down what went wrong. Here is what became of each report. The fixes are in the new alpha AppImage of October 10. * 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> Fixed The first seven have a scripted test in the repository. I ran these tests on the published AppImage of October 10, and all of them pass. The last point is checked by starting the AppImage in a Fedora 44 container. What you reported What it was Now View → Fade does not switch the fade line off. The setting changed, but the timeline was not redrawn. The same held for the other automation entries of the View menu. The timeline redraws at once. The mask tool does not work properly: the picture in the Compositor stays unmasked. New projects use RGBA. In RGBA the stopped frame showed neither masks nor fades, the rendered file was right. The stable AppImage of February behaves the same way. The Compositor shows masks and fades of RGBA projects. The mask tool opens two windows. The old tool window opened next to the new Qt6 panel. Only the Qt6 panel opens, and the toolbar follows the tool. Making a PNG clip longer freezes the program. No freeze: the trim preview stayed in the Compositor after the trim and covered the picture. A click in the Compositor, moving the playhead or starting playback ends the preview. In cut-and-paste mode, dragging on the time ruler does not scrub. The Qt6 ruler selected a range there instead. It scrubs in both editing modes, as the stable version does. Dragging with the I-beam on a track moves clips. A wrong mouse position check, found while testing the point above. Fixed. Plugin windows in the Inspector: the sliders of Color 3 Way do nothing, a click on the Histogram curve lands in the wrong place. A docked plugin window kept its old top-level window, so mouse positions were off. Both work. Fontconfig warnings in the terminal at start. The AppImage carried its own older fontconfig. It uses the one of your system. My check in a Fedora 44 container shows no warning. Not fixed, or not changed on purpose * *Red lines on audio tracks.* Not confirmed as fixed. I cannot reproduce them here. A screenshot from your machine with the new AppImage would help me a lot. * *Mask tool, two smaller points.* A click that misses a mask point inserts a new point, and the tool panel can squeeze the Compositor picture when it is docked narrow. I have not rechecked these on the new build. * *Histogram in the Inspector.* Its window has a fixed size and does not fit a small dock. Scroll, or pull the dock out of the main window. * *Roll stops at a gap that follows.* The stable version does the same, so I left it. * *Wayland.* The AppImage runs through XWayland. A native Wayland start is not there yet. If something is still wrong Please tell me if one of the fixed points still happens for you, or if I misunderstood a report. The bug tracker at https://bug.cinelerra-gg.org has a new category *Qt6 Alpha* for this. What you clicked, what you expected and what happened is all I need, a screenshot helps. 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. Sam Am 06.10.26 um 23:00 schrieb Terje J. Hanssen via Cin:

Sorry, my fault above. Of course Cinelerra needs to be loaded before verification with

~> xlsclients localhost.localdomain ibus-x11 localhost.localdomain cin localhost.localdomain mutter-x11-frames

That is checking active clients via xlsclients confirms that cin is currently running under the XWayland compatibility layer by default on a Wayland GNOME session.

It looks like this is standard behavior for Qt apps on Linux, unless the program or environment variables explicitly ask for the Wayland platform (QT_QPA_PLATFORM=wayland).

Terje _______________________________________________ Cin mailing list --cin@lists.cinelerra-gg.org To unsubscribe send an email tocin-leave@lists.cinelerra-gg.org

Igor, not sure yet but I can see the value of creating an AppImage for specifically Ubuntu 16 so there is more initial testing. I plan on trying to create one on my Ubuntu 16 distro eventually but no immediate plans yet. ... Phyllis On Sun, Oct 18, 2026 at 2:05 AM Igor BEGHETTO via Cin < cin@lists.cinelerra-gg.org> wrote:

I tried to run the "CinGG-qt6-alpha-20261015-x86_64.AppImage" on my OS: UbuntuStudio_16.04_64bit. It, unfortunately, doesn't start. Terminal says: /tmp/.mount_CinGG-SUcCE5/usr/bin/cin: error while loading shared libraries: libGLX.so.0: cannot open shared object file: No such file or directory

Will there be no chance that it will work on older operating systems?

Thank you. IgorBeg

PS: a great job, you are doing!

Il 06/10/2026 19:42, Phyllis Smith via Cin ha scritto:

Some minor feedback and just a reminder that *you have to have a more up to date/newer Operating System to run the AppImage*.

_______________________________________________ Cin mailing list -- cin@lists.cinelerra-gg.org To unsubscribe send an email to cin-leave@lists.cinelerra-gg.org

You’re right the world of technology moves fast, perhaps too fast (...for me). Phyllis, thank you for considering a version for Ubuntu 16 but, please, don’t worry about it; I’ll just keep an eye on your feedback and the development of the QT6-based version, and we’ll see how things go. Thanks! And thank you, Andrew_R, for the constant updates you provide; it’s something I never take for granted. Il 19/10/2026 04:38, Andrew Randrianasulu via Cin ha scritto:

вс, 18 окт. 2026 г., 22:32 Phyllis Smith via Cin <cin@lists.cinelerra-gg.org <mailto:cin@lists.cinelerra-gg.org>>:

Igor, not sure yet but I can see the value of creating an AppImage for specifically Ubuntu 16 so there is more initial testing. I plan on trying to create one on my Ubuntu 16 distro eventually but no immediate plans yet. ... Phyllis

I am not sure you can build qt6 on Ubuntu 16. Linux world moves fast and breaks itself.

May be try those Anylinux appimages?

On Sun, Oct 18, 2026 at 2:05 AM Igor BEGHETTO via Cin <cin@lists.cinelerra-gg.org <mailto:cin@lists.cinelerra-gg.org>> wrote:

I tried to run the "CinGG-qt6-alpha-20261015-x86_64.AppImage" on my OS: UbuntuStudio_16.04_64bit. It, unfortunately, doesn't start. Terminal says: /tmp/.mount_CinGG-SUcCE5/usr/bin/cin: error while loading shared libraries: libGLX.so.0: cannot open shared object file: No such file or directory

Will there be no chance that it will work on older operating systems?

Thank you. IgorBeg

PS: a great job, you are doing!

Il 06/10/2026 19:42, Phyllis Smith via Cin ha scritto:

...

Some minor feedback and just a reminder that *you have to have a more up to date/newer Operating System to run the AppImage*.

_______________________________________________ Cin mailing list -- cin@lists.cinelerra-gg.org <mailto:cin@lists.cinelerra-gg.org> To unsubscribe send an email to cin-leave@lists.cinelerra-gg.org <mailto:cin-leave@lists.cinelerra-gg.org>

_______________________________________________ Cin mailing list -- cin@lists.cinelerra-gg.org <mailto:cin@lists.cinelerra-gg.org> To unsubscribe send an email to cin-leave@lists.cinelerra-gg.org <mailto:cin-leave@lists.cinelerra-gg.org>

_______________________________________________ Cin mailing list -- cin@lists.cinelerra-gg.org To unsubscribe send an email to cin-leave@lists.cinelerra-gg.org