I right clicked on a clip, went to properties, and changed the speed to .8, that worked.
Then a problem started. Every time after that when I tried to change the speed of the same clip, Shotcut would crash.
Now, when I change the speed of the clip, it simply reverts back to .8 without keeping my changes. I have tried reloading the project multiple times and have tried clicking out of the speed window and hitting enter in an attempt to get the new speed to stick. No avail.
Works for me. Maybe it does not work for an existing project. Maybe it depends on something we have not identified. If you spell out your steps exactly or show a screencast showing how to do it from an empty project, it might help.
I see it, but strangely I still do not reproduce it. I tried with both video files in the same directory as the project file (uses no or relative path for file name links) and video files in a different directory or drive. Are you using network paths (\server\share…). I even tested that without a problem. Can you attach your project file?
I have attached the file; the two clips that I am trying to change begin at 6:56 and end at 7:14
You will notice that the file name includes the word ‘Repaired’ three times. This is either due to the program crashing or my computer, I have been dealing with both. I’m not sure if this information is useful to you but the computer crashing is, I believe, due to problems with my SSD. The computer is only two weeks old so it could be driver issues.
It is strange that I still cannot reproduce it. However, I see a minor problem in your file on the speed-changed clips related to this:
The resolution of that does not fix existing projects that have this minor pollution.The only thing I can think of to try is this new project file with my manual cleanup for that change and one other thing…
Thank you so much for your help with this. I am having to replace a two week old computer so I may drop off the radar for a short bit here.
Concerning the two clips that are borked, since they come from the same source as the rest of the project, and the rest of the project seems to be working fine, should I simply remove and re-add those clips?
double-click the clip to select it and position the play head to its beginning
click Copy on the timeline toolbar
switch to the Source player
change Properties > Speed
click Paste or Overwrite (V icon) on the timeline toolbar
Paste will do a ripple insert whereas overwrite behaves like changing speed of a timeline clip.
I have kind of a similar issue - whenever I try to change the speed, Shotcut crashes, whether I intend to alter the speed of a stand alone file or a split part of a longer project. Tried your suggestion, but after decreasing the speed, as soon as I click away, Shotcut crashes.
What is your version? What is the speed you are trying to change it to? v19.04.30 and later contains the fix mentioned here. However, even in these versions, we found a bug that setting the speed too low is causing a crash. This low speed value was easily achieved by using the arrow buttons on the field or the mouse wheel. That was fixed in the v19.07 beta.
It can also be that some clips for some reason cause a problem. Do you always try with the same clip or the same kind of clip (e.g. same camera or capture tool)?
Been using the latest version 19.06.15 on Windows 10 64 bit… I encounter the crash with the same video file captured with an Android smartphone. I can slow mo with Shotcut other videos captured with this device. This particular file is bigger (around 800 MB) shot with multiple pauses (not sure this info is of any importance). Also I have already edited (splitting, trimming) the video up to the part I wish to slo-mo. Here, I’ve tried to decrease speed to 0.500 (half). Language is set to English.
Your target speed of 0.5 is fine and not what we consider too low. The new minimum is 0.0025.
Yes, that file is going to be problematic probably even without speed change. I recommend that you use Properties > menu > Convert to Edit-friendly… and then replace that clip with the converted one.
Really appreciate your support. Indeed the Edit-friendly conversion has solved the slo-mo crashes, but…the resulting files were HUGE: best quality around 11 GB, the good Q 9 GB and the better almost 4 GB…