This is perfect for incremental controls:
What I do is have 2 specific controls mapped to 2 buttons to tell the macro knob to move one step left, and another right. This is done using
Clyphx X-controls, that way I don't have to use clips to give the instructions, but a text file.
After you install clyphx, you can practice this instruction using clips in your set, but let's assume you'll go the x-controls route.
In your clyphx remote script folder you'll find a text file "user settings". At the bottom is where you'll give the instructions to tell the macro knob to move one step left and another step right.
You can use either a cc message or a note message. You might want to use a note if the cc gives out continuous pressure data like the Quneo does, this way it's just on/off; it's more stable.
So, let's say it's the 1st macro knob on the 3rd device on the 2nd track. The instruction would be
note, 9, 10, 2/dev3 1<
note, 9, 11, 2/dev3 1>
before that you give each control a name like "macro_left" and macro_rite so it'd be
macro_left = note, 9, 10, 2/dev3 p1<
macro_rite = note, 9, 11, 2/dev3 p1>
The names can be whatever you want.
So it's 'name' = 'note or cc', 'midi channel', 'midi note or cc number', 'track'/'dev#'/'macro#'
You can also use the name of the track channel in quotation marks so if track 2 is called SPLERF it would be
macro_left = note, 9, 10, "splerf"/dev3 p1<
It's all in the manual.
X-controls are a great way to make custom mappings to your set especially if you have things set more long term, like a template.
You could make custom mappings to control all your devices the way you wanted to if you want. And it also doesn't clutter up the midi map area.