-
Notifications
You must be signed in to change notification settings - Fork 1
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
Speed doesn't return to original value #2
Comments
I don't know what to do about this, using the defined cap may not suffice and make using the script annoying. Your manually set mpv speed is 2, and your evafast speed 1.5 (original value higher than cap). Do you expect the speed to slowly go down to 1.5 until you release the right arrow key, and go back to 2? Should it always use the higher value between original and evafast, making it have no visible effect in this cases? Should evafast instead always add "target speed - 1" to your current speed, such that it ramps up to 2.5? Should it multiply your original speed by the target, which in this example gives us 3? I want to hear from others what the most desirable behavior would be. |
Yes.
But expected one. And you don't know it's useless. Maybe I want to use it as a slow down key :) The worst thing to do in cases like this is try to be smart and predict how people want to use your app. Just make it go to values I configured. None will complain or be surprised by that. |
Same here. I would expect speed value to revert to the previous value I manually set (0.5, 1.5, 2.6, whatever) rather than 1 when releasing the right arrow key, it feels more logical to me. I'm using |
Finally got started on this in #5, I need to rework some things to achieve that effect. |
If my sped is at 1.2, and I use this, it always returns to 1.
The text was updated successfully, but these errors were encountered: