Skip to content
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

fix: remove broken DTX legacy beatline chips processing (0x51) #758

Merged

Conversation

IepIweidieng
Copy link
Contributor

Why

The insertion of beatlines failed to consider non-x/4 time signature, mid-measure #BPMCHANGE, and mid-measure #DELAY.

Beatline is unused in Taiko gameplay,
and the wrong insertion of beatline can cause
extremely long song duration, wrong retry position (when the calculated time overflows, the BPM is negative, or when the lower number of time signature is negative), and bad performance for charts containing high BPM and long time signature.

Test Cases

Miracle 5ympho X (kirura969), chart download link is in channel description.

Intended behavior: https://youtu.be/rwArv-JyAW4

❌ Before behavior: Wrong chart length, wrong retry position.

OpenTaiko.0.6.0.23.2024-12-04.Miracle.5ympho.X.kirura969.wrong.retry.position.mp4

⭕ After behavior

OpenTaiko.PR.2024-12-04.Miracle.5ympho.X.kirura969.correct.retry.position.mp4

Benchmarks

愛歌「ネグラドルナ」(kirura969), chart download link is in channel description.

Intended behavior: https://youtu.be/2xtRk239msI (except for note count capping)

The ending part is different because the stopping effects of #DELAY has not been implemented in OpenTaiko.

❌ Before behavior: mostly 3x fps, halt at end

OpenTaiko.0.6.0.23.2024-12-04.kirura969.-.0.01.05-0.02.22.mp4

❌ After behavior: mostly 5x fps, halt at end
#757 is applied here.

OpenTaiko.PR.2024-12-04.kirura969.-.0.01.05-0.02.30.mp4

The insertion of beatlines failed to consider
non-x/4 time signature, mid-measure #BPMCHANGE, and mid-measure #DELAY.

Beatline is unused in Taiko gameplay,
and the wrong insertion of beatline can cause
extremely long song duration, wrong retry position
(when the calculated time overflows, the BPM is negative,
or when the lower number of time signature is negative),
and bad performance for charts containing high BPM and long time signature.
@0auBSQ 0auBSQ merged commit 043ad6a into 0auBSQ:main Dec 4, 2024
@IepIweidieng IepIweidieng deleted the fix-remove-broken-DTX-legacy-0x51-beatline branch December 5, 2024 12:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants