Shotcut crashes if you enter region size = 1. It’s about the “Motion Tracker” filter. If you need to enter the size of a region whose number starts with the number 1 - for example, I wanted to manually enter 128.
If you add a counter to the timeline and switch the video mode, the application crashes.
If you close the current project and discard changes, the screen will be black.
On Windows 10, I have the same problem, except that Shotcut crashes when typing “2”.
“1” works fine though.
I couldn’t reproduce those on Windows.
I noticed that the problem with the black screen and the crash of the counter only appears when the gpu-effects mode is activated.
Ok, I get it too when GPU is ON
But in my tests, it only happens when switching to a 720p mode from any other mode.
It won’t crash if I switch between any of the 1080p modes for example. Or from a 2160p mode to a 1080p mode.
I didn’t get that black screen problem with GPU ON though.
I can surmise that this failure may be caused by a feature of the graphic drivers in the linux system. It is updated here very often, and every time some glitches disappear and others appear, it may well be that I was just unlucky and I need to wait for a driver update. But to be fair, updating drivers doesn’t have such a dramatic effect on other software, including other graphics editors.
Minor issue I just noticed: after popping up the timeline panel right click menu doesn’t appear anymore (even after docking it back into its original place).
I don’t like the light theme. Everything is way too bright. Is there a way to change back to a dark theme?
These instructions are for an older version. “Theme” isn’t available as far as I can see.
This was explained in the Beta thread:
1 Like
If you’re using Linux, just don’t use appimage. In the normal version, the theme is dark, or rather depends on the system settings, and my system theme is dark.
The filter set is a nice new feature. After the set is added, you can’t delete any of the filters in the set. It doesn’t prevent you from adding new filters. But if you don’t want a filter from the set, all you can do is deactivate it.
If you right-click on an unnecessary set, the program will prompt you to delete it. It’s not a very obvious way, but it’s there nonetheless.
Before we dig into this, can you please confirm that this is a regression in the 23.04.20 release candidate? Please test with the current release 22.12.21 and see if the behavior is the same. If the behavior is the same in 22.12, then please start a new thread to keep this thread focused on the changes for this release.
I’ve been getting crashes on Windows. It seems to happen when Windows turns the monitor off. details in github.
This is fixed.
1 Like
This is fixed for the release.
1 Like
Shotcut crashes if you accidentally try to convert a video that is missing. I understand that this is an absurd action, but you can accidentally click on this button and lose data. I ask you to make some kind of “stub”, for example, so that some kind of message appears that “it is impossible to convert the video because it was not found.”
Scenario: clip on the timeline but you’re zoomed in so the beginning of the clip is outside visible limits.
Double-click on the clip in the timeline seeks to the beginning of the clip → working.
Timeline scrolls horizontally so that the seek point / beginning of the clip is visible → not working.
Don’t know if I, understand your case correctly, but this is how it works for me