Before anything, there are two types of Advanced Keyframes: One where the keyframes just move left and right and the other where there is a graph that allows the keyframes to move up and down as well . What are the names of those two different types of Advanced Keyframes?
In Advanced Keyframes, when the keyframe timeline is zoomed in the seeking is inaccurate after the keyframes are moved. Also, they stutter as they are being moved around. This happens with both types of Advanced Keyframes. Demo
When you have an Advanced Keyframe selected and you manually move it up and down, the value in its parameter does not update along with the up and down keyframe movement. Demo
Make a transition clip. Change the transition from Dissolve to Cut. Then from Cut go back to Dissolve. Then once again go from Dissolve to Cut. The Cut selection will be ignored and instead will stay at Dissolve. You won’t be able to choose Cut again. Here’s a demo.
Clips that are overwritten by a clip that is made longer by speed change don’t get undone. In this demo, I show the very first frames of the clip I will overwrite to show what the first frames should be. I bring to the timeline the clip that I will overwrite with. I made that clip longer which then overwrites the first clip. I then undo those actions so that it’s before the second clip is brought down and I show that the first frames are not what they originally were.
In Text: HTML, selections for font size, font name, background color, text outline and text shadow are not remembered by the parameters in the HTML Editor. So if you make a selection or enter a value then go back to that parameter make a change, the values that come up in the windows are their defaults rather than what was last set. Instead of this, there should be a default button in each of those parameters.
In Text: HTML, the menu to select colors doesn’t have a parameter for alpha channel. Therefore, if you pick for example a background color but then decide to make the background color transparent again, it seems there is no way to revert back to full transparency.
In Text: HTML, if you add a text shadow to a text then hit the delete or backspace key to bring the text up, the text shadow will be removed. Demo.
If you are on the Source tab to add filters to a clip on the playlist then switch to the Project tab and try to add a filter to a clip on the timeline by hitting Enter on the keyboard, the focus switches from Project to Source rather than staying on the Project tab.
Sorry but I do not plan to address most of these. Some of the ones related to the HTML editor are nearly impossible due to technology limitations. I have a full slate for the next release already and then moving on to bigger things in the engine. Maybe someone else will volunteer.
This bug I’ve noticed since the last beta (19.13) but it’s only now that I’ve finally seemed to have found the trigger! So there is a bug that has multiple clips being selected even when you don’t want to and Shotcut doesn’t respond if you choose to deselect them. The trigger seems to have something to do with adding new video tracks. When video tracks are added, the multi-select bug starts happening. Here is a demo.
There might be something else that can trigger it also because right at the start of my demo I try to deselect the first clip I put on the timeline and it wouldn’t deselect. Still, it’s been a consistent pattern that every time I add a new video track this multi-select bug happens. Here is a 2nd demo that shows how adding new tracks above already existing ones that have clips on them can multi-select all the tracks below.
The Gaussian Blur is buggy. When you start raising the value past 90 the video starts getting totally messed up. This has happened on some 4K videos. I haven’t seen this happen yet on a 1080p video but that doesn’t mean it won’t. My demo here shows this with the 4K upload of the Blender short Big Buck Bunny.
11) The audio in the player is out of sync. I made a demo to highlight this. I first show the original clip then follow it up with how it compares to it being played in Shotcut. Note the moment when the acorn lands on the bird’s head. In the Shotcut player, the sound of the hit comes in a little later than it should: https://streamable.com/9x5dh
It doesn’t seem to affect the export though. However, this does make it difficult to do precise audio and video syncing. The file I used is the 4K 60fps upload of the Big Buck Bunny short. I’ve noticed this issue also with 1080p videos.
12) Add the Choppy, Stabilize, Rutt-Etra-Izer or Text: HTML filter to a video. Add a transparent clip above it. Set the Preview Scaling to 360p or 540p. Have the playhead pass through the section with transparent clip. Shotcut will crash. If you have the Preview Scaling to 720p Shotcut will not crash but instead of the text appearing there will be a visual glitch.
13) The Cut option in Transitions is broken. This issue seems to be related to bug #3 in this thread’s report which hasn’t been addressed yet. Now I have discovered that you can’t even save a Cut transition in a project. If you do try to save the project with Cut chosen:
then reopen the project file, the selected transition will be as a custom transition:
14) If you change the type of transition on a transition clip Shotcut won’t note that with an asterisk as a change that needs to be saved.
15) The animation in Simple Keyframes from the drag handle doesn’t start until two frames after. When going from the trim handles in Simple Keyframes, the animation starts one frame after. However, when going from the drag handles, the animation doesn’t start until two frames after the drag handle. In this demo, I start by showing the animation from the trim handle and how it starts one frame after then show how it takes two frames from the drag handle until the animation starts.
16) Changing the size of the track heights in the keyframes timeline doesn’t move in smaller steps like it does now in the main timeline. Demo.
17) In a fresh timeline, add a video clip then add a text clip above that video track. After dropping the text clip into the timeline the playhead will seek to the end. Demo.
18) Add the Trails filter to a video clip. Put a text clip above that video clip. When the playhead gets to the start and end of the text clip, the Trails filter will stop working. Demo: https://streamable.com/j4upv
This crash is fixed for the next version, but by disabling compositing when a filter does not support preview scaling (those you mentioned). I am trying to find a way to restore composting but no solution yet.
UPDATE: I made another fix to restore the compositing as well, which it will do at preview scaling resolution.
Keyframes panel mouse wheel behavior is now updated to be like Timeline for the next version.
17 ) In a fresh timeline, add a video clip then add a text clip above that video track. After dropping the text clip into the timeline the playhead will seek to the end.
This one is already fixed by the recent change related to not treating every video refresh as a current time position change.
I tested this fix and I am confused. I add the Choppy filter and the whole Preview Scaling is disabled. But when the playhead passes a point where right above it is a transparent clip the Preview Scaling is activated while the Choppy filter is still running. Then when the transparent clip ends the Preview Scaling is disabled again.
Why limit the Preview Scaling when it’s under a transparent clip? If it can handle it when it’s under a transparent clip doesn’t that mean it can handle it all the time?
When track blending is required, each track input to the blender must be the same size. Therefore, with filters that are incompatible with preview scaling, it still processes the filter at full project resolution and then must do an additional downscale to make it match. This is not ideal, but the blend component has no insight into whether some other component supports preview scaling, and it is better than upscaling the other input that is already at preview scale.
If it can handle it when it’s under a transparent clip doesn’t that mean it can handle it all the time?
Yes, but then it would add the overhead of additional scaling all of the time an incompatible filter is on the clip, which is counter the goal of preview scaling.
