Confusing snapping with playhead: please highlight reason

I just tried to crossfade two clips and didn’t manage to do it. Eventually I figured out that the playhead was very close to the clip end of the first clip, and the second clip was always snapping to the playhead instead of crossfading.

It would have been immediately obvious to me if the snapping would somehow highlight or blink the reason for a snap position. So in my case, the clip would have snapped to the playhead and the playhead would have bounced, or blinked, or zoomed, something fun but small that doesn’t irritate after a while.

TL;DR: please provide more visual feedback on snapping

1 Like

Do you have the “snapping” turned on (magnet highligthed)? Than it can be tricky to overlap the clips. Maybe you also have to increase the timeline resolution (zoom in) to have more visual feedback for the action.
What i would like to see is to be able to manually re-adjust the blending zone, i.e. to move the clips closer over each other or to spread them. Or a kind of (adjustable) default value (e.g. 2 sec.) for the crossfade, so every crossfade has the same duration. This is kind of hard to achieve manually.

1 Like

Yes but I tried turning it off too, to no avail. Only when I noticed the playhead and moved it away did I manage to crossfade.

C’est parce que j’avais le même problème que vous que j’ai rajouté sur la barre de titre de la timeline une zone de saisie et 2 boutons.

It’s because I had the same problem as you that I added on the title bar of the timeline an input field and 2 buttons.

Pour reprendre votre exemple, si je souhaite une transition d’une seconde, je saisi 30 dans la zone (projet en 30 ips). Je positionne la playhead au début du clip 2 et je clique sur le bouton de gauche. La playhead recule exactement de 30 images. Avec l’aimant activé, il est alors très facile de déplacer le clip 2 pour créer une transition d’exactement 1 seconde. Démo

To use your example, if I want a transition of one second, I enter 30 in the field (project in 30 fps). I position the playhead at the beginning of clip 2 and I click on the left button. The playhead moves back exactly 30 frames. With the magnet activated, it is then very easy to move clip 2 to create a transition of exactly 1 second. Demo

J’ai aussi rajouté un bouton après le curseur de zoom. Ce bouton reset la valeur du zoom pour que tout le projet tienne sur la timeline.

I also added a button after the zoom slider. This button resets the zoom value so that the whole project fits on the timeline.

Pour ceux que cela intéresse, voici le fichier modifié.

For those who are interested, here is the modified file.

TimelineToolbar.qml.txt (11.5 KB)

After removing ‘.txt’ put it in /Applications/Shotcut.app/Contents/Resources/shotcut/qml/views/timeline/

(Before make a copie of the original file)

8 Likes

This is very cool, thank you, Namna! These are very helpful tools, esp. appreciate the button to zoom to video length!
This should be put into standard default values, also the “zoom to fit”-button, rather than modification i guess! This is of great help to everyone :slight_smile:

Absolutely, those buttons to move the playhead by X frames are brilliant for making transitions. Thanks for sharing, I’ll add this to my toolbar too.

The zoom fit is pretty cool too!

Merci, je suis content que d’autres utilisateurs aiment ceci

Thanks, I’m glad other users like this.

Please submit this as a pull request, but NOT the other thing to move the playhead by N frames. That will not be accepted. Use keyboard shortcuts that seek by seconds instead.

Is there a keyboard shortcut I’m not aware of? I don’t know what to do for a 60fps video that needs a bunch of half-second transitions set up. The only keyboard shortcut I know for that scenario is hitting the left arrow key 30 times, which is what made the N frames feature attractive. I’m aware the slideshow generator is a possible solution, but that doesn’t help align stinger transitions.

Page Up (-1 second) & Page Down (+1 second) ?

Right, but that doesn’t solve the scenario I posed. What would someone do for a half-second jump at 60fps that doesn’t require 30 keystrokes? As in, what’s a fast way to set up the playhead for transitions that aren’t exactly one second long?

Honestly, I don’t see all this as a big problem. After a couple of times swearing because the playhead was in the way, I just learned to move it away before dragging a clip to create a transition.

For single-track overlapping transitions, agreed, there isn’t an issue. But for two track cross fades, or for stinger transitions that involve graphics on a higher track that start a half second before the end of the clip, this is a very big deal. This applies to J- and L-transitions as well, where audio (usually dialog) comes in a little before or after the video cut point. N-frame advance is also very useful for setting up keyframe animation points on a cadence.

Hopefully this appeal doesn’t come across as obnoxious. I respect Dan’s decision to not include the feature. On rare occasion, I feel there could be virtue in making a case for a feature if its benefits have not been well-documented. But if No is still No, then I don’t bring it up again. :smile:

1 Like

I just saw this post now. I had made this suggestion for this very button back in February in this post:

Thank you very much, @Namna for creating it! :smiley:

1 Like

I agree. I saw it yesterday after I installed version 20.09.13. I love it. Thanks @Namna for the contribution. And thanks to @shotcut for including it along with the other great new features, changes and fixes. :+1: :+1:

@namna, I am seeing this thread for the first time very late and just spotted your toolbar modifier:

Shotcut Toolbar frame seek

I know @shotcut doesn’t like it and has rejected it, so it won’t be added as a regular feature of SC but I’d like to put my view that for me it is a fantastic tool and I will be using it often. Thank you so much!

It’s perfect for making, say, 7-frame transitions (eg the motion-blur transitions for which I’m trying to prepare a tutorial for).

Also great for seeking through a clip to find a place to make a cut, when the 1-second shortcut is too long and single-frame advancing is too short (having the ability to jump just 10 frames at time is SO useful)!

Also, for setting at the value of 1 second (eg 25 for a 25fps video) to advance or reverse by 1-second steps without having to keep finding the page-up or page-down keys (when working at speed) is in my view, brilliant.

Thanks!! :+1: :+1: :+1: :+1:

(I’m with @austin , in favour of this!!)
PS On my system the path to the timelinetoolbar qml file is different to yours:
Program files/shotcut/share/shotcut/qml/views/timeline

3 Likes

Hi @austin, I found that it’s possible to use a simple AutoHotkey script to move the playhead a specific number of frames (Windows only).

  1. Download and install Auto HotKey.

  2. Copy /paste the following into Notepad.

    SetKeyDelay, 80
    
    ^0::
    send, {right  10}
    return
    
    ^9::
    send, {left  10}
    return
    
  3. Save it but change the extension from .txt to .ahk.

  4. Right-click the AHK file and select “Run Script”

  5. Open a Shotcut project.

When on the timeline, pressing CTRL/0 will advance the playhead 10 frames; pressing CTRL/9 will reverse the playhead by 10 frames.

I’ve set the “SetKeyDelay” parameter to 80 (milliseconds) to move the playhead slow enough for it to work in Shotcut. You could change to a lower value but it may be too fast to work properly.
By using proxy editing you should be able to use a lower value, especially for reverse movement.

Change the number 10 in the AHK script to change the number of frames.

Even better, you could set up different AHK hotkeys to trigger different frame distances - so for example the script below uses the numberpad keys to advance the playhead 5, 10, or 15 frames when pressing numberpad 1, numberpad 2 or numberpad 3, for example (when Num lock is on).
(I find this script very useful for locating precise spit points when I need to convert a long clip into individual scenes).

numpad1::
send, {right  5}
return

numpad2::
send, {right  10}
return

numpad3::
send, {right  15}
return
1 Like

That’s a clever use of AutoHotKey. I’ll consider using it if I get tired of reapplying the Namna mod some day.

1 Like