Fix incorrect implementation of TrackVirtual
#6019
Merged
Conversation
This file contains 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
…ill start after a failed seek
- When seeking to an invalid location, the track should stop. It wasn't being stopped. - When attempting to start when alrerady at the end, the track shouldn't start. It was starting.
|
The |
bdach
reviewed
Oct 5, 2023
bdach
approved these changes
Oct 5, 2023
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.
Noticed when going through osu! side test failures.
Also adds safeties and test coverage to
DecouplingFramedClockagainst a source which may still start after a failed seek. Better safe than sorry I guess.Note that the test doesn't fail even without the
TrackVirtualfix, as it's not using aTrackVirtual.