I use a beatstep to control parameters of a midihub patch as suggested by the community. Let’s assume for now that I want to control the level of a chance pipe with the first beatstep endless encoder. I have created the mapping between this continuous parameter and the encoder.
The issue I am facing is the following: the value of the chance parameter is 10% when I first load the patch, as I want this to be my starting point. As soon as I move the encoder the parameter value jumps to 50% which is the default value of the endless encoder. I want to avoid this jump and have continuous control over the parameter from its starting value.
Unfortunately, it seems that on beatstep it is not possible to store encoder values to a preset in a way that these values persist across power cycles (although they can persist within the same power cycle – If I am wrong here, please correct me).
I have also tried to change the endless encoder to relative from the Arturia MIDI Control Center but this doesn’t work either. In this case I am getting even weirder outcomes where the parameter shifts between two values (these are not the extreme values, i.e. 0 - 127).
I am pretty sure there should be a way to achieve what I want and it may be obvious. Any help would be greatly appreciated.
Is the Beatstep Pro able to receive a MIDI CC message from Midihub to update its own stored CC value?
In that case, it might be possible to make Midihub send the initial value to set the endless encoder to the correct initial value, then it should avoid jumps.
I don’t own a Beatstep Pro myself.
@Giedrius I am not sure if that’s an option. Does Midihub support control of its parameters with relative CC?
At this time, Midihub does not support relative CC updates. It’s also a bit not standard, there can be many ways how relative signaling could be implemented.
Could you try and see if the Beatstep Pro reacts to incoming CCs on the same channel and number that are assigned to an encoder? If it updates its own value, it might work.
I’ve checked the manuals for MIDI Control Center & Beatstep Pro, but they don’t seem to document this area much, they don’t even describe how their relative modes work like.
@Giedrius your help is really appreciated!
Quick question – sorry if it is too obvious --, how can I send a fixed CC value from Midihub to a specified MIDI channel and CC number?
@Giedrius, @agamemnonc
Beatstep Pro MIDI-IN has no effect on the knobs output.
(I think MIDI-IN is more intended for when you want a MIDI → CV interface, but I’ve not used this yet so I’m not sure)
The relative modes are useless in this context too, probably more useful in a DAW context.
They differ only in what the initial value is (64, 0/127, 16 respectively) presumably to suit various DAW types.
if you want your fixed value to come from an message input, then use Transform
like this
(this example takes any Note On and replaces it by Ch12 CC114 value 59.
By restricting the Note Range, people sometimes use this technique to adapt part of a keyboard to send different fixed CCs from different keys)
Otherwise you could use a LFO to continually send out CC values with Ch Remap and Rescale to get the correct channel/value (or use Transform similar to above).
1 Like
What do you mean by ‘no effect on the knobs’?
As far as I know the BSP also responds to incoming messages. For instance when functioning as a Mackie HUI compatible controller and keeping state when switching channel groups in Ableton Live. Or displaying button on/off statuses when toggling.
Or is this implemented in another way? Though you have to enable MIDI out in Live for this to work.
1 Like
Hey, @MaikR-010, good to see you again!
What I meant was merely in the context I thought @Giedrius was asking about:
-
so say knob 9 is sending Ch1 CC114 and current value is 23
-
then when I get a Midihub LFO to send Ch1 CC114 value = 59 to BSP…
-
…we might hope the next knob 9 change would give 58 or 60
-
but this is not the case
That’s all I meant.
If you can get BSP to do this then I’m most happy to be wrong 
– it’s not a device I’ve owned for long and that’d be a nice thing to learn…
1 Like
Thanks everyone for your willingness to help.
Just a note – probably to make things even worse – it is a regular Beatstep that I own and not the Beatstep Pro.
1 Like