question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Taiko Major Barlines are too arbitrary

See original GitHub issue

Currently, the BarLineGenerator uses Major = currentBeat % (int)currentTimingPoint.TimeSignature == 0 to determine whether or not a barline is major (has triangles above and below), with currentBeat incrementing each measure and starting at 0 whenever a new timing point is reached.

This is problematic for a few reasons:

  1. Major barlines may not necessarily line up with the time signature. A song in 4/4 may not have major beats every 4 measures, nor does this necessarily apply to any other time signature.

  2. Timing points do not necessarily occur on major beats. In these cases, even if the song’s major beats theoretically line up, every single major bar line would be incorrect. In the case of songs with variable bpm, this also results in far more major barlines than necessary.

I don’t think there is a simple solution that guarantees these major barlines won’t be incorrect, when taking into account songs with awkward pauses, or simply no clear pattern at all. The only method that guarantees no errors would be making it something mappers do, but this wouldn’t solve the problem for older maps, in addition to requiring some sort of additional information attached to (effect? timing?) points, as well as a relatively significant amount of extra effort (in the cases of more complex songs, perhaps requiring every major barline to be marked individually?) on the part of mappers for very little benefit in terms of map quality.

Perhaps these major barlines could be something mappers can choose to add for emphasis, but I don’t think auto-generating them is the right answer, which often places emphasis on random barlines that may have nothing on them at all.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:6 (5 by maintainers)

github_iconTop GitHub Comments

2reactions
peppycommented, Aug 20, 2020

4:4 songs will have bars ever 4 beats. That’s how music works. They should be correct for correctly made beatmaps. Not sure this requires action?

0reactions
Alchyrcommented, Aug 20, 2020

That makes sense to me

Read more comments on GitHub >

github_iconTop Results From Across the Web

Untitled
Upbeat songs clean lyrics to thrift, Thomas vaccari et luc arbogast mp3 free, Jagged edge walked outta heaven too hot remix songs, Lock-in...
Read more >
ODD_TIME_VGM OF THE DAY on Tumblr - #uncommon meter
That results in some vaguely ambiguous barline division if you were to break it down further than 37 like I did, so there...
Read more >
K2 - What's Your Deep Wish · forum | osu!
3/10 - thanks to some awesome in game feedback from awesome people like Sync and MMzz, taiko diff lost 72 notes, but gained...
Read more >
Using the ManuScript Language
ManuScript is a simple, music-based programming language developed to write plug-ins for the Sibelius music processor. The name was invented by Ben Sloman, ......
Read more >
How would you like your Guitar Pro, sir? - [ult.edu.vn]
Ability to decide in which bars the pedals are on or off, just like you would do in a live ... Very important...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found