This is a pretty stable release. Not a whole lot of problems Iâm noticing.
Undo doesnât bring back markers after ripple delete if clip in point is the same as timeline 00:00:00.
Ripple markers with edits needs to be turned on.
I canât hold a mouse button on the up or down button of the Start or End spinbox in the markers dock to make a continuous increase or decrease. Itâs possible in the marker edit dialog as well as all the other spinboxes that I can use in Shotcut.
This is not really a bug, but UI inconsistency.
I may not be using the markers correctly but, If I highlight a marker shouldnât the information of the highlighted marked be updated in the rename texbox, colour and the start/end/duration? In the image here I clicked on marker 3 which then highlights but the data below still shows the last clicked marker information, marker 2.
Edit: Just noticed in the screenshot - Looking at the duration of marker 2, there is a disparity of 1 frame. Top shows 05:17 and bottom shows 05:18, again not sure this is intended.
Your understanding is correct. But I can not reproduce the problem you report (and clearly illustrated in your screenshot). I tested in both Windows and Linux and the marker editor always matches the selected marker. Maybe there is a trick to it - like click fast or something? How easily do you produce it?
Iâve used Override Frame Rate in Convert To Edit-Friendly to try and convert several files to 29.970030 but instead they are coming out as 29.970000.
Iâm testing the beta. I donât know if it happened in previous versions, but the STITCH REMOVAL filter is out of order, the marking is in one part and the hiding is in another. Another detail (I did the print), the delay in exporting the file, almost three hours.
@brian, looking at @PaulusMaximus picture of the Markers panel reminded me of something I forgot to mention in my Markers thread:
Is there another way to have a selection on the list be highlighted? The way that it is now the blue highlight covers up the color of the marker. I wonder if there is another way to highlight the selection without ever covering up the color of that selection with the blue highlight.
I am not seeing any problem with Spot Remover filter or export speed. For speed, you need to compare the same project and export option with a previous version.
While a video is playing go to its Propertiesâ panel and change the Rotation to either 90 or 270. Shotcut will crash.
Shift + Ctrl + M is too many keys for such a simple function of deleting one marker. Why not repurpose Z or Backspace to be the delete key for markers? I think itâs a waste to have three different keys for one function (i.e. Lift) when at least one of those two extra keys can be used to delete markers which would make that action far easier to do with the keyboard. Between Z and Backspace I lean towards Z since itâs on exactly at the other end on the same row on the keyboard as M.
I had noticed this previously and took a quick look at it. The highlighting behavior is controlled by our GUI toolkit and the highlight color is driven by the theme. So I would have to re-implement a lot of functionality that is provided by the toolkit in order to change the highlighting. I decided to spend my time on other things.
Speaking of marker colors:
The font color is chosen based on the background color. Thus the text is displayed in white when the background is dark and in black when the background is light.
However this does not always work, for example for blue. The text is in black and would be more readable if it was in white.
It uses a simple heuristic based on the âvalueâ of the color per the HSV color model. The same is used in the color clip Properties. The value of pure/full blue is the maximum value. Thus, making it work for pure blue would always make the text white. So, I tried using âlightnessâ per HSL, and the lightness of pure blue is 0.5. When I change the threshold to that inclusive, then the lightness of pure green and yellow are the same lighness and white on those colors is mostly unreadable. I also tried building a text color from hue, 0 saturation, and 1.0 - value; but that did not work either. This is not important enough to get fixed before the release, and maybe eventually someone will make a code contribution.
