Re: [PD] preset system for complex gem patches

2009-02-05 Thread punchik punchik
many thanks for the explanation ! --- On Thu, 2/5/09, Frank Barknecht wrote: > From: Frank Barknecht > Subject: Re: [PD] preset system for complex gem patches > To: pd-list@iem.at > Date: Thursday, February 5, 2009, 2:32 PM > Hallo, > punchik punchik hat gesagt: // punchik punchik wrote: > >

Re: [PD] preset system for complex gem patches

2009-02-05 Thread Frank Barknecht
Hallo, punchik punchik hat gesagt: // punchik punchik wrote: > Hi, ive been working on a complex gem patch for creating 3d > structures, the patch has a lot of parameters for changing translation > , rotation, scale, color, etc. I want to make a preset system for > saving the states of interesting

Re: [PD] preset system for complex gem patches

2009-02-05 Thread Hans-Christoph Steiner
Definitely not coll. Look at sssad or mememto, or maybe pool. There is also Mike McGonagle's sqlite object if you want a full database. .hc On Feb 5, 2009, at 1:29 PM, punchik punchik wrote: > Hi, ive been working on a complex gem patch for creating 3d > structures, the patch has a lot of

[PD] preset system for complex gem patches

2009-02-05 Thread punchik punchik
Hi, ive been working on a complex gem patch for creating 3d structures, the patch has a lot of parameters for changing translation , rotation, scale, color, etc. I want to make a preset system for saving the states of interesting shapes and then load them, Do anybody have tried something like th

Re: [PD] Very Strange Behaviour of dumpOSC on Pd

2009-02-05 Thread Roman Haefeli
On Thu, 2009-02-05 at 18:12 +0100, Jack wrote: > Thanx Roman for the clarification. I thought that [tcpsend]/ > [tcpreceive] worked with OSC. > I think it must be specify somewhere in the help patch (with > [packOSC]/[unpackOSC] or/and [tcpsend]/[tcpreceive] ?). > I just download abstractions fr

Re: [PD] here I go again..dynamic abstractions

2009-02-05 Thread IOhannes m zmoelnig
Rory Walsh wrote: > [...] read about $0. it does exactly what you want without having to dynamically change anything. just use "$0-tgl-1" as a send/receive name in each abstractions and be happy. fgmadsr IOhannes smime.p7s Description: S/MIME Cryptographic Signature ___

[PD] here I go again..dynamic abstractions

2009-02-05 Thread Rory Walsh
I keep running into problem with an abstraction I'm trying to implement. Let me first explain what I'm trying to do. I have an abstraction that has 16 tgls in a row. These are graphed on parent so they they can be altered from the main patch. When a user clicks on of the tgls it changes colour. Thi

Re: [PD] wavetable lookup

2009-02-05 Thread Frank Barknecht
Hallo, Rapha?l ILIAS hat gesagt: // Rapha?l ILIAS wrote: > I'm thinking about a way to produce a short table which would sum up a sound > table. This might be a way to prevent audioclicks when displaying a huge > wavetable, or an idea to be able "zoom" on a part of the table. I tried the > firs

Re: [PD] Very Strange Behaviour of dumpOSC on Pd

2009-02-05 Thread Jack
Thanx Roman for the clarification. I thought that [tcpsend]/ [tcpreceive] worked with OSC. I think it must be specify somewhere in the help patch (with [packOSC]/[unpackOSC] or/and [tcpsend]/[tcpreceive] ?). I just download abstractions from : http://romanhaefeli.net/software/pd/OSCstream.tar.gz

[PD] wavetable lookup

2009-02-05 Thread Raphaël ILIAS
Hi ! I'm thinking about a way to produce a short table which would sum up a sound table. This might be a way to prevent audioclicks when displaying a huge wavetable, or an idea to be able "zoom" on a part of the table. I tried the first method that came to my mind : just to play the sample while

Re: [PD] Very Strange Behaviour of dumpOSC on Pd

2009-02-05 Thread Roman Haefeli
--- Jack schrieb am Do, 5.2.2009: > Yep, as Roman says try [udpreceive] with [unpackOSC] (OSC > comme often > 'on' UDP) or [tcpreceive] with [unpackOSC], if you > want a service > with connection. The choice depends if you absolutely need > to receive > your data. > AFAIK, OSCx accepts o

Re: [PD] Very Strange Behaviour of dumpOSC on Pd

2009-02-05 Thread mbutubuntu
I think the problem is "server side" processing couldn't open a socket... :P:P IOhannes m zmoelnig wrote: > mbutubuntu wrote: >> JacK, I know... packOSC works, but udpsend doesn't connect, neither >> tcpsend... >> > > highly unlikely. > show your patch :-) > > fgmasdr > IOhannes _

Re: [PD] Very Strange Behaviour of dumpOSC on Pd

2009-02-05 Thread IOhannes m zmoelnig
mbutubuntu wrote: JacK, I know... packOSC works, but udpsend doesn't connect, neither tcpsend... highly unlikely. show your patch :-) fgmasdr IOhannes smime.p7s Description: S/MIME Cryptographic Signature ___ Pd-list@iem.at mailing list UNSUBSCRI

Re: [PD] Very Strange Behaviour of dumpOSC on Pd

2009-02-05 Thread Jack
Ah, ok :) Have you open [routeOSC] and [packOSC] in mrpeach ? Click on [connect 127.0.0.1 9997( message, you must have in the console : udpsend: connecting to port 9997 Then click on [send /test/one/two/three zz 88 T( message, you must have in the console : print: /test/one/two/three zz 88 T er

Re: [PD] Very Strange Behaviour of dumpOSC on Pd

2009-02-05 Thread mbutubuntu
JacK, I know... packOSC works, but udpsend doesn't connect, neither tcpsend... Jack wrote: > If you use OSC, you need [packOSC] before [udpsend]. See the help > patch of [packOSC] in mrpeach. > ++ > > Jack > > > Le 5 févr. 09 à 16:12, mbutubuntu a écrit : > >> thanks... udpreceive wors wery wel

Re: [PD] Very Strange Behaviour of dumpOSC on Pd

2009-02-05 Thread Jack
If you use OSC, you need [packOSC] before [udpsend]. See the help patch of [packOSC] in mrpeach. ++ Jack Le 5 févr. 09 à 16:12, mbutubuntu a écrit : > thanks... udpreceive wors wery well but udpsend > doesn't... :P:P > > > > Jack wrote: >> Yep, as Roman says try [udpreceive] with [u

Re: [PD] Very Strange Behaviour of dumpOSC on Pd

2009-02-05 Thread mbutubuntu
thanks... udpreceive wors wery well but udpsend doesn't... :P:P Jack wrote: > Yep, as Roman says try [udpreceive] with [unpackOSC] (OSC comme often > 'on' UDP) or [tcpreceive] with [unpackOSC], if you want a service with > connection. The choice depends if you absolutely need to receiv

Re: [PD] Very Strange Behaviour of dumpOSC on Pd

2009-02-05 Thread Jack
Yep, as Roman says try [udpreceive] with [unpackOSC] (OSC comme often 'on' UDP) or [tcpreceive] with [unpackOSC], if you want a service with connection. The choice depends if you absolutely need to receive your data. AFAIK, OSCx accepts only UDP protocol. ++ Jack Le 5 févr. 09 à 14:15, Rom

[PD] public opinion poll

2009-02-05 Thread mbutubuntu
what about netsend~ vs nstream~ ??? ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

Re: [PD] communicating with the shell

2009-02-05 Thread Martin Schied
Chris McCormick wrote: Attached is a concrete example of this for your specific use case. It allows you to run arbitrary commands on your shell and get the results back into Pd. I know you said that this seems messy to you, but I feel that Claude's way is actually quite elegant. Untar the attach

Re: [PD] Very Strange Behaviour of dumpOSC on Pd

2009-02-05 Thread Roman Haefeli
--- mbutubuntu schrieb am Do, 5.2.2009: > hello folks, I'm using OSC to send information from > Processing to Pd... > I started writing my "receiving" Patch in a > Computer where was Installed > Ubuntu 8.04 and Pd-extended 0.40.3 in stalled by the .deb > package, my > laptop was an Archlinu

[PD] Very Strange Behaviour of dumpOSC on Pd

2009-02-05 Thread mbutubuntu
hello folks, I'm using OSC to send information from Processing to Pd... I started writing my "receiving" Patch in a Computer where was Installed Ubuntu 8.04 and Pd-extended 0.40.3 in stalled by the .deb package, my laptop was an Archlinux "client" in which Processing was running... Processing s

Re: [PD] communicating with the shell

2009-02-05 Thread Chris McCormick
On Wed, Jan 28, 2009 at 02:26:13PM +, Rob Canning wrote: > (it would be really nice to have an object for communicating with the > shell that is not buggy.) [snip] > also this method is fine for sending stuff to the shell but what about > getting results back from the shell? like a bang whe