Adjust swing grid (mousewheel) - action too coarse

[Luster]

Hello there,

I just discovered the possibility to change the grid via mouse wheel (thanks to me2beats and mpl for the script!).

There is also a native action called Grid: Adjust swing grid.

Unfortunately changing this percent value (-100 to +100) via mousewheel is way to coarse to be useful. It's quantized in steps of 12.

I already tried changing the Windows mousewheel setting (how many lines will be scrolled with one turn) but this didn't have any effect.

My questions are:
Is this value system dependent?
What quantization are you experiencing using the action with mousewheel?
Maybe this nitpick can be optimized by the devs?

Best regards
Luster

[MusoBob]

Originally Posted by Luster

Hello there,

I just discovered the possibility to change the grid via mouse wheel (thanks to me2beats and mpl for the script!)....

What is the name of the script ? maybe you can change a setting in it.

[Luster]

These two scripts do the same - changing the measures grid.
They are fine. I just mentioned them.

The problem is the native action Grid: Adjust swing grid.

Obviously you cannot look under the hood there.
If it's about a script I would have posted in the scripts forum.

[Luster]

Bump because I really want to know if the coarse quantization with the native action is the same for everyone. In case yes, is this a bug? A nitpick? How to report so it gets a chance of improvement?

[nofish]

Doing a custom action, combining 'Adjust swing grid (mousewheel)' and putting 'Modify MIDI CC/mousewheel: 0.5x' or 'Modify MIDI CC/mousewheel: -10%' (maybe several times) before it may improve things.
(At least I'd assume that's the purpose of these actions..)

[Luster]

Originally Posted by nofish

Doing a custom action, combining 'Adjust swing grid (mousewheel)' and putting 'Modify MIDI CC/mousewheel: 0.5x' or 'Modify MIDI CC/mousewheel: -10%' (maybe several times) before it may improve things.
(At least I'd assume that's the purpose of these actions..)

Thanks for the tip! That have fixed it for me. It's not totally ideal because due to rounding errors you will never get back 0 % but hey - we can't have it all!

Love the forum, thanks for this solution!

[mccrabney]

subscribed

this is definitely the kind of thing we should be able to control predictably from controller

preserving the hardware only approach to midi editing/recording is something that modern DAWS completely missed out on in the move from the hardware sequences of the 90s/early 00s

I miss it