Hi,
First thanks for OSCulator, having a lot of fun with it.
I have this application that I wrote that emits OSC message that look like this:
(taken from the console, simple logging)
"/klid/pattern_1323672071743: 60 | 127 | 1"
The message will always have this pattern:
"/klid/pattern_" + [uniqueID] + pitch + velocity + note_on/note_off
The application is web based with clients connecting to a website where they can send oscmessage to local server. The messages are used to send midi notes locally, with OSCulator acting as an osc-to-midi bridge.
My problem is that the uniqueID will always be different and the number of clients will always be changing. So manually assign messages to events is out of the question.
However, each will message will always have the same pattern and the same 3 parameters will always be sent. Any clue how I could configure OSCulator to send midi from those oscmessages?
Thanks!
-Miguel
First thanks for OSCulator, having a lot of fun with it.
I have this application that I wrote that emits OSC message that look like this:
(taken from the console, simple logging)
"/klid/pattern_1323672071743: 60 | 127 | 1"
The message will always have this pattern:
"/klid/pattern_" + [uniqueID] + pitch + velocity + note_on/note_off
The application is web based with clients connecting to a website where they can send oscmessage to local server. The messages are used to send midi notes locally, with OSCulator acting as an osc-to-midi bridge.
My problem is that the uniqueID will always be different and the number of clients will always be changing. So manually assign messages to events is out of the question.
However, each will message will always have the same pattern and the same 3 parameters will always be sent. Any clue how I could configure OSCulator to send midi from those oscmessages?
Thanks!
-Miguel
Comment