Hello, I have a problem with an osc message.
I have a raw of four switches and a monitor that shows me the number of the switch by creating the function z = firstof (x). When I press each switch, the monitor displays Good the value of the variable z : 0 1 2 3, but MaxMSP via osc message /switch/z always shows me the value 0 whichever the switch pressed.
I do not understand why ?
Is there a solution.
thank you
message osc problem with function firstof
-
- Newbie
- Posts: 39
- Joined: 18 Dec 2011 17:30
Re: message osc problem with function firstof
hi
I have the same problem ! on Max too. but it's not only with firstof but also with round() (I have just try this two expression) and when I pass inside a script !!!
I used Ipad1 with ios5.1.1 on mac with OSX 10.7.5
if you have suggest !!!
Thanks & best
o-o
I have the same problem ! on Max too. but it's not only with firstof but also with round() (I have just try this two expression) and when I pass inside a script !!!
I used Ipad1 with ios5.1.1 on mac with OSX 10.7.5
if you have suggest !!!
Thanks & best
o-o
-
- Newbie
- Posts: 39
- Joined: 18 Dec 2011 17:30
Re: message osc problem with function firstof
hi
If I show values on Lemur with monitor object, all is OK. It's on sending/transmitting via OSC where the message is corrupt. I haven't try if it's the same with Midi…
Are there a problem with older iPad Version or iOS or stuff like that ? Any other Have same problem ? This problem appear on recently iPad version or not ???
I hope this problem can solve soon !
best
f
If I show values on Lemur with monitor object, all is OK. It's on sending/transmitting via OSC where the message is corrupt. I haven't try if it's the same with Midi…
Are there a problem with older iPad Version or iOS or stuff like that ? Any other Have same problem ? This problem appear on recently iPad version or not ???
I hope this problem can solve soon !
best
f
Re: message osc problem with function firstof
Hey Saint_T,
another solution to achive "firstof" would be using "zl sub 1." in max (while sending the whole vector of knobs "Tralala/x" from lemur to max)
That way the variable calculation is in max. Thats the way I do, never tried calculating firstof on lemur and sending it to max... but in common your way seems possible too...
hope that helps
mat
another solution to achive "firstof" would be using "zl sub 1." in max (while sending the whole vector of knobs "Tralala/x" from lemur to max)
That way the variable calculation is in max. Thats the way I do, never tried calculating firstof on lemur and sending it to max... but in common your way seems possible too...
hope that helps
mat
Lemur modules and sequencer: http://music-interface.com
Setup: Win7professional 32bit, Intel Core 2 Duo @ 2,66 GHz.,Tascam US-144MKII, Ableton Live 8.4,
Arturia Analog Lab., Max/Msp, Maxforlive, Lemur Legacy + Ipad, Akai MPK61, Doepfer Pocket Control
Setup: Win7professional 32bit, Intel Core 2 Duo @ 2,66 GHz.,Tascam US-144MKII, Ableton Live 8.4,
Arturia Analog Lab., Max/Msp, Maxforlive, Lemur Legacy + Ipad, Akai MPK61, Doepfer Pocket Control
-
- Newbie
- Posts: 39
- Joined: 18 Dec 2011 17:30
Re: message osc problem with function firstof
hello
If I sent message via Midi, functions & sending run good… it's really on osc transmitting where the problem is.
best
f
If I sent message via Midi, functions & sending run good… it's really on osc transmitting where the problem is.
best
f
Re: message osc problem with function firstof
I found a solution with a script with the function oscout(). I disables x and the the script is oscout(0, '/test',firstof(x)); with on expression x. It's all ok.
Thank you to all.
Thank you to all.
-
- Liine Staff
- Posts: 285
- Joined: 01 Oct 2010 11:06
Re: message osc problem with function firstof
The following is broken in 5.0 and will be fixed in the 5.0.2 update:
- Fixed OSC output of integer variables
- Fixed OSC remote control of object attribute
The firstof(x) problem you describe sounds like a case of the first bug.
- Fixed OSC output of integer variables
- Fixed OSC remote control of object attribute
The firstof(x) problem you describe sounds like a case of the first bug.