Hello Camille and the others,
Considering those three softwares : lemur line, oscillator, and max 6.
In Max, i've managed to route a simple signal fader from Lemur iPad, threw Osculator, to Max 6. No problems. It works like a charm. Well… Next step : In the Lemur Editor, i create a new interface with one Pad icon composed of 6 columns and 6 rows (which renders, a beautiful grid of 36 triggering buttons). Great… In Osculator, i've got this : /Pads85/x and a sub-levels of numbers (the 36 buttons : 1 2 3 4 5 6 7 and so on). If i tap on my iPad on each button, it works well : Osculator see which button is triggered on the iPad ("Event Type" : Osc routing, and "Value" localhost 9000 set up).
One step forward, On Max 6 :
In my patch : I use the "udp" object (udp receive 9000), and the "route" object (written : route /Pads85/x), connected directly to the inlet of a "preset" object. Unfortunately, this manipulation doesn't work, and max don't know what button is triggered on iPad, even if Osculator see the changes.
Do you know how to tell to Max : "Max, my friend, guess what buttons is triggered under the repertory of /Pads85/x, threw Osculator".
I think there's a best and more flexible solution to point my pads buttons, instead of typing all the buttons in the route object :
/Pads85/1 /Pads85/2 /Pads85/3 /Pads85/4 /Pads85/5 /Pads85/6 /Pads85/7 /Pads85/8 and so on… which will be quite long, boring, and impossible to maintain in Max.
Any idea ?
Best
Crem'
Considering those three softwares : lemur line, oscillator, and max 6.
In Max, i've managed to route a simple signal fader from Lemur iPad, threw Osculator, to Max 6. No problems. It works like a charm. Well… Next step : In the Lemur Editor, i create a new interface with one Pad icon composed of 6 columns and 6 rows (which renders, a beautiful grid of 36 triggering buttons). Great… In Osculator, i've got this : /Pads85/x and a sub-levels of numbers (the 36 buttons : 1 2 3 4 5 6 7 and so on). If i tap on my iPad on each button, it works well : Osculator see which button is triggered on the iPad ("Event Type" : Osc routing, and "Value" localhost 9000 set up).
One step forward, On Max 6 :
In my patch : I use the "udp" object (udp receive 9000), and the "route" object (written : route /Pads85/x), connected directly to the inlet of a "preset" object. Unfortunately, this manipulation doesn't work, and max don't know what button is triggered on iPad, even if Osculator see the changes.
Do you know how to tell to Max : "Max, my friend, guess what buttons is triggered under the repertory of /Pads85/x, threw Osculator".
I think there's a best and more flexible solution to point my pads buttons, instead of typing all the buttons in the route object :
/Pads85/1 /Pads85/2 /Pads85/3 /Pads85/4 /Pads85/5 /Pads85/6 /Pads85/7 /Pads85/8 and so on… which will be quite long, boring, and impossible to maintain in Max.
Any idea ?
Best
Crem'
Comment