 |
Re: OSC REMOTING
Started by Karol at 06-11-2009 12:48. Topic has 22 replies.
|
|
 06-11-2009, 12:48
|
Karol
 
Joined on 05-15-2005
Posts 428
|
|
|
Hi Colin,
is it possible that the other message is send on a different Port or Address?
Karol
|
|
|
|
|
Report
|
|
|
|
|
06-11-2009, 14:45
|
studioman
Joined on 01-07-2009
Posts 92
|
|
|
|
I'll check and get back to you
|
|
|
|
|
Report
|
|
|
|
|
06-11-2009, 14:52
|
studioman
Joined on 01-07-2009
Posts 92
|
|
|
|
don't think so , just checked the config xml file and there is only one port to configure.
ccv has the ability to output osc or to flash (tuioflashport) which is turned off in the program , so the only output is on 9001. the python sniffer is also set to listen on 9001 only and it's receiving both messages.
this is the config.
<!--// CAMERA SETTINGS // -->
<CAMERA_0>
<USECAMERA>1</USECAMERA>
<DEVICE>0</DEVICE>
<WIDTH>320</WIDTH>
<HEIGHT>240</HEIGHT>
<FRAMERATE>120</FRAMERATE>
</CAMERA_0>
<!--// NETWORK COMMUNICATION SETTINGS //-->
<NETWORK>
<LOCALHOST>192.168.5.33</LOCALHOST>
<TUIO>0</TUIO>
<TUIOPORT_OUT>9001</TUIOPORT_OUT>
<TUIOFLASHPORT_OUT>3000</TUIOFLASHPORT_OUT>
</NETWORK>
<!--// VIDEO SETTINGS // -->
<VIDEO>
<FILENAME>test_videos/RearDI.m4v</FILENAME>
</VIDEO>
<!--// BLOB SETTINGS // -->
<BLOBS>
<MAXNUMBER>20</MAXNUMBER>
</BLOBS>
|
|
|
|
|
Report
|
|
|
|
|
06-11-2009, 15:01
|
studioman
Joined on 01-07-2009
Posts 92
|
|
|
|
you can see in the received messages image that the alive version has the value "90" and the fseq version has the "5855" value, it's the alive version i need but for some reason i am only getting the fseq version, no matter how many floats or ints or strings I add to the node :(
cheers
Colin
|
|
|
|
|
Report
|
|
|
|
|
06-11-2009, 17:19
|
studioman
Joined on 01-07-2009
Posts 92
|
|
|
|
just managed to get hold of another listener which seems to work a lot better.
The entire message that is sent reads like this.
[000000001
/tuio/2Dcur "set" 21 0.842604
0.426593 0.000000 0.000000
0.000000
/tuio/2Dcur "alive" 21
/tuio/2Dcur "fseq" 2155
]
I can see that the "set" is the X Y info followed by acceleration and movement values.
"fseq" messages associate a unique frame id with a set of set and alive messages ( which I don't need at the moment but is being shown automatically in ventuz )
and the "alive" message, which is giving me an ON/OFF state with an id number.
I wonder how I can pick up these values in the inverted commas and why it is picking up fseq in a string argument but no others ?
Hope this helps with the deduction.
Cheers
Colin
|
|
|
|
|
Report
|
|
|
|
|
07-03-2009, 16:31
|
studioman
Joined on 01-07-2009
Posts 92
|
|
|
|
Hi Guys, Did you manage to have a look at this osc message format ?
|
|
|
|
|
Report
|
|
|
|
|
07-03-2009, 17:04
|
Karol
Joined on 05-15-2005
Posts 428
|
|
|
|
Hi Colin,
it´s the strange implementation of the OSC messaging of the TUIO protocol in version 1.1.
The command is part of the arguments which are send via OSC. The messages contain different commands and arguments but are send to the same OSC adress.
So you only receive the last message in Ventuz.
But it seams that they are aware of their ineffective implementation now. In the preview of the protocol version 2.0 they handle the OSC messaging correctly.
The only solution for you right now would be to handle the OSC messaging in a script of your own.
Best Regards
Karol
|
|
|
|
|
Report
|
|
|
|
|
07-03-2009, 22:06
|
chriss0212
Joined on 03-21-2006
Düsseldorf/ Germany
Posts 362
|
|
|
|
hi karol....
you are absolutly right (of course :-) ) so let us hope for version 2 :-)
but then: a osc node would be fantastic :-)
greetz
chriss
...........and don't give up :-)
|
|
|
|
|
Report
|
|
|
|
|
|