BETA version 26.9

[TLR_Pictures]

Thanks @SimPaulJack I did manage.

[Patrice]

@shotcut

See this build log prints the AppImage URL

From the build-linux workflow where each run summary includes the portable as an artffact. Also, it publishes to the “edge” channel for Snap.

Thanks, but from those links how we download the appimage? I tried to click on every “appimage” it redirect or does nothing

[shotcut]

http://builds.us.meltytech.s3.amazonaws.com/shotcut/shotcut-linux-x86_64-26.9.19.AppImage

[Patrice]

Thanks a lot, I also can confirm (if ever it’s needed) that on Shotcut version 26.9.19 there is no more bug about the auto audio ducking and other properties, it is working flawlessly.

@Patrice

Linux mint 22.3, Shotcut version 26.9.6 appimage

I got a problem with audio auto ducking and the other one proprieties on image.

When selecting the track the FIRST time, it is there, I select a clip on that track, then select the track back, no more access… I need to restart shotcut

[brian]

@jonray

checkbox OFF by default, with NO sliders / labels visible. Just blank.
Checkbox ON, all sliders become visible. Threshold set to a fairly high level, say 75%.
Would that work, and is it possible?

That wold work, and your example is very clear. But that does not align with the existing patterns we already have in Shotcut - we do not ever HIDE controls that depend on other controls. The UI framework has a different option: DISABLE - which keeps the control visible, but it does not do anything. I’ll play around with some ideas.

[jonray]

@brian

That wold work, and your example is very clear. But that does not align with the existing patterns we already have in Shotcut - we do not ever HIDE controls that depend on other controls.

Very good point, @brian. I completely understand and see your point.

@brian

The UI framework has a different option: DISABLE - which keeps the control visible, but it does not do anything. I’ll play around with some ideas.

Good point also. Congratulations on your great work on this feature!

[wHiptHor]

Hi! I found a slight regression in this new version (26.9.6 appImage on Windows64 and 26.9.15 self compiled on linux mint 22.3) regarding the CUT tool (Split at Palyhead). When I select more than one tracks (video + video, video + audio, audio + audio) (ctrl+left mouse click), the tool only cuts the first track. Previously, all the tracks were cut out. Thank you again for this wonderful job !

Shotcut 26.9.6 BETA - Light bug on multi selected tracks cut

[Patrice]

@wHiptHor

When I select more than one tracks (video + video, video + audio, audio + audio) (ctrl+left mouse click), the tool only cuts the first track. Previously, all the tracks were cut out.

I confirm, not the same behavior than in 26.6.25, in 26.8.1 (those are appimage I still have), it cuts one clip at a time in the 26.9.15

Previous version behavior (cut 2 selected clips at once) in 26.8.1:

[shotcut]

@wHiptHor

(Split at Palyhead). When I select more than one tracks (video + video, video + audio, audio + audio) (ctrl+left mouse click), the tool only cuts the first track. Previously, all the tracks were cut out.

Thanks, this is fixed for the release.

[ConteudoAnimal]

Hello

I tried to move video track to up and down … it changes … but the track name keep unchanged …

My example I recorded horizontal and want to get vertical … I added same video with size position and rotate to cover the black bar

[shotcut]

@ConteudoAnimal

I tried to move video track to up and down … it changes … but the track name keep unchanged

I think what you are reporting is long existing behavior. If you do not rename the tracks and then reorder them, they are automatically renamed based on their position. In your example, when you move V1 up, the top track is still V2–by design, not different in this version, and no plans to change it.

[ConteudoAnimal]

@shotcut

isting behavior. If you do not rename the tracks and then reorder them, they are automatically renamed based on their position. In your example, when you move V1 up, the top track is still V2–by design, not different in this version, and no plans to change it.

thx for feedback

[wHiptHor]

Thanks a lot from south of France

[MusicalBox]

Tiny bug in beta version

When dragging a non-seekable file in the Source panel, the space next to the Timecode isn’t wide enough to display the words “Not Seekable”

Version 26.9.15

Version 26.8.1