The basic/higher snap description takes a bit of wording to explain and is more complicated than it needs to be.
1 - Remove basic snaps
Currently, there is no situation where basic snap rules should not also be applied to higher snap. When a basic-snap is mentioned, the RC should instead say that it applies to all dashes/hdashes.
In fact, having basic snap be mentioned at all is currently working against the RC, take for example.
This should be changed to:
===
2 - Remove the ranges for higher-snapped dashes and just make them to be less than a value.
Old system:
if (x < 125 && x > 61)
New system:
if (x < 125)
There is no point in defining the lower bounds of what a higher snap dash is. Currently, it's set as the minimum gap between objects (Eg minimum 62ms gap between dashes on platter), but there's no point in defining the lower bound since it's unrankable and can't be used. It's just more numbers to deal with. Just defining the upper bound is more intuitive and easier to explain.
===
3 - Rename Higher-snapped dash to High-snap dash
This just makes it shorter, easier to say/write, and more consistent with other wordings we use.
We don't say lower circle sized map, it's a low circle size map.
===
4 - Remove Cup/Overdose from the table
they don't need to be there.
1 - Remove basic snaps
Currently, there is no situation where basic snap rules should not also be applied to higher snap. When a basic-snap is mentioned, the RC should instead say that it applies to all dashes/hdashes.
In fact, having basic snap be mentioned at all is currently working against the RC, take for example.
Salad Guideline:Basic dashes shouldn't use different consecutive beatsnaps, but technically there's nothing that discourages this from being used on higher-snap dashes.
Dashes that are basic-snapped should not be used consecutively when different beat snaps are used. For example, a 1/1 dash followed by a 1/2 dash.
This should be changed to:
Dashes should not be used consecutively when etc...I would suggest taking a quick look at the other rules/guidelines and picturing applying basic-snap rules to higher-snap, it already makes sense.
===
2 - Remove the ranges for higher-snapped dashes and just make them to be less than a value.
Old system:
if (x < 125 && x > 61)
New system:
if (x < 125)
There is no point in defining the lower bounds of what a higher snap dash is. Currently, it's set as the minimum gap between objects (Eg minimum 62ms gap between dashes on platter), but there's no point in defining the lower bound since it's unrankable and can't be used. It's just more numbers to deal with. Just defining the upper bound is more intuitive and easier to explain.
===
3 - Rename Higher-snapped dash to High-snap dash
This just makes it shorter, easier to say/write, and more consistent with other wordings we use.
We don't say lower circle sized map, it's a low circle size map.
===
4 - Remove Cup/Overdose from the table
they don't need to be there.