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.

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.

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.

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 to cin-leave@lists.cinelerra-gg.org