I made a MIDI to OSC controller that translates any general USB midi device to OSC on the network on a Pi4. I'm using for example a LIVID DS1 which has buttons sending Midi notes, and faders sending CC commands.
Buttons: /midi/note and the two float values, Faders: /midi/cc and the two midi values for fader number and fader value like the midi protocol
When I'm learning OSC (or manually) configuring the Aximmetry, the commands arrive and the fader works, but Aximmetry does not distinguish the different MIDI Notes or CC commands as it not detects or uses the number float after the OSC string.
As result, any button or any fader controls the same assigned variable. Aximmetry (I'm using version 2021.4.2. build 20596) is not using all values of the OSC command to distinguish.
Hi Marc,
I am not exactly sure about the problem.
Are the "/midi/note" and "/midi/cc" the address of the OSC commands, and do you send them together?
If so, you could just send them separately while assigning the OSC in Aximmetry. And then you can send them together. Otherwise, only one of them will be registered, and it does not matter if you are assigning a button or a scalar in Aximmetry.
If "/midi/note" and "/midi/cc" are in the arguments of the OSC, you can use the OSC Method module to separate them.
Also, for the OSC Button to work, you have to send a 1 value: https://aximmetry.com/learn/tutorials/control-methods/using-the-osc-protocol/#controlling-module-properties-and-control-board-buttons
Warmest regards,