here, two controller buttons are mapped with the MIDI Remote Mapping Assistent to
Key Commands / Transport / Nudge Cursor Left
and
Key Commands / Transport / Nudge Cursor Right.
When I choose the Ruler Mode “Bars+Beats”
the step when using a controller button is correct like the grid type
(i.e. Bar, Beat, Use Quantize).
But when I choose the Ruler Mode “Seconds”
the step when using a controller button is always 2 seconds and NOT like the grid type
(i.e. 1 ms, 10 ms, 100 ms, 1000 ms).
I think, this is a bug. Can you reproduce this?
With the PC-Keyboard and using “Strg-Num -” and “Strg-Num +” it works correct.
Best regards
CKB (Christian)
Addendum:
Other MIDI Remote commands for which the current grid is relevant work correctly with both Ruler Modes (Bars+Beats Mode and Seconds Mode), e.g. commands for moving events/clips and commands for changing the lengths of fade-ins and fade-outs.
when the Ruler is set to “seconds” or “timecode”, the Grid is always 2 seconds here
and not (1 ms / 10 ms / 100 ms / 1000 ms).
I testet it now with a complete another controller (ESI XJam)
and assigned the functions without a script ony with MIDI Remote Assistent.
All other Commands work as expected and also this command, wenn the Ruler is set to “bars & beats”, but not when the Ruler is set to seconds or timeode.
Much more important than setting the ruler to seconds is of course setting the primary tempo to seconds at the bottom of the screen. How could I forget that…
However, it is still strange that when the PRIMARY TEMPO is set to Bars & Beats at the bottom of the screen but the Ruler is set to “seconds” or “timecode”, the Grid with MIDI Remote is always 2 seconds here and not (1 ms / 10 ms / 100 ms / 1000 ms).
(With the PC-Keyboard and using “Strg-Num -” and “Strg-Num +” it works correct.)