Osu: Add support for unusual beat snaps like 1/5

[Xinnoh]

There are rare cases where 1/5 or 1/7 beatsnap is used in a song. This is uncommon, but some songs are simply unrankable due to this.
https://osu.ppy.sh/s/647360 - Example of a 1/5 map that could easily be ranked if 1/5 was supported

The current workaround to 1/5 is to multiply the bpm by five, use 1/1 snapping, and have a 5/4 meter. It's dumb.

Because 1/5 and other weird snaps are so uncommon, they should only be accessible via an extra panel or by editing the .osu file, else new mappers would be confused by them. Regardless, it needs support somehow

[Frontear]

Considering how this is already possible, as you said, isn't that somewhat support already? Unintentional support sure, but support nonetheless. Also, since you mention rare, I seriously doubt it is necessary to officially begin support for something that is not only rare, but already somewhat possible, especially considering that there are more important issues to worry about currently. Perhaps backlog, if it must be supported?

[Xinnoh]

1. It's not supported or possible. If you open it in the editor you'd see 500 bpm is really not fun to work with at all. Changing the bpm to the correct bpm and 80% of the map becomes unsnapped because the editor does not support it.
2. I am mentioning it now because if it's brought up again after lazer is finished it may be harder to implement then. It's easier to implement features while still developing. Regardless, it should be kept in mind.
3. this is a rhythm game, barring some kinds of music from ever being ranked due to technical issues just doesn't make sense.

This is 100% a backlog feature, but it needs to be implemented in the future.

[dscosu]

not much to add to what sinnoh said, very well worded and concise but just to elaborate with examples as i do think its important to have

the current implementation for something like this is really broken especially when most of a song is in a regular divisor like 1/4. if you have 1/5 in just one place, you have to artificially raise the bpm by 5/4 or by 5 and then map that one part in 1/5 and then go back to 1/4, even though musically the bpm never changes. for an example: https://osu.ppy.sh/s/693816 at 06:42:715 the bpm is raised by 5/4x to map a small section of quintuplets, even though musically the bpm isnt changing. this is a rather light example but i'm sure you can imagine how things would get more complicated. it's an unnecessary roadblock and results in the song really being timed incorrectly.

as far as implementation, an option to select a "custom beat snap divisor" in the top right, where the beat-snap divisor currently is, so that the regular 1/1, 1/2, 1/4 etc.. aren't affected but custom values are possible. then maybe move/reword the "1/16 should never be used EVER!!!" message to custom divisors.

[AlFasGD]

Given this I would like to express my proposal for even further divisions. What I had in mind is three separate panels like the one that already exists where in order the divisors they contain are:

• Common Panel: 1/1, 1/2, 1/4, 1/8, 1/16, 1/32 (there are some cases where this might be needed)
• Triplets Panel: 1/3, 1/6, 1/9, 1/12, 1/18, 1/24 (1/9, 1/18, 1/24 are quite unusually encountered, but I don't see why not supporting these as well)
• Other Panel: 1/5, 1/7, 1/11 (honestly I doubt there is any point going further in this case)

Now I see this being useful for osu!mania since it involves more complex patterns and faster speeds, and not that much in other gamemodes. However these are to be universally available since they might be needed for any case (please don't do 1/32 in osu!standard though).

[Frontear]

This new comment puts me more on edge. It improves the mapping scene, but further complicates what the editor is going to become.

How many cases would other panel even help with? I can understand the common panel, or even (with some hesitation), the triplets panel. I don't see how useful the other panel can be, or how much music it even assists in.

Additionally, I feel just adding divisors is just going to be a hassle, there should be a better way to mapping these kinds of songs without just adding new divisors. It will start getting cluttered, and become extremely tedious for mappers.

[AlFasGD]

The implementation I have in mind and will hopefully do a pull request implementing it does not complicate it, in fact it gives the mapper the option to switch between the types of panels (common, triplets, other) with other buttons, which will only show the divisors on each panel.

In my opinion, 1/11 is the rarest to use, yet I don't see why not adding it. It would be useful somehow somewhen, and having it implemented beforehand surely assists.

[LittleEndu]

What is preventing us from making lazer beatmaps and thus the editor support any arbitrary beat snapping? Then all the rare beat snaps like 1/5, 1/7, 1/9, 1/11, 1/18, 1/24, 1/32 would all be supported but only when necessary.

[Xinnoh]

this was added to stable so i would assume it's fine to close this?

[bdach]

No, this is the issue tracker for lazer specifically. The issue should remain open until the snaps are added to lazer, too.