Midi Receiving for mapped parameters

Did you try the "universal midirx profil" from profile cloud? How does that one fare in terms of functionality in this case?

I hadn't tried it. Will do so now.

I have found that profile, but am totally lost as to what I'm meant to do with it. What is a snippet? How do I use it? How do I save my current profile so that I can go back to it after experimenting? What does "Load this code on System Setup" mean?
Can you point me to some layman's guides that I can work through to get better acquainted with how this all works. The bits I have read seem to assume a base level of knowledge which is beyond my current knowledge. I'm happy to get up to speed, just need to know where to look.

I have the exact same problem. I don´t know how to "Load this code on System Setup".

Hey @user and @user! Another code novice here trying to get these things working exactly how I want. The directions Kristof gave mean selecting the System button, clicking the Setup tab, and dragging the Snippet over. You have to delete the existing code block, otherwise it will bark at you for having too many lines of code.

BUT! I ... haven't been able to get that Universal RX snippet to work at all. I've had better luck with the MIDI RX profiles for my BU16 and EN16 devices.

However, it doesn't look like one of those exists for VSN1 yet?

Thanks for the answer. I have a BU16 and three PBF4. The BU16 MIDI RX profile works fine but it´s based on midi note messages and not CCs. I couldn´t get my head around how to apply this to CCs and to the PDF4. And I can´t drag&drop the snipped "Universal MIDIRX" to the setup tab. When I drag and drop it, nothing happens.

Yeah, you have to drag it at the very edge until a green + button appears. Unfortunately the macOS screenshot tool removes the mouse cursor so I couldn’t capture that exactly 😭

That's right, I forgot the profile does notes by default. On the System Setup event you have to change the IF statement to look for message == 176, and you need to change the individual buttons MIDI Command to Control Change.

I just uploaded a cloud profile called "MIDI RX CC BU16" that has these changes already applied! Read the profile description though, because I also changed how the MIDI channel and LED colors are defined.

I just checked it out and it works great. Thank you so much!

In the profile browser you can expand the profile and actually load specific components onto any compatible module. So in theory you could load this BU16 System and Button configs onto the PBF4?

I actually have a PBF4 but it's not with me at the moment 😅

I copied the BU16 system setup code to the PBF4s and dragged the button of your "MIDI RX CC BU16" to the buttons of the PBF4 but it didn´t work yet. But so far, that was a huge step.

I'm sure there's something about PBF4 I don't understand 🤣 I don't know much about code etc. but I work at a library so I'm pretty good at finding things out ✨

I'm glad I could help you get your BU16 up and running though!

Hey mate - thanks for that. Easy when you know how. I was trying all sorts of drag and drop but didn't work.
BUT - the good news is the universal receive did seem to work for me ALMOST 100%.
So now I get feedback to the Intech device LED, and the actual value setting for the Encoder resets to whatever I change it to in the DAW...BUT, the DISPLAYED value for the encoder remains at the last set position.

Eg, Map encoder to Send A of track 1
Change Send to 127 with VSN1 Encoder
Send changes in Ableton Live, and value and LED change on VSN1
Double click on Send A in Ableton live, and it resets to 0
LED is reset to 0, VALUE STAYS AT 127
BUT, when I turn the encoder slightly, it does not jump back to 127 but moves from 0, so the internal value is at 0.

So getting there, just one more step to do with chhanging the displayed value on VSN1.

Anyone got any ideas how I get the Midi Value to display on the VSN1 for a mapped parameter. The LED is updating correctly, the value for the control is updating, BUT the displayed value remains at the last set value when I reset the parameter internally in the DAW. So, the missing piece is:

• Update displayed value on VSN1 screen when mapped parameter value changes (from DAW as opposed to via actual control - that piece is working)