Adjust editor seeking to be fairer when track is playing#36043
Merged
bdach merged 1 commit intoppy:masterfrom Dec 17, 2025
Merged
Adjust editor seeking to be fairer when track is playing#36043bdach merged 1 commit intoppy:masterfrom
bdach merged 1 commit intoppy:masterfrom
Conversation
The previous multiplier was supposed to account for seeking backwards being "slower" because the track is playing forwards, but it really didn't work amazingly. Rather than trying to pull off some magic, let's just ensure that seeks in both directions feel correct, even if that means that time gradually moves forwards. Closes ppy#35998 (mostly). Of note, this still doesn't match stable completely. I attempted to implement the full stable seeking algorithm but it's objectively worse in other scenarios, so I'd rather just tweak what we have until the majority of users are happy.
This was referenced Jan 1, 2026
This was referenced Jan 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The previous multiplier was supposed to account for seeking backwards being "slower" because the track is playing forwards, but it really didn't work amazingly.
Rather than trying to pull off some magic, let's just ensure that seeks in both directions feel correct, even if that means that time gradually moves forwards.
Closes #35998 (hopefully). Now when rapidly scrolling over a known range of mouse wheel like the user was, things gradually move forwards, but the drift is far lower than what they were seeing.
Of note, this still doesn't match stable completely. I fully implemented the full stable seeking algorithm but concluded it's objectively worse in other scenarios, so I'd rather just tweak what we have until the majority of users are happy.
Here's more-than-twenty-minutes-spent-making-things-work-like-stable. Was not worth it.