Some early implementations of mrmr were using an integer from 0 to 1000. The "standard" range for numerical OSC message is a float going from 0.0 to 1.0. You can attach your files on this thread, or you can carry on this discussion by email if you prefer (camille at osculator dot net).Ībout the scaling of vs :Īt the time OSCulator was designed, it was supposed to work with a Lemur, or a Wiimote. I have experimented with a solution, and found it was working in some sense, but of course your could be totally different. I would like to help, but it is a bit difficult to anwser your question without having access to your oscd and touchosc files. I send it 64 and the fader shoots to the very top. In addition, rather than send a value of n(1/128) to the faders (where n = the MIDI note number I want) it would be much easier to send it the direct number 0-127 but even if I set the input scaling of the faders to 0-127, they still seem to respond on the basis 0-1. However, the value doesn't seem to get passed on to the buttons as they still output their 'old' pitch. That works in so faar as the faders move. However, I want to create a set of preset 'pitch sets' such that when I hit a button called 'Pitch Set 1', it sends each fader an OSC Routing fixed to the correct value for a set of pitches I want to use (say C Major). I have a set of buttons sending a 'MIDI Note /w params', each taken from a corresponding fader sending 'Note Param: Pitch', such that I select the notes I want on the faders, and then trigger them using the buttons. My set up is iPad -> TouchOSC -> OSCulator -> Logic
0 kommentar(er)
