Table Quantization Ease of use

[vidret]

Currently we scroll through all of the available chords to get to the next note (first all the chords for B, then we get to C).

Maybe they should be separate parameters to minimize scrolling.

Instead we could scroll note separately and chords separately, getting to the chord and note we want faster.

[XORadmin]

Currently we scroll through all of the available chords to get to the next note (first all the chords for B, then we get to C).

Maybe they should be separate parameters to minimize scrolling.

Instead we could scroll note separately and chords separately, getting to the chord and note we want faster.

I could do shift up/down for the notes and left/right for the chords (which could eventually change notes then as well like right now or not)

[vidret]

That sounds excellent. I might prefer for the changing chords to not change notes, maybe someone else could chime in on preference.

That'd mean scrolling too far to go back around would mean you'd have to switch back your note. No biggie, but still.

[marek]

+ 1 to this.

And It would be really nice for the workflow to be able set the table speed in clock divisions instead of hexadecimal values.