Advice/nudge in the right direction pleeeease

I want to use the same 8 knobs to control 8 groups of 8 knobs depending on which track of the radios is active. I tried a couple different routes but the one I was exploring last, I was using a variable in send and receive symbol. Any help is appreciated...learn-2-midi.pd

Patch attached

Ō

Here is a quick patch to show how to do it for 4 sliders, just add more numbers to the route and set the number of cells in the radio to get 8. If your controller can be set to send relative CCs I have a couple abstractions that will make things easier and allows you to avoid the value jumps associated with absolute value encoders, it also highlights the parameter being edited, I can throw together a help file for it and upload it if wanted.

cc.pd

@Organism This should work: learn-2-midi.pd.

Now, usually you would want the control display to change to the setting of the selected track. This is a bit more complicated and i would recommend to completely separate GUI and logic if you want to go in this direction...

@oid @ingox yes, jumpy encoders... lots to consider still, thanks for the help, please feel free to send the abstractions if you have a chance, in the meantime I will keep reading and trying things out, and working from home

@Organism I would make one central array with 64 values, one for each of the sliders on the bottom. Each slider would write to its value into the array. When the track is changed, the values of the track are read from the array and the control sliders are set via set message. This way you have a centralized store of all settings and the program logic can also access the data from there. Depending on your goals you would not even need the sliders at the bottom any more

@ingox Ahhh that makes sense... really appreciate the boost!

Jonathan

@oid @ingox etc...
I'm back... Using PD help files and your advice I got it to the next stage, using array. If you have a minute, to let me know what you think... (can it be better optimized etc) I used 8 arrays vs the extra math of a single 64 key array.

control-2.pd

Next step is to recall fader positions

Thanks!

@Organism Arrays can be good, but if you are using relative CCs to avoid parameter jumps when switching, they make less sense since the array is just filled with 64 or 16 or 127 depending on how the particular controller handles relative CCs. It is a good thing to know how to do, not all midi controllers can send relative CCs and the techniques learned can be applied elsewhere including when dealing with relative CCs when you want to have patch memory. This weekend I will have time to polish up my abstraction and upload it,

@oid sweet! I checked my controller it supports relative encoders
prolly doesnt matter so much right now, but I'm using beatstep pro with a bela/beaglebone black (learning and building on Macbook pro) thanks again.

@Organism Just a quick demo to show what i was talking about: learn-2-midi.pd . When you switch the track, the display updates. The sliders on the bottom and the machinery on the right side are not necessarily necessary any more.

@Organism, what controller are you using that supports relative encoders? My control surface has rotary encoders but the MIDI it generates is absolute.

@Organism Here are the abstractions, it will ignore the first tick from the controller and just highlight the control to be edited and keep the CC value and the slider/numberbox2 up to date with each other so you can edit on the screen or with the controller and avoid all parameter jumps. The help file shows how to use the note data sent by the BeatSteps pads to switch what controls the encoder edits, but that can be switced to a radio or another CC like the tempo knob on the beatstep. As is this is setup to work with relative CCs centered on 64, but it would be simple to change it to work on other values,

cc.zip

@jameslo To my knowledge all of the Arturia controllers and sequencers can be set to send relative CC data, the one caveat is that if you do not have access to a Windows or Mac computer to run their software it can be difficult to change the controllers settings, Arturia has not been good about releasing the sysex for their gear and not all of their devices have had people figure out the sysex and post it on the web. Thankfully it is not hard to figure out the sysex, if you have access to a Windows or Mac machine at least. The regular BeatStep is the only device that I know of which has had someone do the work and publish the full sysex of on the web, I think one of the Keysteps has a good portion of its sysex posted, the rest just have bits and pieces scattered about.

@oid doooope! I'll check it out, thanks a lot!