I would like to be able to change the number of note blocks in one beat

[stabery]

Currently noteblockstudio has 4 blocks per beat, but this is not suitable for representing songs that contain triplets or sextuplets.
(Rhythm game songs frequently include sextuplet intervals.)

If you want to include triplets, the number of blocks required per beat is 6, and the BPM setting must be increased by 1.5 times.

If you want to include sextuplets, the number of blocks required per beat is 12, and the BPM setting must be tripled.

What happens in the editor when this happens is that the number of bold lines within a beat becomes three, even though the song is in 4/4 time, making it difficult to work with.
( |□□□|□□□|□□□|□□□| This corresponds to one beat. But in the editor it is displayed as |□□□□|□□□□|□□□□| )
I would be very grateful if you would consider this.

↓ If 180BPM song

(You may ignore the following text.)
Also, although it is localized
There are several songs in this world that contain sextuplets and have a BPM of 300 or more. In this case, if you try to triple the BPM, it will exceed the software's maximum BPM of 900 and it will be impossible to reproduce the BPM.
(For example, there is a rather famous rhythm game song called “DESTRUCTION 3,2,1” with a BPM of “321.321”)

※using translate

[Bentroen]

Thank you for your suggestion!

The current way tempo and intervals are handled is very simple to conceptualize, but we're aware it can be quite limiting when it comes to mixing different intervals. We have plans to entirely rework how tempo is handled across the application to make the grid layout less restricting, while at the same time avoiding the need to get to 400+ BPM in order to unlock more precision -- which is far from ideal and not how things usually go in professional music-making applications. This will allow you to work in a layer 'above' what vanilla note blocks allow you to do, yet still be able to easily convert any song to fit within the game's limitations.

This, however, will only be worked on after we work on rewriting the codebase in a proper UI engine, which is currently underway. I'll add it to the v4.0 milestone to indicate this!