hi list,
i have running eyesweb and pd on a pc and connected them with OSC successfully. so far so god. now i would like to know, how to get matrix data from EyesWeb to pd. i can receive and [print] the data but it seems that i can't [unpack] several values. did anybody do that? experience?
thanks, max
Hallo, Max Neupert hat gesagt: // Max Neupert wrote:
i have running eyesweb and pd on a pc and connected them with OSC successfully. so far so god. now i would like to know, how to get matrix data from EyesWeb to pd. i can receive and [print] the data but it seems that i can't [unpack] several values.
Could you post an example message as EyesWeb sends them?
Ciao
Frank Barknecht _ ______footils.org__
I 've tried this , i used a "matrix2scalar" in eyesweb , and then a [repack] in pd, that make a list that can be understood by gem. But all this is quiet slow and it seams that there is nothing you can do in eyesweb that you can not do in pd , witch is very faster .........
3o3
Max Neupert wrote:
hi list,
i have running eyesweb and pd on a pc and connected them with OSC successfully. so far so god. now i would like to know, how to get matrix data from EyesWeb to pd. i can receive and [print] the data but it seems that i can't [unpack] several values. did anybody do that? experience?
thanks, max
PD-list mailing list PD-list@iem.at to manage your subscription (including un-subscription) see http://iem.at/cgi-bin/mailman/listinfo/pd-list
we recently used Eyesweb in a theaterproject where we tracked and analysed the motion of the performer and send out the data via OSC to various computer for further processing. Some of the dataresults in EW are in matrixformat but I use the scalarfrommatrix object which gives access to the individual cells and sent them out as scalars.
in eyesweb that you can not do in pd , witch is very faster .........
While I done several motiontracking stuff with PD /gem and being really happy with that combination, I think Eyesweb can do some more stuff in that area. So if you are into motionanalysis AND on Windows (but the guys promised me a Linux version), go give it a try.
Cheers,
Malte
Am 09.06.2004 um 16:57 schrieb Malte Steiner:
we recently used Eyesweb in a theaterproject where we tracked and analysed the motion of the performer and send out the data via OSC to various computer for further processing. Some of the dataresults in EW are in matrixformat but I use the scalarfrommatrix object which gives access to the individual cells and sent them out as scalars.
i am also using the matrix to scalar and it it should (as far as i understand) send two coordinates as: /var1 56 45
through OSC and in pd i can do a [print] at retrieve var1 56
so here is already one coordinate missing.
then i can do [unpack s f] to get a var (in a symbol field) but there is no float coming out of the second outlet of the unpack.
i think i haven't understand the matrixtoscalar completely yet, but it seems that i am doing something wrong in pd too.
in eyesweb that you can not do in pd , witch is very faster .........
While I done several motiontracking stuff with PD /gem and being really happy with that combination, I think Eyesweb can do some more stuff in that area. So if you are into motionanalysis AND on Windows (but the guys promised me a Linux version), go give it a try.
i know, windows i evil, but the result counts in this case so that's why i want to do those tracking thing is EW.
we want to track a table soccer game..
Hallo Max, hello list
i am also using the matrix to scalar and it it should (as far as i understand) send two coordinates as: /var1 56 45
that shouldnt work. each number need to send out separate, so make it like /var1 56 /var2 45
and in PD with oscroute object something like
[osc-route /var1 /var2]
so this acts as your 'unpack', it gives you two outlets, one for var1 and one with var2
we want to track a table soccer game..
klasse idee :)
Cheers,
Malte
Hallo, Malte Steiner hat gesagt: // Malte Steiner wrote:
and in PD with oscroute object something like
[osc-route /var1 /var2]
It's called [OSCroute] in Pd. If someone knows offhand, how to create an alias to [OSC-route] - as it's called in Max AFAIK - in a C external, then I could add that to the CVS. I'm flext-polluted. :)
Ciao
Frank Barknecht _ ______footils.org__
Hi, I'm trying to send a list of 1024 floats from my app to pd via OSC, but always get a segmentation fault. Shorter lists (e.g. 32) do work. Sending 1024 floats to the terminal version of dumpOSC works too.
I'm a little new to OSC so maybe I'm missing something obvious. The floats are not organized in any complex structure anyway. [dumpOSC] is not connected to anything that could cause the crash.
OSC version is 0.2, freshly compiled from CVS. pd version is 0.37.1 devel installed thru planetCCRMA as is the rest of the machine (Fedora Core 1 version). Low latency is enabled, but there's no audio being computed anyway in this test.
thanks for any ideas, Sukandar
You're probably exceeding the maximum network packet length. UDP packets can have up to 65536 bytes of data but ethernet packets are not that long, more like 1500 bytes. So your 1024 floats take at least 1024*4 bytes, and they won't get through. On the local machine, ethernet is not used so the UDP packets can be longer.
Martin
----- Original Message ----- From: "Sukandar Kartadinata" sk@glui.de To: pd-list@iem.at Sent: Friday, June 18, 2004 1:58 PM Subject: [PD] OSC segmentation fault
Hi, I'm trying to send a list of 1024 floats from my app to pd via OSC, but always get a segmentation fault. Shorter lists (e.g. 32) do work. Sending 1024 floats to the terminal version of dumpOSC works too.
I'm a little new to OSC so maybe I'm missing something obvious. The floats are not organized in any complex structure anyway. [dumpOSC] is not connected to anything that could cause the crash.
OSC version is 0.2, freshly compiled from CVS. pd version is 0.37.1 devel installed thru planetCCRMA as is the rest of the machine (Fedora Core 1 version). Low latency is enabled, but there's no audio being computed anyway in this test.
thanks for any ideas, Sukandar
PD-list mailing list PD-list@iem.at to manage your subscription (including un-subscription) see http://iem.at/cgi-bin/mailman/listinfo/pd-list
hmm, thanks for the answer, I had some thoughts in that direction too, but: a. pd-dumpOSC already chokes on 64 floats (256 bytes) b. terminal-dumpOSC receives everything correctly c. there's no ethernet involved. all is local
btw, I just tried w/o type tags - no difference
thanks, Sukandar
On 18. Jun 2004, at 20:35 Uhr, Martin Peach wrote:
You're probably exceeding the maximum network packet length. UDP packets can have up to 65536 bytes of data but ethernet packets are not that long, more like 1500 bytes. So your 1024 floats take at least 1024*4 bytes, and they won't get through. On the local machine, ethernet is not used so the UDP packets can be longer.
Martin
----- Original Message ----- From: "Sukandar Kartadinata" sk@glui.de To: pd-list@iem.at Sent: Friday, June 18, 2004 1:58 PM Subject: [PD] OSC segmentation fault
Hi, I'm trying to send a list of 1024 floats from my app to pd via OSC, but always get a segmentation fault. Shorter lists (e.g. 32) do work. Sending 1024 floats to the terminal version of dumpOSC works too.
I'm a little new to OSC so maybe I'm missing something obvious. The floats are not organized in any complex structure anyway. [dumpOSC] is not connected to anything that could cause the crash.
OSC version is 0.2, freshly compiled from CVS. pd version is 0.37.1 devel installed thru planetCCRMA as is the rest of the machine (Fedora Core 1 version). Low latency is enabled, but there's no audio being computed anyway in this test.
thanks for any ideas, Sukandar
PD-list mailing list PD-list@iem.at to manage your subscription (including un-subscription) see http://iem.at/cgi-bin/mailman/listinfo/pd-list
In dumpOSC.c I see: #define MAXMESG 32768 static char mbuf[MAXMESG]; ... which looks like the maximum packet size is 32768.
Also: #define MAXOUTAT 50 sets the size of an array in the t_dumpOSC struct. ...so the maximum number of values the functions in dumpOSC can handle in the packet is 50. Elsewhere the variable myargc is incremented for each value parsed out of the OSC packet but no check is done to see if it exceeds MAXOUTAT, hence the segfault when memory gets overwritten. You could try compiling dumpOSC.c with MAXOUTAT set to 1024 or more.
Martin
----- Original Message ----- From: "Sukandar Kartadinata" sk@glui.de To: pd-list@iem.at Sent: Friday, June 18, 2004 2:57 PM Subject: Re: [PD] OSC segmentation fault
hmm, thanks for the answer, I had some thoughts in that direction too, but: a. pd-dumpOSC already chokes on 64 floats (256 bytes) b. terminal-dumpOSC receives everything correctly c. there's no ethernet involved. all is local
btw, I just tried w/o type tags - no difference
thanks, Sukandar
On 18. Jun 2004, at 20:35 Uhr, Martin Peach wrote:
You're probably exceeding the maximum network packet length. UDP packets can have up to 65536 bytes of data but ethernet packets are not that long, more like 1500 bytes. So your 1024 floats take at least 1024*4 bytes, and they won't get through. On the local machine, ethernet is not used so the UDP packets can be longer.
Martin
----- Original Message ----- From: "Sukandar Kartadinata" sk@glui.de To: pd-list@iem.at Sent: Friday, June 18, 2004 1:58 PM Subject: [PD] OSC segmentation fault
Hi, I'm trying to send a list of 1024 floats from my app to pd via OSC, but always get a segmentation fault. Shorter lists (e.g. 32) do work. Sending 1024 floats to the terminal version of dumpOSC works too.
I'm a little new to OSC so maybe I'm missing something obvious. The floats are not organized in any complex structure anyway. [dumpOSC] is not connected to anything that could cause the crash.
OSC version is 0.2, freshly compiled from CVS. pd version is 0.37.1 devel installed thru planetCCRMA as is the rest of the machine (Fedora Core 1 version). Low latency is enabled, but there's no audio being computed anyway in this test.
thanks for any ideas, Sukandar
PD-list mailing list PD-list@iem.at to manage your subscription (including un-subscription) see http://iem.at/cgi-bin/mailman/listinfo/pd-list
PD-list mailing list PD-list@iem.at to manage your subscription (including un-subscription) see http://iem.at/cgi-bin/mailman/listinfo/pd-list
aaah, thanks again Martin, that makes things clearer
I'd have some follow up questions then...
I seem to remember that when I first heard about OSC, one of the applications it was demoed with was to send large arrays of spectral data around to drive STFTs, oscillator banks or phase vocoders. Which is exactly what I'm attempting now. If sending e.g. an FFT frame as one big array was/is not intended, then I'm wondering what the general strategies are to send such large chunks of data. Surely I could split it up in smaller messages but then it'd become kinda tedious to regroup e.g. 32 lists with 32 numbers each back into one frame.
thanks much, Sukandar (recompiling...)
On 18. Jun 2004, at 21:55 Uhr, Martin Peach wrote:
In dumpOSC.c I see: #define MAXMESG 32768 static char mbuf[MAXMESG]; ... which looks like the maximum packet size is 32768.
Also: #define MAXOUTAT 50 sets the size of an array in the t_dumpOSC struct. ...so the maximum number of values the functions in dumpOSC can handle in the packet is 50. Elsewhere the variable myargc is incremented for each value parsed out of the OSC packet but no check is done to see if it exceeds MAXOUTAT, hence the segfault when memory gets overwritten. You could try compiling dumpOSC.c with MAXOUTAT set to 1024 or more.
Martin
----- Original Message ----- From: "Sukandar Kartadinata" sk@glui.de To: pd-list@iem.at Sent: Friday, June 18, 2004 2:57 PM Subject: Re: [PD] OSC segmentation fault
hmm, thanks for the answer, I had some thoughts in that direction too, but: a. pd-dumpOSC already chokes on 64 floats (256 bytes) b. terminal-dumpOSC receives everything correctly c. there's no ethernet involved. all is local
btw, I just tried w/o type tags - no difference
thanks, Sukandar
On 18. Jun 2004, at 20:35 Uhr, Martin Peach wrote:
You're probably exceeding the maximum network packet length. UDP packets can have up to 65536 bytes of data but ethernet packets are not that long, more like 1500 bytes. So your 1024 floats take at least 1024*4 bytes, and they won't get through. On the local machine, ethernet is not used so the UDP packets can be longer.
Martin
----- Original Message ----- From: "Sukandar Kartadinata" sk@glui.de To: pd-list@iem.at Sent: Friday, June 18, 2004 1:58 PM Subject: [PD] OSC segmentation fault
Hi, I'm trying to send a list of 1024 floats from my app to pd via OSC, but always get a segmentation fault. Shorter lists (e.g. 32) do work. Sending 1024 floats to the terminal version of dumpOSC works too.
I'm a little new to OSC so maybe I'm missing something obvious. The floats are not organized in any complex structure anyway. [dumpOSC] is not connected to anything that could cause the crash.
OSC version is 0.2, freshly compiled from CVS. pd version is 0.37.1 devel installed thru planetCCRMA as is the rest of the machine (Fedora Core 1 version). Low latency is enabled, but there's no audio being computed anyway in this test.
thanks for any ideas, Sukandar
PD-list mailing list PD-list@iem.at to manage your subscription (including un-subscription) see http://iem.at/cgi-bin/mailman/listinfo/pd-list
PD-list mailing list PD-list@iem.at to manage your subscription (including un-subscription) see http://iem.at/cgi-bin/mailman/listinfo/pd-list
PD-list mailing list PD-list@iem.at to manage your subscription (including un-subscription) see http://iem.at/cgi-bin/mailman/listinfo/pd-list
Sukandar Kartadinata sk@glui.de wrote:
I seem to remember that when I first heard about OSC, one of the applications it was demoed with was to send large arrays of spectral data around to drive STFTs, oscillator banks or phase vocoders. Which is exactly what I'm attempting now. If sending e.g. an FFT frame as one big array was/is not intended, then I'm wondering what the general strategies are to send such large chunks of data. Surely I could split it up in smaller messages but then it'd become kinda tedious to regroup e.g. 32 lists with 32 numbers each back into one frame.
I think the advantage of OSC is the ability to send small chunks of data to specific addresses inside of another process. If you are sending large amounts of almost realtime data, it would be better to use straight UDP.
Martin
for me it worked with matrix to scalar (row aorder, aferter hitcelldetector e.g.) on eyesweb and repack (no of items/matrix as arguments) followed ny unpack
At 18:43 09.06.2004 +0200, you wrote:
Am 09.06.2004 um 16:57 schrieb Malte Steiner:
we recently used Eyesweb in a theaterproject where we tracked and analysed the motion of the performer and send out the data via OSC to various computer for further processing. Some of the dataresults in EW are in matrixformat but I use the scalarfrommatrix object which gives access to the individual cells and sent them out as scalars.
i am also using the matrix to scalar and it it should (as far as i understand) send two coordinates as: /var1 56 45
through OSC and in pd i can do a [print] at retrieve var1 56
so here is already one coordinate missing.
then i can do [unpack s f] to get a var (in a symbol field) but there is no float coming out of the second outlet of the unpack.
i think i haven't understand the matrixtoscalar completely yet, but it seems that i am doing something wrong in pd too.
in eyesweb that you can not do in pd , witch is very faster .........
While I done several motiontracking stuff with PD /gem and being really happy with that combination, I think Eyesweb can do some more stuff in that area. So if you are into motionanalysis AND on Windows (but the guys promised me a Linux version), go give it a try.
i know, windows i evil, but the result counts in this case so that's why i want to do those tracking thing is EW.
we want to track a table soccer game..
Am 11.06.2004 um 11:57 schrieb Michael Iber:
for me it worked with matrix to scalar (row order, after hitcelldetector e.g.) on eyesweb and repack (no of items/matrix as arguments) followed ny unpack
i am sorry if this thread becomes off-topic because it seems to be more an EyesWeb problem. Michael, could you explain how to configure the matrix to scalar object in order to let it send individual values? what do you mean with “after hitcelldetector???” i searched for that object in EW but could not find anything.
max
At 18:43 09.06.2004 +0200, you wrote:
Am 09.06.2004 um 16:57 schrieb Malte Steiner:
we recently used Eyesweb in a theaterproject where we tracked and analysed the motion of the performer and send out the data via OSC to various computer for further processing. Some of the dataresults in EW are in matrixformat but I use the scalarfrommatrix object which gives access to the individual cells and sent them out as scalars.
i am also using the matrix to scalar and it it should (as far as i understand) send two coordinates as: /var1 56 45
through OSC and in pd i can do a [print] at retrieve var1 56
so here is already one coordinate missing.
then i can do [unpack s f] to get a var (in a symbol field) but there is no float coming out of the second outlet of the unpack.
i think i haven't understand the matrixtoscalar completely yet, but it seems that i am doing something wrong in pd too.
in eyesweb that you can not do in pd , witch is very faster .........
While I done several motiontracking stuff with PD /gem and being really happy with that combination, I think Eyesweb can do some more stuff in that area. So if you are into motionanalysis AND on Windows (but the guys promised me a Linux version), go give it a try.
i know, windows i evil, but the result counts in this case so that's why i want to do those tracking thing is EW.
we want to track a table soccer game..
-
Frank Barknecht -
Malte Steiner -
Martin Peach -
Max Neupert -
Michael Iber -
Sukandar Kartadinata -
zozizozu