I understand how to use the demuxer to get the individual midi values as separate messages but felt it to be very tedious with such a large range of values. But unfortunately the volume fader wants to see an OSC message with an integer value from 1-127 and not the decimal 0.0 to 1.0. I notice that the OSC is being sent successfully and the volume fader changes its value. For example, if someone asks if your sequence data is demuxed, they’re probably wondering whether the sequences from your samples are all group together (i.e., they are multiplexed), or if they have already been associated with the samples they are derived from (i.e., they are demultiplexed). I'm sending the following OSC message: "/glitch-sequencer/vol (1,)". Demux is a common abbreviation for demultiplex. I'm sending Midi CC1 from the controller as a variable value (1-127), I would like this midi controller to modulate a volume fader in the application. I've finally got the OSC syntax problems down and am now left with this problem. At the moment I'm using the Native Instruments Maschine midi controller (knobs, buttons, and an 4*4 Pad array) to control an application called Glitch-Sequencer. ![]() I've finally had some time to sit down and think about how I was hoping to integrate osculator. Thank you for your quick response, please excuse the tardiness of my own. I will fix that so you just have to select the /midi/cc line and do "demux". Now, select the argument at first index (the line that is named "0"), and do Edit->Demultiplex. I would recommend you demux on a stable key, like the track number rather than something that can change. In order to force the demultiplex, you need to duplicate (Edit->Duplicate) the /midi/cc93/1 message, and then delete the second duplicate (the line named "0->0"). Received messages in OSCulator cannot be modified. PS: I can see there is a small bug in the current version (2.8.4) that forbids demultiplex of messages in this specific case. ![]() If you can give a further description of what you would like to do exactly, I can maybe think about a better solution in the meantime. OSCulator is the missing link between your controllers and your music or video software. If you really need to do that, it will make the trick. This will "demultiplex" the input, meaning the message values will be represented as discrete events.Īs I said, it is not pretty since it produces a lot of rows, and the values are ranging from 0 to 1 will all the numbers in between. The message will now be filled with every values it can take on input (max 128 values). Select the line corresponding to the MIDI CC input (/midi/cc93/1), and then go in the Edit menu, and choose Demux. If you want to know when a particular value has been triggered, there is a way to do that, but it's not pretty: The problem is: would you consider the data coming from a MIDI CC is rather a continuous value changing in the 0-127 range, or is it rather a single event at a particular value? To keep things general, MIDI CC are represented on input the same way there are on output (MIDI CC event).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |