TempoSync value order tweak.

[CyberGen]

Hello fellas,

This is mostly a music theory argument, so bear with me.

For a long time, I’ve noticed that the tempoSync subdivisions in HISE are not arranged in true linear order. At first glance, it might seem logical — for example, "1/8D", "1/8", "1/8T" appear to follow a descending rhythm duration: dotted is longer than standard, which is longer than triplet. That’s fine within that group.

But the problem arises when you move between groups. For instance:

"1/16D" (dotted 16th) is actually longer than "1/8T" (triplet 8th),
Yet "1/8T" appears before "1/16D" in the current list.

This breaks the musical continuity of gradually increasing rhythmic speed. It results in awkward, non-linear jumps when changing values, especially noticeable when modulating tempo-synced effects.

Suggestion:
Reorder the values based on actual timing, not just visual grouping.
For example:

  "1",
  "1/2D", "1/2", "1/4D", "1/2T", "1/4", "1/8D", "1/4T", "1/8",
  "1/16D", "1/8T", "1/16", "1/32D", "1/16T", "1/32", "1/64D", "1/32T", "1/64", "1/64T"

Now, yes — this can be worked around in scripting by rearranging arrays manually, but I figured I’d point it out in case others feel the same. It might be a worthwhile change at the source-code level to ensure smoother musical transitions and better UX and make our coding lives a bit easier.

Thoughts?

[Chazrox]

@CyberGen I noticed that too and I literally just did that for my eq module. Re-ordered it how I wanted it and had to do a little bit of scripting for a combobox. Not to hard, just saying I noticed that as well.

[ustk]

@CyberGen you're absolutely right, but this would break backward compatibility. So making your own array seems to be the solution for now.
In the waiting for a HISE_USE_NATURAL_TEMPO_ORDER preprocessor