In the RC, there is a concept called BPM Scaling. it is written aside the main RC as the main RC is written assuming 180BPM, and we need an idea on how the rule applies on higher/lower BPM. However this makes the RC harder to understand as users need to calculate this through themselves, and there is no clarification on which rules are covered by BPM Scaling and which rules are not.
so my proposal is as follows:
We should write the exact time length in milliseconds next to the note length on rules where BPM Scaling applies.
for example-
on rules where BPM Scaling doesn't apply - 1/2 gap, 1/2 sliders, ...
on rules where BPM Scaling does apply - 1/2 (166ms) gap, 1/2 (166ms) sliders, ...
this change will make the BPM Scaling rule easier to understand, and make the RC easier to understand as people can see the note length both in the editor (with the timestamp) and the RC.
so my proposal is as follows:
We should write the exact time length in milliseconds next to the note length on rules where BPM Scaling applies.
for example-
on rules where BPM Scaling doesn't apply - 1/2 gap, 1/2 sliders, ...
on rules where BPM Scaling does apply - 1/2 (166ms) gap, 1/2 (166ms) sliders, ...
this change will make the BPM Scaling rule easier to understand, and make the RC easier to understand as people can see the note length both in the editor (with the timestamp) and the RC.