-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Seek controls in line with most media players #1611
Comments
Delerium
changed the title
Seek controls in line with most media players
Feature Request: Seek controls in line with most media players
Jun 9, 2023
gotcha. I think it could be solved by allowing an additional set of keys that can be bound to additional customisable intervals (currently there's just one - default 1 sec, customisable). i'm closing this to keep issue count down but im referring to your issue here: #604 (comment) |
next version will have 3 total customisable seek speeds |
mifi
added a commit
that referenced
this issue
May 14, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a lot of issues to go through, so in order to make it easier for me to help you, I ask that you please try these things first
Description
Is there any chance we can get media controls that are closer in line with media players such as SMPlayer, media player classic, etc?
Example from SMPlayer:
Customizable fixed seek times:
With keyboard shortcuts configurable for each one:
Explanation why:
The way it works now in LosslessCut, you have two keyboard options to seek, normal and by 1% of timeline. Normal is fine for the left and right arrows to do small movements, but when you are working with videos that could range from 5 minutes to 6 hours, 1% is such a HUGE change that it has become useless to me. That means my only source of control is the small seek, which doesn't help much to traverse a 6 hour video.
That leaves seek acceleration, which is way too hard to control due to not having a "top speed" so without watching the timeline, you have no clue how fast you are going, and end up skipping most of the video because your eyes are glued to the actual video not the timeline.
The basics of it is that when I am seeking through a video to cut up, I would use each seek distance for different purposes... 1 minute to traverse a large video quickly and consistently regardless of total video length. 5 second to traverse points between the 1 minute marks to find the general area I want to cut, and 1 second to get in the exact position I want to cut.
(edited title to reflect that this is a feature request not a bug. lol)
The text was updated successfully, but these errors were encountered: