Hi list!
I'm finishing an application using PD & Processing (great combination for sound applications with easy & nice GUI!), but I have a little problem.
I use OSC communication (oscx library) to send & receive values from Processing to PD. PD receive data from GUI control in Processing, and send values stored in text files (sssad based saving state system) to Processing in order to change some presets. Everything it's OK!
But Processing OSCP5 library send error sometimes when receive values from PD because it expetcs floats but receive some integers! These values PD send are in the range from 0 to 1, therefore the problem appear when is sent a 0 or 1 (integers values).
I send this values with a [pack f f f f f f f f f f f f f] object, so I suposse any integer is converted in this way to a float, but I was wrong because Processing reads something like f f f f i f f f f i f f f (where i values are 0 or 1). Even if I edit the text file where values are stored, and I change 0 with 0.0 and 1 with 1.0, the same error appear.
How can I avoid this problem? Do I need to put a [float] object before each [pack f f f f f f f f f f f f f] inlet to make implicit the conversion? Or it is this behaviour an oscx bug?
Thanks in advance!
Saludos!
raul diaz wrote:
Or it is this behaviour an oscx bug?
as i do not get tired to repeat my self: "please do not use oscx if you are not prepared to handle bugs (there are several of them and it is not maintained anymore)"
use mrpeach's net/osc objects, which
- allows you to explicitely set the types of the OSC-atoms.
- has way fewer bugs
- has more features (transport independency, timestamps,...)
- is actively maintained
mfga.afdg IOhannes
Thanks for the advide IOhannes!
I will move to mrpeach's osc.
Tchuss!
2008/5/20 IOhannes m zmoelnig zmoelnig@iem.at:
raul diaz wrote:
Or it is this behaviour an oscx bug?
as i do not get tired to repeat my self: "please do not use oscx if you are not prepared to handle bugs (there are several of them and it is not maintained anymore)"
use mrpeach's net/osc objects, which
- allows you to explicitely set the types of the OSC-atoms.
- has way fewer bugs
- has more features (transport independency, timestamps,...)
- is actively maintained
mfga.afdg IOhannes
Hi IOhannes, all!
I have tried with mrpeach net/osc objects but I receive this error:
"udpsend: connecting to port 12000 error: udpsend_send: item 34 (-101.000000) is not between 0 and 255"
Must I send only positive values in the range between 0 - 255? And how can I specify explicitely the types of the OSC-atoms? I can't find any information about this in mrpeach folder at Pd 0.39.3-extended.
Thanks for all!
2008/5/20 raul diaz raul.lete@gmail.com:
Thanks for the advide IOhannes!
I will move to mrpeach's osc.
Tchuss!
2008/5/20 IOhannes m zmoelnig zmoelnig@iem.at:
raul diaz wrote:
Or it is this behaviour an oscx bug?
as i do not get tired to repeat my self: "please do not use oscx if you are not prepared to handle bugs (there are several of them and it is not maintained anymore)"
use mrpeach's net/osc objects, which
- allows you to explicitely set the types of the OSC-atoms.
- has way fewer bugs
- has more features (transport independency, timestamps,...)
- is actively maintained
mfga.afdg IOhannes
-- Raul Diaz Poblete
raul.lete@gmail.com Barcelona [Spain]
raul diaz wrote:
Hi IOhannes, all!
I have tried with mrpeach net/osc objects but I receive this error:
"udpsend: connecting to port 12000 error: udpsend_send: item 34 (-101.000000) is not between 0 and 255"
Must I send only positive values in the range between 0 - 255? And how can I specify explicitely the types of the OSC-atoms? I can't find any information about this in mrpeach folder at Pd 0.39.3-extended.
you have to convert your osc-message with [packOSC] (and decode it with [unpackOSC] on the receiving side) [udpsend] only takes raw-data (lists of bytes (disguised as floats))
fgmasdr IOhannes
Hi again!
you have to convert your osc-message with [packOSC] (and decode it with
[unpackOSC] on the receiving side) [udpsend] only takes raw-data (lists of bytes (disguised as floats))
I've used [packOSC] to send data to [udpsend] as in the help patches, but I receive error sending floats or negative values. You can look at this at attached patch.
Saludos!
No error here on MacOSX.4.11, PowerBook G4, pd-extended 20080520. ++
Jack
Le 20 mai 08 à 14:28, raul diaz a écrit :
Hi again!
you have to convert your osc-message with [packOSC] (and decode it
with [unpackOSC] on the receiving side) [udpsend] only takes raw-data (lists of bytes (disguised as floats))I've used [packOSC] to send data to [udpsend] as in the help
patches, but I receive error sending floats or negative values. You can look at this at attached patch.Saludos!
-- Raul Diaz Poblete
raul.lete@gmail.com Barcelona [Spain]<OSCsend-example.pd> _______________________________________________ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
-
IOhannes m zmoelnig -
Jack -
raul diaz