This repository has been archived by the owner on Jan 31, 2019. It is now read-only.
Beatmap "cutting" #6
Open
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
|
Can you add a test case for this? |
|
This/next week I'll try to prepare some manually cut beatmaps to be able to compare results with automatic cuts. Sorry for not responding earlier. |
Doesn't actually affect pp result at all Also this was causing ocasional OutOfRangeException in GetMaxCombo on timingpoints list indexing
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Adds new beatmap method "Cut" that allows for selecting(in ms) what part of beatmap should be exposed to rest of library effectively allowing for calculating pp values only for that selected part.