hi, just wondering if theres a way to receive plain floats/ints/messages with dumpOSC. i can print it, like "print: 2" shows in console or "print: apple", but driectly from [dumpOSC arg], numberboxes and messages coming from [set $1( 's are not working well. bangs work though. i turned typetags off. there a way to get these things? if typetags is easier, any have a quick method for stripping the received thing from dumposc of the slashes and whatnot... ok thanks ________________________________________________________________________ Check out the new AOL. Most comprehensive set of free safety and security tools, free access to millions of high-quality videos from across the web, free AOL Mail and more.
Could you use [route] to strip them? I'm not sure I understand the problem exactly. If you give route a 2 or more argument message (packed) then the creation argument will be stripped off.
When I use osc each message is usually preceded by "/test" or whatever. I use [route] to strip that.
Maybe this helps... not sure :)
Kevin
On 1/26/07, europa989@aol.com europa989@aol.com wrote:
hi, just wondering if theres a way to receive plain floats/ints/messages with dumpOSC. i can print it, like "print: 2" shows in console or "print: apple", but driectly from [dumpOSC arg], numberboxes and messages coming from [set $1( 's are not working well. bangs work though. i turned typetags off. there a way to get these things? if typetags is easier, any have a quick method for stripping the received thing from dumposc of the slashes and whatnot... ok thanks ________________________________________________________________________ Check out the new AOL. Most comprehensive set of free safety and security tools, free access to millions of high-quality videos from across the web, free AOL Mail and more.
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
hi, i understand now how route works. yeah. thanks. its a neat tool which i'll implement if good use for it comes up in future. what i was doing was sending [send 3( through [sendOSC]. this was producing "error: $1: argument number out of range". I didn't know that the message, regardless of initializing or disabling "typetags", would have to be the second? argument of the message "send". like [send blah 3( produces the result from dumpOSC. perhaps there is a way to only use one argument, as in what you want to transmit. whatever. ok thanks bunch..
-----Original Message----- From: km.takewithyou@gmail.com To: europa989@aol.com; PD-list@iem.at Sent: Fri, 26 Jan 2007 8:51 AM Subject: Re: [PD] osc typetags
Could you use [route] to strip them? I'm not sure I understand the
problem exactly. If you give route a 2 or more argument message (packed) then the creation argument will be stripped off.
When I use osc each message is usually preceded by "/test" or whatever. I use [route] to strip that.
Maybe this helps... not sure :)
Kevin
On 1/26/07, europa989@aol.com < europa989@aol.com> wrote:hi, just wondering if theres a way to receive plain floats/ints/messages with dumpOSC. i can print it, like "print: 2" shows in console or "print: apple", but driectly from [dumpOSC arg], numberboxes and messages coming from [set $1( 's are not working well. bangs work though. i turned typetags off. there a way to get these things? if typetags is easier, any have a quick method for stripping the received thing from dumposc of the slashes and whatnot... ok thanks
Check out the new AOL. Most comprehensive set of free safety and security tools, free access to millions of high-quality videos from across the web, free AOL Mail and more.
PD-list@iem.at mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
--
++++ http://pocketkm.blogspot.com
Check out the new AOL. Most comprehensive set of free safety and security tools, free access to millions of high-quality videos from across the web, free AOL Mail and more.
Hallo, europa989@aol.com hat gesagt: // europa989@aol.com wrote:
hi, i understand now how route works. yeah. thanks. its a neat tool which i'll implement if good use for it comes up in future. what i was doing was sending [send 3( through [sendOSC]. this was producing "error: $1: argument number out of range".
Could you post an example patch for this behaviour?
Frank Barknecht _ ______footils.org_ __goto10.org__
This is my guess: since you were mentioning [set $1( earlier, is this rather an issue with dollarsigns and not with OSC? The out of range error usually happens as a result of the message not being properly [pack]ed or just clicking a $1 message box instead of supplying it with the value needed to make $1 meaningful.
No? :)
Kevin
On 1/26/07, Frank Barknecht fbar@footils.org wrote:
Hallo, europa989@aol.com hat gesagt: // europa989@aol.com wrote:
hi, i understand now how route works. yeah. thanks. its a neat tool which i'll implement if good use for it comes up in future. what i was doing was sending [send 3( through [sendOSC]. this was producing "error: $1: argument number out of range".
Could you post an example patch for this behaviour?
Ciao
Frank Barknecht _ ______footils.org_ __goto10.org__
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list