Continous playback when arrows are pressed

Hi, this suggestion, obviously goes to the devs. My main use for this nice program is to cut the interesting parts of long recordings, to can after, trash the raw recording. This, at least to me, is like “debugging” a recording (and obviously lighten it)… anyway, i guess you got it. The fact is, that making that, i use intensively the frame by frame to find the right cuts in the video track. If the target frame is far, i use the mouse to aim more or less where i want to put the playhead. But if the playhead is near i prefer to use the side arrows keys (← → keys) to find the frame for cutting a clip. Ok, but sometimes, i have the `playhead to near, as for using the mouse to move it, but to far, as to have to press many times the arrow keys to reach the target frame.
So, why not to enable the possibility of can leave an arrow key pressed for a continous playback (forward and backward playback)?
I mean, if you short press an arrow key, normal frame by frame playback function. But if you leave any of those arrows pressed, you could perform a continous playback (like when you press play, but if you lift the pressed arrow key, the playback pauses)
I don’t know if you got the idea, but if yes, please implement it.
Anyway, thanks for your attention.

Hi @CamiloAndresGil
There was a discussion about this a couple of days ago:

As an alternative, using the mouse wheel on the timecode display could work for you.

Mouse wheel alone: Moves the playhead by increments of 1 frame
Ctrl + Mouse wheel: Moves the playhead by increments of 10 frames.

1 Like

That’s more or less convenient, if you are on a desktop pc, which has mouse and a full keyboard, but working in a laptop without mouse and with normal laptop keyboard, those keys and mouse shortcuts, add more complexity to the work. instead of making easier. Because of that, in a laptop (i use one, many times without mouse) would much more convenient for working with clips, the idea what i’m saying.

It is easy on a laptop with a touchpad; click in the timecode field (or simply move the mouse over it) and scroll up/down (often a two finger drag up/down action). You know, like how you scroll a web page? Also, most keyboards work the same on laptop as a desktop computer.

Most people press space to toggle play/pause like that. You simply press twice, second time to stop. There are other keys, screen buttons, mouse behaviors, etc. Honestly, how many different ways do you need to do the same thing?

Continuous playback when arrows are pressed” (arrow keys repeat) already work in Shotcut.
Maybe you didn’t read the discussion I linked above.
It explains why sometimes key repeat doesn’t work, and how to work around the problem.

Here’s the link again (read the entire discussion):

Another great tip, @musicalbox. Never realised it. Thanks! :grin:

1 Like

But if you need to playback backwards (because maybe you went over a bit far of your target frame, but not too far as for moving playhead with the touchpad?
Better said, ¿Is it too hard to implement this? I found this behavior on players like media player classic. On this playe, you can playback frame by frame, by holding ctrl key and pressing right arrow (forward) or left arrow (reverse). But on this mode (frame by frame) if you leave pressed any of the arrows, the playback is continous until you leave pressing it. If you wonder why i use media player classic frame by frame tool, is because the possibility of save frames as picture.
Obviously i find it very comfortable.

Your laptop is too weak for this function in Windows 11. You have three options: install Windows 7, buy a cool computer, or tinker with the settings (link above).

I would believe that the current behavior of shotcut is because of “weak resources”, if media player classic wouldn’t play frame by frame, and continuous playing by keeping the arrows pressed, but it can. To me, is a shotcut “issue” not related to my resources.
But if the devs don’t see the need to perform this modification, I can’t do anything, just thanks them for their listening.

This is fixed for the next version.