[PD] Question reference patches
Hello, i am building a project that uses several audio channels. That is all working well. No I have one question. I have build one channel and put that into a patch [pd channel] Each [pd channel] holds a [dac~ n]. If I then copy the [pd channel] and make changes in one [pd channel] changes are not reflected in the others. It seems that a copy is made from the patch, I would like to know if it is possible to make each copy a reference to a patch so that changes in one is reflected in many. Then I also wonder if it is possible to set the [dac~ n] at 'runtime'. n otherwords is it possible to have a var setting the output channel. I hope somebody can help me, and many thanks to those who can. Jiri ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Question reference patches
Jiri Heitlager wrote: Hello, i am building a project that uses several audio channels. That is all working well. No I have one question. I have build one channel and put that into a patch [pd channel] Each [pd channel] holds a [dac~ n]. If I a [pd] is NOT a patch but a sub-patch. it's only purpose is to make your code more readable by hiding stuff (well, not entirely true when it comes to datastructures, but ignore this for now), and NOT for re-using code. for this you have to make _abstraction_s. an abstraction is a pd patch saved to disk. e.g. create a new patch (Ctrl-N), copy the channel-code in there, and save it as channel.pd. now you can create objects [channel], each holding one instance of the channel-code. of course you will have to parametrize your abstraction by use of arguments (dollargs): use [dac~ $1] within the channel.pd and call it as [channel 5] which will magically address the [dac~ 5] within this instance. this is certainly described within the documentation that comes with pd (e.g. doc/2.control.examples/12.PART2.subpath.pd) mfg.asdr. IOhannes ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Question reference patches
Hallo, Jiri Heitlager hat gesagt: // Jiri Heitlager wrote: i am building a project that uses several audio channels. That is all working well. No I have one question. I have build one channel and put that into a patch [pd channel] Each [pd channel] holds a [dac~ n]. If I then copy the [pd channel] and make changes in one [pd channel] changes are not reflected in the others. It seems that a copy is made from the patch, I would like to know if it is possible to make each copy a reference to a patch so that changes in one is reflected in many. You stumbled accros the difference between a subpatch like [pd subpatch] and an abstraction, which is a complete patch saved as a seperate file in the working directory or somewhere in Pd's search path. You want an abstraction here instead of a subpatch. To make on, just copy the contents of [pd channel] to a new file, save that as e.g. channel.pd and then use that instead of [pd channel] by creating an object [channel]. Then I also wonder if it is possible to set the [dac~ n] at 'runtime'. n otherwords is it possible to have a var setting the output channel. Somehow it is: If you write your channel.pd abstraction to use a [dac $1] you can create [channel 1], [channel 2] ... [channel 16] objects, and [dac $1] will be the same as [dac~ 1], [dac~ 2] ... [dac~ 16] in the respective [channel ...] instances. Ciao -- Frank Barknecht _ __footils.org_ __goto10.org__ ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] puredatabase
On 07/02/2007, at 2.25, David Powers wrote: On 2/6/07, Steffen [EMAIL PROTECTED] wrote: And a suggestion: It might be good to debate here how the database should be designed to best do it job. Fx. would it be an idea to make a set of (not necessarily disjunkt/non-intersecting) categories/ labels objects/libs could fit in - like math, audio, control, graphic (inspired by http://puredata.info/dev/PdLibraries)? I mean, there must be a quite a few opinions on how the database could be organized in order to be of most use. It would be nice if things could be tagged with keywords, rather than categorized. That way, there's no need to think of every category or decide on all keywords in advance, people could add keywords to objects as they saw fit. I agree. That what i meant by 'not necessarily non-intersecting categories'. It might be a bad choice to use the word category like that - I'm sorry. But it was mostly meant as an example of an idea we could want in such database. Since I0 said: help with database-design [...] might be appreciated I thought we (the potential users of the database) in this phase could brainstorm and discuss ideas on how we would like it. ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [pd] shaper filter
well, i downloaded the manual for the k2000, and from what i can gather, the shaper filter that my friend told me about is not actually a filter at all, but a waveshaper not very far removed from pd's [cos~] object, but with a couple of important tweaks. sounds ok. think i will string a few together and detune them and make some funky envelopes...but for the moment here is the basic patch if u care. shaper0.0.5.pd Description: Binary data ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [pd] shaper filter
aaarrhh! watch your speakers if you play that patch, it will start making sound as soon as it is opened, and it's pretty loud. ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Turing Machine
On 07/02/2007, at 3.26, Hans-Christoph Steiner wrote: On Feb 6, 2007, at 5:22 PM, Frank Barknecht wrote: Hallo, Tim Boykett hat gesagt: // Tim Boykett wrote: Frank, This is completely mad! Glad you like it and I hope you're doing well. Wow, that is quite something. Yeah, this is so cool it hurts my teeth. The potential of scoring with Turing blows my mind. We really need to get that puredata.org gallery up for things like this. Indeed! ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] flext, fluid~, readanysf~, and FLEXT_USE_CMEM (or don't)
moin Conor, On 2007-02-07 01:12:05, Conor J Curran [EMAIL PROTECTED] appears to have written: sounds familiar indeed... have you by any chance tried compiling your external without threads, linking (statically) to libflext-pd_s.a ? I don't know if you need threads or not, but at least that might narrow down the range of possible error sources... I have not but I was under the impression that if I was to compile my external in the current flext setup using single-release. This would imply no use of threads and also statically linking to the .a lib as opposed to the .so. Is this correct? If not what do I need to do to ensure I do so? Sorry but I might have mentioned before I pretty clueless with this gcc stuff. yep, afaik any -single build should produce a threadless (the official term in Thomas' documentation appears to be single-threaded) version; at least, the flext build system won't define FLEXT_THREADS for *-single builds. Just make sure you're not defining it yourself ;-) ... I'd try it without FLEXT_THREADS (libpthread), both with and without FLEXT_USE_CMEM: that might make things clearer. I think this can be accomplished by: (a) ensuring that FLEXT_THREADS is undefined for your external (-UFLEXT_THREADS) Should -UFLEXT_THREADS be added to my config.txt in the external directory. UFLAGS += -UFLEXT_THREADS ? Or should I ensure it is no defined. -U = undefine ? If you're not defining it (e.g. with -DFLEXT_THREADS or with a #define in some source file), then you're ok: it won't be defined by flext build.sh for a *-single build. Maybe it might help to remove the -pthread compiler linker flags for threadless (shared,single) builds: this amounts to editing flext/buildsys/lnx/gnumake-gcc.inc, and the idea is just a shot in the dark, but at least it would make debugging easier ;-) I have edited this file so now the part which did contain the pthread stuff looks like this ## #removed from both: -pthread CFLAGS += -fPIC LDFLAGS += -shared yep, that's the bit I meant. As I noted yesterday, my fluid~ problems were due to a missing initialization / assumed zero-initialization of the object's memory, which resulted in an attempt to free() a pointer of basically random junk (either unallocated or allocated by a different program or thread or whatever)... According to the gcc docs: -pthread Add support for multithreading using the POSIX threads library. This option sets flags for both the preprocessor and linker. It does not affect the thread safety of object code produced by the compiler or that of libraries supplied with it. These are HP-UX specific flags. ... there are -pthread flags listed for other architectures too, and gcc doesn't complain about the flags, but I haven't yet found any docs for the -pthread option on x86, so maybe it doesn't do anything at all here except maybe link to libpthread... One question are you working from 5.0 release of flext or are you using the head of cvs? I'm using the head of cvs, and I haven't actually removed the -pthread from my build flags here. Of course, I am still getting bizarre crashes lockups, but not the fluid~-related ones. marmosets, Bryan -- Bryan Jurish There is *always* one more bug. [EMAIL PROTECTED] -Lubarsky's Law of Cybernetic Entomology ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Live Apectrum Analyzer
hi, just got a link from a friend to this software spectrum analyzer: http://www.baudline.com/ best e - http://randomseed.org On Thu, 1 Feb 2007, Thomas Mayer wrote: Hello, thanks for all your suggestions, TAPESTREA looks great, but I'm just intrigued by the patch of carmen. After playing around a while with some objects, the following idea came into my mind: Create a [pdp_xv] canvas with 800x640 pixels. Use the values of [fft~] as right input for [pdp_gain] and multiply it with a white rectangle of 10x10 pixels and put it in the right place (bottom to top in column) Goto next column and repeat (50 ms), so the pic will look like: ^ | | |--- 64 values from fft~ | | | | -- 80 values for time (=4 s) So, for now, I'd ask for some specific objects: How can I split lists of audio data, as [snapshot~] only outputs the first value? The 4.fft.examples folders from CVS is empty, and the help for fft~ is not really helpful. Is there any help for tweaking [fft~] available, e.g. setting window size (in frequency domain)? Is there a pdp/pidip object that can put a picture in a desired position on a pdp window? Thanks, Thomas -- Prisons are needed only to provide the illusion that courts and police are effective. They're a kind of job insurance. (Leto II. in: Frank Herbert, God Emperor of Dune) http://thomas.dergrossebruder.org/ ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] gem - feedback perspective
hi, just realised that anti-aliasing settings also tend to interfere with feedback: enabling any sort of anti-aliasing via |FSAA x( fscks up clean feedback on my geforce 5700 with the 1.0.8776 driver blob. with kind regards, thoralf. ___ What kind of emailer are you? Find out today - get a free analysis of your email personality. Take the quiz at the Yahoo! Mail Championship. http://uk.rd.yahoo.com/evt=44106/*http://mail.yahoo.net/uk ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [pd] shaper filter
hard off a écrit : .but for the moment here is the basic patch if u care. Excellent! It reminds me the sound of a famous song I don't remember the name, I tried to make the sequence of this song gimmick in the attached patch #N canvas 120 84 807 552 10; #N canvas 0 22 458 308 (subpatch) 0; #X array v.a.s.t 131 float 1; #A 0 0 0 0 0 0 0 0 0.0169492 0.0338983 0.0508475 0.0677966 0.0847458 0.101695 0.135593 0.169492 0.20339 0.220339 0.20339 0.20339 0.220339 0.237288 0.254237 0.254237 0.254237 0.271186 0.305085 0.322034 0.338983 0.372881 0.40678 0.440678 0.474576 0.491525 0.457627 0.440678 0.457627 0.457627 0.457627 0.440678 0.372881 0.254237 0.220339 0.254237 0.305085 0.288136 0.254237 0.20339 0.186441 0.169492 0.186441 0.186441 0.135593 0.0847458 0.0338983 -0.0338983 -0.101695 -0.169492 -0.271186 -0.355932 -0.423729 -0.440678 -0.423729 -0.474576 -0.559322 -0.576271 -0.508475 -0.423729 -0.40678 -0.457627 -0.508475 -0.59322 -0.677966 -0.711864 -0.728814 -0.779661 -0.864407 -0.966102 -1 -0.966102 -0.898305 -0.79661 -0.711864 -0.711864 -0.745763 -0.762712 -0.711864 -0.627119 -0.576271 -0.627119 -0.711864 -0.779661 -0.813559 -0.813559 -0.762712 -0.677966 -0.576271 -0.508475 -0.508475 -0.474576 -0.355932 -0.254237 -0.220339 -0.135593 0 0.0677966 0.0169492 -0.0508475 -0.0677966 0.0169492 0.135593 0.169492 0.101695 0.0338983 0.0677966 0.152542 0.288136 0.423729 0.474576 0.457627 0.474576 0.559322 0.644068 0.677966 0.644068 0.576271 0.576271 0.542373 0.525424 0.508475 0.508475 0.525424; #X coords 0 1 130 -1 200 140 1; #X restore 31 177 graph; #X floatatom 622 265 5 0 0 0 - #0-downphasor -; #X obj 17 76 soundfiler; #X obj 17 35 openpanel; #X obj 16 13 bng 15 250 50 0 empty empty empty 0 -6 0 8 -262144 -1 -1; #X obj 622 303 phasor~ 0.1; #X floatatom 430 270 5 0 1000 0 - #0-sigfreq -; #X obj 468 287 mtof; #X obj 18 93 t b; #X msg 16 56 read \$1 v.a.s.t; #X msg 17 112 \; v.a.s.t normalize; #N canvas 0 22 524 570 shaper 0; #X obj 206 454 cos~; #X obj 211 329 ~ 2; #X obj 246 330 ~ -2; #X obj 227 366 ==~ 0; #X obj 193 396 *~; #X obj 204 429 +~ 0.25; #X obj 89 196 *~; #X obj 182 106 *~; #X obj 293 277 * -1; #X obj 187 291 *~ 2; #X obj 287 198 t b f; #X obj 293 238 * 2; #X obj 347 213 * 2; #X obj 213 80 / 64; #X obj 213 56 r \$0-deps; #X obj 347 170 r \$0-deps; #X obj 346 66 r \$0-lims; #X obj 346 136 / 256; #X obj 347 113 abs; #X obj 347 88 - 257; #X obj 347 191 / 64; #X obj 80 36 inlet~ signal; #X obj 178 36 inlet~ envelope; #X obj 207 478 outlet~; #X connect 0 0 23 0; #X connect 1 0 3 0; #X connect 2 0 3 0; #X connect 3 0 4 1; #X connect 4 0 5 0; #X connect 5 0 0 0; #X connect 6 0 9 0; #X connect 7 0 6 1; #X connect 8 0 2 1; #X connect 9 0 1 0; #X connect 9 0 2 0; #X connect 9 0 4 0; #X connect 10 0 11 0; #X connect 10 1 11 1; #X connect 11 0 8 0; #X connect 11 0 1 1; #X connect 12 0 11 0; #X connect 13 0 7 1; #X connect 14 0 13 0; #X connect 15 0 20 0; #X connect 16 0 19 0; #X connect 17 0 10 0; #X connect 18 0 17 0; #X connect 19 0 18 0; #X connect 20 0 12 0; #X connect 21 0 6 0; #X connect 22 0 7 0; #X restore 467 393 pd shaper; #X obj 623 283 / -100; #X floatatom 696 442 5 0 256 0 - #0-depr #0-deps; #X floatatom 648 442 5 0 256 0 - #0-limr #0-lims; #X text 648 426 limit; #X text 696 427 depth; #X text 654 481 (scaled 0-256); #X text 344 268 input signal~; #X text 621 245 filter envelope~; #X text 646 464 shaper parameters; #X obj 465 511 dac~; #X obj 252 483 s \$0-limr; #X obj 321 483 s \$0-depr; #X msg 255 461 128; #X msg 322 459 128; #X obj 288 417 loadbang; #X obj 45 477 s \$0-sigfreq; #X obj 138 479 s \$0-downphasor; #X msg 138 458 50; #X msg 49 454 24; #X msg 554 277 0; #X obj 495 260 t a b; #X obj 467 310 tabosc4~ v.a.s.t; #X msg 468 211 40; #X msg 494 210 43; #X msg 524 210 35; #X msg 552 211 45; #X msg 585 212 47; #X obj 469 69 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 1 1; #X obj 470 125 i; #X obj 494 125 + 1; #X msg 617 213 50; #X obj 468 149 mod 24; #X obj 468 171 sel 0 3 5 6 9 12 15 17 20 21 23; #X obj 349 111 s \$0-limr; #X obj 349 42 avg~; #X obj 349 22 osc~ 0.02; #X obj 349 63 * 50; #X obj 349 86 + 50; #X obj 282 44 avg~; #X obj 282 113 s \$0-depr; #X obj 282 24 osc~ 0.1; #X obj 282 65 * 40; #X obj 282 90 + 60; #X obj 447 479 *~ 0.1; #X obj 490 479 *~ 0.1; #X msg 536 109 0; #X obj 536 84 sel 1; #X obj 469 101 metro 160; #X msg 561 109 0; #X obj 591 136 s \$0-volr; #X floatatom 546 403 5 0 100 0 - #0-volr -; #X obj 519 443 dbtorms; #X text 544 386 volume; #X msg 600 101 80; #X msg 531 35 \; pd dsp 1; #X text 440 68 play; #X obj 476 11 loadbang; #X connect 1 0 12 0; #X connect 2 0 8 0; #X connect 3 0 9 0; #X connect 4 0 3 0; #X connect 5 0 11 1; #X connect 6 0 7 0; #X connect 7 0 33 0; #X connect 8 0 10 0; #X connect 9 0 2 0; #X connect 11 0 55 0; #X connect 11 0 56 0; #X connect 12 0 5 0; #X connect 24 0 22 0; #X connect 25 0 23 0; #X connect 26 0 24 0; #X connect 26 0 25 0; #X connect 26 0 29 0; #X connect 26 0 30 0; #X connect 29 0 28 0; #X connect 30 0 27 0; #X connect 31 0 33 1; #X
[PD] creation of a random-line in Gem
here´s a patch for creating a line in Gem by ramdom-coordinates for x et y. it´s far away from perfect or something, but i am a beginner, so, please don´t laught :) I don´tknow if it will work just as an attachment, if not how would it be the best way to post to the community? thanks for your links and hints on fractals in Gem! I will ave a look at them the naxt days and maybe I will have success ;) another question: were can I find all the different libraries for Pd? when i load up pd, I get the message from some libraries: can´t load library. Cheers, Johannes -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer #N canvas 289 2 714 638 10; #X obj 46 186 gemwin; #X msg 244 103 1; #X msg 243 128 0; #X msg 114 73 create; #X msg 114 104 destroy; #X msg 205 103 bang; #X obj 205 73 t b b; #X msg 205 44 bang; #X obj 233 398 translateXYZ; #X obj 233 360 gemhead; #X obj 233 202 t b b b b; #X msg 303 143 1; #X msg 346 143 0; #X obj 84 302 world_light; #X obj 84 274 gemhead; #X text 78 34 click here to begin; #N canvas 95 194 302 191 Gem.init 0; #X obj 118 18 loadbang; #X msg 201 78 reset; #X obj 118 113 outlet; #X obj 118 45 t b b; #X msg 118 79 lighting 1; #X msg 22 77 buffer 1; #X connect 0 0 3 0; #X connect 1 0 2 0; #X connect 3 0 4 0; #X connect 3 0 5 0; #X connect 3 1 1 0; #X connect 4 0 2 0; #X connect 5 0 2 0; #X restore 8 119 pd Gem.init; #X obj 320 174 metro 0.001; #X obj 234 426 color 1 0 0; #X msg 419 90 0; #X msg 469 86 0; #X obj 233 454 sphere 0.02; #X obj 557 193 0; #X floatatom 479 482 5 0 0 0 - - -; #X obj 580 435 +; #X msg 600 318 0; #X msg 631 317 1; #X obj 533 435 0; #X msg 655 76 1; #X msg 624 75 0; #X floatatom 515 252 5 0 0 0 - - -; #X obj 601 193 +; #X obj 479 506 / 200; #X obj 515 276 / 200; #N canvas 133 39 525 453 random 0; #X floatatom 249 151 5 0 0 0 - - -; #X floatatom 266 292 5 0 0 0 - - -; #X obj 249 109 random 4; #X obj 245 186 select 0 1 2; #X msg 200 230 -0.5; #X msg 249 229 -2; #X msg 301 229 2; #X msg 352 229 0.5; #X obj 266 323 outlet; #X obj 289 15 loadbang; #X msg 345 15 1; #X msg 376 15 0; #X obj 289 68 metro 1000; #X connect 0 0 3 0; #X connect 1 0 8 0; #X connect 2 0 0 0; #X connect 3 0 4 0; #X connect 3 1 5 0; #X connect 3 2 6 0; #X connect 3 3 7 0; #X connect 4 0 1 0; #X connect 5 0 1 0; #X connect 6 0 1 0; #X connect 7 0 1 0; #X connect 9 0 12 0; #X connect 10 0 12 0; #X connect 11 0 12 0; #X connect 12 0 2 0; #X restore 614 151 pd random; #N canvas 133 39 513 441 random 0; #X floatatom 249 151 5 0 0 0 - - -; #X floatatom 266 292 5 0 0 0 - - -; #X obj 249 109 random 4; #X obj 245 186 select 0 1 2; #X msg 200 230 -0.5; #X msg 249 229 -2; #X msg 301 229 2; #X msg 352 229 0.5; #X obj 266 323 outlet; #X obj 289 15 loadbang; #X obj 289 68 metro 100; #X msg 345 15 1; #X msg 376 15 0; #X connect 0 0 3 0; #X connect 1 0 8 0; #X connect 2 0 0 0; #X connect 3 0 4 0; #X connect 3 1 5 0; #X connect 3 2 6 0; #X connect 3 3 7 0; #X connect 4 0 1 0; #X connect 5 0 1 0; #X connect 6 0 1 0; #X connect 7 0 1 0; #X connect 9 0 10 0; #X connect 10 0 2 0; #X connect 11 0 10 0; #X connect 12 0 10 0; #X restore 593 389 pd random; #X text 497 56 click here to random y-coordinates; #X text 500 299 click here to random x-coordinates; #X obj 594 361 metro 5; #X obj 614 122 metro 5; #X text 284 124 turn on/off the metro to draw the line; #X connect 1 0 0 0; #X connect 2 0 0 0; #X connect 3 0 0 0; #X connect 4 0 0 0; #X connect 5 0 0 0; #X connect 6 0 5 0; #X connect 6 1 1 0; #X connect 7 0 6 0; #X connect 7 0 19 0; #X connect 7 0 20 0; #X connect 8 0 18 0; #X connect 9 0 8 0; #X connect 10 0 9 0; #X connect 10 1 14 0; #X connect 10 2 23 0; #X connect 10 3 30 0; #X connect 11 0 17 0; #X connect 12 0 17 0; #X connect 14 0 13 0; #X connect 16 0 0 0; #X connect 17 0 10 0; #X connect 18 0 21 0; #X connect 19 0 27 1; #X connect 19 0 23 0; #X connect 20 0 22 1; #X connect 20 0 30 0; #X connect 22 0 31 0; #X connect 23 0 32 0; #X connect 24 0 23 0; #X connect 24 0 27 1; #X connect 25 0 38 0; #X connect 26 0 38 0; #X connect 27 0 24 0; #X connect 28 0 39 0; #X connect 29 0 39 0; #X connect 30 0 33 0; #X connect 31 0 30 0; #X connect 31 0 22 1; #X connect 32 0 8 1; #X connect 33 0 8 2; #X connect 34 0 31 1; #X connect 35 0 24 1; #X connect 38 0 27 0; #X connect 39 0 22 0; ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] [OT] gallery installation sound
Hello all, Apologies for the ot post; I've got my final thesis show coming up in early April and I'm doing all sound work using Pd. The gallery space I am using is actually quite poor for acoustics, as it's got a concrete floor and metal roofing. It's relatively small though - two hallways each about 10 feet by 30 feet large (3 by 9 meters if you like) making a T shape. I would like to do two 4 channel sound installations, perhaps one for each hallway. I know there are many sound scientists and artists on the list so I thought I would ask if anyone knows of resources to look at for dealing with these kinds of issues? How are other artists sorting these things out? Any links or recommendations would be very helpful. Low ends tend to get very muddy and the highs and mids spill all over the place. Are there certain tricks I could use in mixing or placement/kinds of speakers to preserve the highs and mids better in a difficult space? This might be a difficult question since you can't hear the piece in person, but even general advice would be very helpful. Also if any of you have documentation of your own installations, I would love to see them. Thanks! Kevin -- http://pocketkm.blogspot.com ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] puredatabase
On Wed, 7 Feb 2007 12:19:08 +0100 Steffen [EMAIL PROTECTED] wrote: I thought we (the potential users of the database) in this phase could brainstorm and discuss ideas on how we would like it. Good idea. One I thought of is to have a difficulty/level attribute. Some examples are too hard for complete beginners. It would be nice to browse all the level 1 help files and then move on to level 2 etc. Deciding what difficulty level is a bit arbitary, the author should probably do that initially. Probably 1 (beginner) to 5 (experienced) would be enough. ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
RE: [pd] shaper filter
When I run this, I get a inlet expected got float error?? (sorry no time to debug, going for 'instant gratification'). mcg -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Patco Sent: Wednesday, February 07, 2007 8:43 AM To: hard off; pd-list@iem.at Subject: Re: [pd] shaper filter hard off a écrit : .but for the moment here is the basic patch if u care. Excellent! It reminds me the sound of a famous song I don't remember the name, I tried to make the sequence of this song gimmick in the attached patch ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Live Apectrum Analyzer
That's gorgeous. It runs fast on the 550MHz machine here. Shame about the baudline_jack though, it just crashes, so the only input that works is /dev/audio On Wed, 7 Feb 2007 14:27:28 +0100 (CET) Erich Berger [EMAIL PROTECTED] wrote: hi, just got a link from a friend to this software spectrum analyzer: http://www.baudline.com/ best ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] [OT] gallery installation sound
On 2/7/07, Kevin McCoy [EMAIL PROTECTED] wrote: there are many sound scientists and artists on the list so I thought I would ask if anyone knows of resources to look at for dealing with these kinds of issues? How are other artists sorting these things out? Any links or recommendations would be very helpful. Low ends tend to get very muddy and the highs and mids spill all over the place. Are there certain tricks I could use in mixing or placement/kinds of speakers to preserve the highs and mids better in a difficult space? This might be a difficult question since you can't hear the piece in person, but even general advice would be very helpful. I'm no sound scientist, but wouldn't just some ordinary foam of the type people put in their music studios help? It sounds like you are having trouble with unwanted and weird reverberations, which the foam should lesson. Having performed music in such spaces (concrete and metal), I've got a pretty good idea of the kind of acoustic nightmare you are probably facing... ~David ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] [OT] gallery installation sound
I haven't done any sound installations, but in thinking about a particular space had some ideas for dealing with these acoustical issues. You could design the sound for the space, working with rather than against the acoustics. If possible, you could capture the impulse response of the space (perhaps in multiple locations), then as you work on the sound, use convolution to hear how it will sound in the space. I guess the degree to which you can adapt your piece depends on how far along you already are. Alternatively, you could acoustically treat the space using acoustic foam or rigid fiberglass. This page has tons of good info: http://www.ethanwiner.com/acoustics.html Ben Kevin McCoy wrote: Hello all, Apologies for the ot post; I've got my final thesis show coming up in early April and I'm doing all sound work using Pd. The gallery space I am using is actually quite poor for acoustics, as it's got a concrete floor and metal roofing. It's relatively small though - two hallways each about 10 feet by 30 feet large (3 by 9 meters if you like) making a T shape. I would like to do two 4 channel sound installations, perhaps one for each hallway. I know there are many sound scientists and artists on the list so I thought I would ask if anyone knows of resources to look at for dealing with these kinds of issues? How are other artists sorting these things out? Any links or recommendations would be very helpful. Low ends tend to get very muddy and the highs and mids spill all over the place. Are there certain tricks I could use in mixing or placement/kinds of speakers to preserve the highs and mids better in a difficult space? This might be a difficult question since you can't hear the piece in person, but even general advice would be very helpful. Also if any of you have documentation of your own installations, I would love to see them. Thanks! Kevin -- http://pocketkm.blogspot.com http://pocketkm.blogspot.com ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] popping from - and prepending to - a generic message
Hi all, Is there a reasonably stright-forward way in pd-proper (I mean, without externals) to do either of the following two things? 1) Removing the first element of a message (NOT necessarily a list) and returning the rest of the message 2) Prepending a symbol or number to a message But I mean: this must work with ANY message, without knowing its composition (whether it starts with a number or symbol, how many elements and of what type it has, etc.) For example, let's say I get a message which is [foo 1 2 3( Removing the first element should give me [1 2 3( But if the message is [1 foo 3 4 5 bar( it must give me [foo 3 4 5 bar( and so on. I will omit examples for the prepend thing :p Solving problem 1 would indeed allow solving problem 2 (not so stright forward though:) Not viceversa, as far as I can see. I came up with a rather tricky solution for (1) but it involves scripting (dynamically adding and connecting objects in a canvas by sending it messages) and I'm finding out that PD is quite buggy when you start using that sort of things. When trying to use it to solve problem 2, I ended up with a patch that makes pd crash (but it shouldn't). However, I'm still trying to isolate the bug before I submit it to the bug tracker. Furthermore, the solution to (1) alone works fine but generates some errors in the pd output (because I intentionally use unpack s and unpack f at the same time so that only one of them matches and produces output). Which by the way raises a secondary question: is there a way to turn off/on error reporting? Also I found an almost as tricky (and not elegant) solution to problem 2 alone, without scripting but which requieres the message not to exceed a fixed maximum length (number of elements). And it generates unpack mismatch error messages too. If anyone is interested I can share the mentioned patches, but first I was wondering if I am missing a much simpler solution. I know there are externals that do this sort of things, but I like doing things natively in pd whenever I can, and this is also a speculative curiosity. Thanks M. ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] [OT] gallery installation sound
If you can (and it's a big if), try to suspend your acoustic dampening panels above the heads of people. This will have a big effect on your reverb problems without disrupting the space in the hallway. I like the suggestions on this thread. very insightful Chuck ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] Dynamic generation of $0-including objects?
I'm trying to generate objects within a subpatch using [obj( messages, and I want those generated objects to have $0 as one of their arguments, e.g. [myobject $0]. Using [obj x y myobject $0( gives [myobject 0] (I know $0 is not for messages, just thought I'd give that a try), and of course [list append $0] to the object message just adds the interpreted $0 of the parent patch. I'd like to preserve the $0. Anyone know of a way to do it? ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Dynamic generation of $0-including objects?
Yes. Either use [f $0], or a [makefilename %s-%s] or [makesymbol %s-%s] with a [f $0] as argument. I think that [makesymbol] is supposed to be deprecated, but I prefer its behaviour to the one of [makefilename], and its name is clearer. -- Alexandre Quessy http://alexandre.quessy.net 2007/2/7, Luke Iannini (pd) [EMAIL PROTECTED]: I'm trying to generate objects within a subpatch using [obj( messages, and I want those generated objects to have $0 as one of their arguments, e.g. [myobject $0]. Using [obj x y myobject $0( gives [myobject 0] (I know $0 is not for messages, just thought I'd give that a try), and of course [list append $0] to the object message just adds the interpreted $0 of the parent patch. I'd like to preserve the $0. Anyone know of a way to do it? ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] puredatabase
On Feb 7, 2007, at 6:19 AM, Steffen wrote: On 07/02/2007, at 2.25, David Powers wrote: On 2/6/07, Steffen [EMAIL PROTECTED] wrote: And a suggestion: It might be good to debate here how the database should be designed to best do it job. Fx. would it be an idea to make a set of (not necessarily disjunkt/non-intersecting) categories/ labels objects/libs could fit in - like math, audio, control, graphic (inspired by http://puredata.info/dev/PdLibraries)? I mean, there must be a quite a few opinions on how the database could be organized in order to be of most use. It would be nice if things could be tagged with keywords, rather than categorized. That way, there's no need to think of every category or decide on all keywords in advance, people could add keywords to objects as they saw fit. I agree. That what i meant by 'not necessarily non-intersecting categories'. It might be a bad choice to use the word category like that - I'm sorry. But it was mostly meant as an example of an idea we could want in such database. Since I0 said: help with database-design [...] might be appreciated I thought we (the potential users of the database) in this phase could brainstorm and discuss ideas on how we would like it. I think this should be generated from the meta data in the help files. For PDDP, we plan on using the help files as the central location for meta data. .hc ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/ listinfo/pd-list ¡El pueblo unido jamás será vencido! ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] puredatabase
On Feb 8, 2007, at 5:05 AM, padawan12 wrote: On Wed, 7 Feb 2007 12:19:08 +0100 Steffen [EMAIL PROTECTED] wrote: I thought we (the potential users of the database) in this phase could brainstorm and discuss ideas on how we would like it. Good idea. One I thought of is to have a difficulty/level attribute. Some examples are too hard for complete beginners. It would be nice to browse all the level 1 help files and then move on to level 2 etc. Deciding what difficulty level is a bit arbitary, the author should probably do that initially. Probably 1 (beginner) to 5 (experienced) would be enough. That could be based on a vote on the website. .hc ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/ listinfo/pd-list Man has survived hitherto because he was too ignorant to know how to realize his wishes. Now that he can realize them, he must either change them, or perish.-William Carlos Williams ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [Pd] Playing a bitmap
So I'm using this now, and the problem I'm encountering is that I'd like to be able to control the frequency range of a picture without editing the picture itself. I'd like to find a way to have pix_pix2sig~, or some other object, read the image and render it to audio, but padding some number of samples with zeros, so high points in the picture aren't necessarily out of my hearing range. Would it work, perhaps, to give the cursor user-controllable height, up or down, and color it before adding the image? But if I'm not mistaken, rectangles cannot be textured to in any other way than right at the corners... Any suggestions? Thanks. -Chuckk On 1/27/07, Chuckk Hubbard [EMAIL PROTECTED] wrote: Well, here's where I have it now. I'm still working out how to scale everything correctly, so you'll have to adjust the size calculations and stuff according to the image. The metro object plays from left to right, or you can manually scroll with the y-input to the pix_crop object. I'm not sure of any of this. I wish I could get rid of the staircase effect; might just need more overlap. The scaling settings as it is are for the .jpg of the patch itself. The scaling settings exist because I have a separate rectangle for the cursor, and its crop and translate take different values to have it show the part of the image it is over depending on the width of the image, and I don't understand exactly how those values work. -Chuckk On 1/27/07, Kevin McCoy [EMAIL PROTECTED] wrote: When you get something workable, please post a patch. I've been following your conversation here with much interest. Thanks, Kevin -- Far and away the best prize that life has to offer is the chance to work hard at work worth doing. -Theodore Roosevelt #N canvas 0 0 320 263 12; #N canvas 517 158 717 714 gem 1; #X obj 229 611 outlet~; #X obj 347 612 outlet~; #X obj 36 78 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 1 1 ; #X obj 25 120 gemwin; #X msg 70 71 create; #X msg 70 96 destroy; #X obj 250 78 gemhead; #X obj 250 140 pix_image; #X msg 329 69 bang; #X obj 329 92 openpanel; #X msg 329 115 open \$1; #X obj 214 222 pix_info; #X obj 214 268 pix_texture; #X floatatom 252 245 5 0 0 0 - - -; #X floatatom 311 243 5 0 0 0 - - -; #X obj 214 310 rectangle 4 3; #X floatatom 421 173 5 0 0 0 - - -; #X floatatom 506 162 5 0 0 0 - - -; #X floatatom 599 267 5 0 0 0 - - -; #X msg 599 290 \$1 0 0; #X obj 438 398 pix_invert; #X obj 411 380 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0 1; #X obj 438 428 pix_pix2sig~; #X obj 467 522 tabsend~ frame; #X obj 352 511 /~ 16386; #X obj 352 536 rifft~; #N canvas 0 0 450 300 (subpatch) 0; #X array frame 4096 float 3; #A 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0.00392157 0 0 0.00392157 0.00784314 0.027451 0.00392157 0 0 0.0156863 0.0235294 0 0 0.0235294 0.00784314 0 0 0.0392157 0.027451 0 0 0 0.0196078 0 0.027451 0 0 0 0.00784314 0.0392157 0.0352941 0 0 0.0431373 0.00784314 0.00392157 0 0 0 0.0392157 0.0235294 0 0 0 0 0.027451 0 0.0196078 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0; #A 1000 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Re: [PD] Dynamic generation of $0-including objects?
On Wed, Feb 07, 2007 at 07:54:40PM -0700, Luke Iannini (pd) wrote: I'm trying to generate objects within a subpatch using [obj( messages, and I want those generated objects to have $0 as one of their arguments, e.g. [myobject $0]. Using [obj x y myobject $0( gives [myobject 0] (I know $0 is not for messages, just thought I'd give that a try), and of course [list append $0] to the object message just adds the interpreted $0 of the parent patch. I'd like to preserve the $0. Anyone know of a way to do it? Hi, I think the attached patch demonstrates what you mean. Best, Chris. --- [EMAIL PROTECTED] http://mccormick.cx #N canvas 9 30 445 139 10; #X obj 7 53 makefilename %s%d; #X msg 7 5 $ 0; #X obj 7 28 pack s f; #N canvas 0 0 450 300 result 1; #X restore 360 4 pd result; #X msg 7 76 \; pd-result obj 10 10 test \$1; #X connect 0 0 4 0; #X connect 1 0 2 0; #X connect 2 0 0 0; ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] popping from - and prepending to - a generic message
On Thu, Feb 08, 2007 at 02:25:56AM +0100, Matteo Sisti Sette wrote: Is there a reasonably stright-forward way in pd-proper (I mean, without externals) to do either of the following two things? 1) Removing the first element of a message (NOT necessarily a list) and returning the rest of the message 2) Prepending a symbol or number to a message It doesn't matter if it's a list or not, you can still use [list] to turn it into a list, do a pre-pending or pre-unpending and then use [list trim] to turn it back into a message. Best, Chris. --- [EMAIL PROTECTED] http://mccormick.cx ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] PD CHAT
On 5 Feb 2007, at 7:37 PM, Tim Boykett wrote: On the other side I was using some pdreceive (on a linux machine, now I use OSX and I cannot find it!) to take messages to find pdreceive on OSX open the Pd.app package -- it is in Contents/ Resources/bin/pdreceive - OSX aliases don't work pointing into a package but symlinks do and /PATH_TO_PD/Pd.app/Contents/Resources/bin/ pdreceive works fine in Terminal or a script. simon ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] graphical possibilities in GEM
Sounds good, but it doesnt' work for me. I get these errors on load: error: 1007-$2x: no such object error: 1007-$2y: no such object error: 1007-$2z: no such object .hc On Feb 7, 2007, at 3:28 AM, Patco wrote: Johannes Eckart a écrit : 3.)One specific question: is there any possibility to work with fractals or the formulas of them on Gem? maybe any patches exist already? any hint would be great for me!!! Hello, you might be interested by this attached patch for drawing strange attractors, Patco. #N canvas 448 7 516 364 10; #N canvas 0 0 494 344 gemwin 0; #X msg 262 153 0 \, destroy; #X text 294 108 - create GEM windows; #X obj 109 132 hsl 128 15 0 127 0 0 empty empty Camera_X -2 -6 0 8 -262144 -1 -1 0 1; #X obj 110 158 hsl 128 15 0 127 0 0 empty empty Camera_Y -2 -6 0 8 -262144 -1 -1 0 1; #X obj 109 184 hsl 128 15 0 500 0 0 empty empty Camera_Z -2 -6 0 8 -262144 -1 -1 0 1; #X text 188 86 camera position; #N canvas 0 0 462 312 ch_gemwin 0; #X obj 285 171 f; #X obj 206 152 spigot; #X obj 267 143 sel 0 1; #X obj 237 124 t f f; #X obj 206 200 -; #X obj 206 249 +; #X obj 267 213 f; #X obj 159 168 f; #X obj 80 149 spigot; #X obj 141 140 sel 0 1; #X obj 111 121 t f f; #X obj 80 200 -; #X obj 80 249 +; #X obj 141 210 f; #X obj 406 162 f; #X obj 327 146 spigot; #X obj 388 137 sel 0 1; #X obj 358 118 t f f; #X obj 327 197 -; #X obj 388 207 f; #X obj 80 465 * 4; #X obj 135 467 * 4; #X obj 156 308 t b f; #X obj 94 372 cos; #X obj 106 430 * 1; #X obj 80 430 * 1; #X obj 132 373 sin; #X obj 107 466 * 4; #X obj 94 394 t b f; #X obj 94 348 / 200; #X obj 80 491 pack f f f; #X obj 458 49 gemmouse; #X obj 515 135 t b f; #X obj 515 164 |; #X obj 487 240 gemhead; #X obj 491 193 loadbang; #X msg 487 215 0; #X obj 487 315 curve 2; #X obj 487 266 color 1 0 0; #X obj 571 240 gemhead; #X obj 571 315 curve 2; #X obj 651 242 gemhead; #X obj 651 317 curve 2; #X msg 524 289 3 0 0; #X msg 608 289 0 3 0; #X msg 688 291 0 0 3; #X msg 80 516 view \$1 \$2 \$3 0 0 0 0 1 0; #X obj 571 266 color 0 1 0; #X obj 651 268 color 0 0 1; #X obj 80 308 sin; #X obj 106 309 cos; #X obj 327 246 + 200; #X obj 157 282 / 50; #X obj 80 283 / -200; #X obj 18 12 inlet; #X obj 20 579 outlet; #X obj 60 14 inlet; #X obj 215 19 inlet; #X obj 132 15 inlet; #X obj 213 44 * 5; #X obj 59 82 / 127; #X obj 60 61 * 400; #X obj 131 82 / 127; #X obj 131 58 * 200; #X obj 131 36 * -3.14; #X obj 60 37 * 3.14; #X obj 21 551 gemwin 10; #X connect 0 0 4 1; #X connect 1 0 4 0; #X connect 2 0 6 0; #X connect 2 1 0 0; #X connect 3 0 1 1; #X connect 3 1 2 0; #X connect 4 0 5 0; #X connect 5 0 6 1; #X connect 5 0 29 0; #X connect 6 0 5 1; #X connect 7 0 11 1; #X connect 8 0 11 0; #X connect 9 0 13 0; #X connect 9 1 7 0; #X connect 10 0 8 1; #X connect 10 1 9 0; #X connect 11 0 12 0; #X connect 12 0 13 1; #X connect 12 0 53 0; #X connect 13 0 12 1; #X connect 14 0 18 1; #X connect 15 0 18 0; #X connect 16 0 19 0; #X connect 16 1 14 0; #X connect 17 0 15 1; #X connect 17 1 16 0; #X connect 18 0 51 0; #X connect 19 0 51 1; #X connect 20 0 30 0; #X connect 21 0 30 2; #X connect 22 0 21 0; #X connect 22 0 20 0; #X connect 22 0 27 0; #X connect 22 1 21 1; #X connect 22 1 20 1; #X connect 22 1 27 1; #X connect 23 0 28 0; #X connect 24 0 21 0; #X connect 25 0 20 0; #X connect 26 0 27 0; #X connect 27 0 30 1; #X connect 28 0 24 0; #X connect 28 0 25 0; #X connect 28 1 24 1; #X connect 28 1 25 1; #X connect 29 0 23 0; #X connect 29 0 26 0; #X connect 30 0 46 0; #X connect 31 0 8 0; #X connect 31 0 7 1; #X connect 31 1 1 0; #X connect 31 1 0 1; #X connect 31 1 14 1; #X connect 31 1 15 0; #X connect 31 2 3 0; #X connect 31 2 10 0; #X connect 31 2 33 0; #X connect 31 3 17 0; #X connect 31 3 32 0; #X connect 32 0 33 0; #X connect 32 1 33 1; #X connect 33 0 34 0; #X connect 33 0 39 0; #X connect 33 0 41 0; #X connect 34 0 38 0; #X connect 35 0 36 0; #X connect 35 0 43 0; #X connect 35 0 44 0; #X connect 35 0 45 0; #X connect 35 0 53 0; #X connect 35 0 51 0; #X connect 36 0 34 0; #X connect 36 0 39 0; #X connect 36 0 41 0; #X connect 38 0 37 0; #X connect 39 0 47 0; #X connect 41 0 48 0; #X connect 43 0 37 2; #X connect 44 0 40 2; #X connect 45 0 42 2; #X connect 46 0 66 0; #X connect 47 0 40 0; #X connect 48 0 42 0; #X connect 49 0 25 0; #X connect 50 0 24 0; #X connect 51 0 19 1; #X connect 51 0 52 0; #X connect 52 0 22 0; #X connect 53 0 49 0; #X connect 53 0 50 0; #X connect 54 0 66 0; #X connect 56 0 65 0; #X connect 57 0 59 0; #X connect 58 0 64 0; #X connect 59 0 52 0; #X connect 60 0 53 0; #X connect 61 0 60 0; #X connect 62 0 29 0; #X connect 63 0 62 0; #X connect 64 0 63 0; #X connect 65 0 61 0; #X connect 66 0 55 0; #X restore 144 244 pd ch_gemwin; #X obj 109 105 tgl 15 0 empty empty gemwin 17 7 0 10 -262144 -1 -1 0 1; #X obj 223 58 sel 0 1; #X msg 335 153 create \, 1; #X obj 193 106 tgl 15 0 empty empty light 17 7 0 10 -262144 -1 -1 0 1; #X msg 328 187 lighting \$1 \, color \$1 0 0; #X connect 0 0 6 0; #X connect 2 0 6 1; #X connect 3 0 6 2; #X connect 4 0 6 3; #X
Re: [PD] puredatabase
On Feb 6, 2007, at 8:25 PM, David Powers wrote: On 2/6/07, Steffen [EMAIL PROTECTED] wrote: And a suggestion: It might be good to debate here how the database should be designed to best do it job. Fx. would it be an idea to make a set of (not necessarily disjunkt/non-intersecting) categories/ labels objects/libs could fit in - like math, audio, control, graphic (inspired by http://puredata.info/dev/PdLibraries)? I mean, there must be a quite a few opinions on how the database could be organized in order to be of most use. It would be nice if things could be tagged with keywords, rather than categorized. That way, there's no need to think of every category or decide on all keywords in advance, people could add keywords to objects as they saw fit. Yeah, that's the idea. Though there isn't really a way to do a user- generated taxonomy, only a developer generated taxonomy. Really, it would be generated by who ever writes the help patches. .hc ~David ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/ listinfo/pd-list As we enjoy great advantages from inventions of others, we should be glad of an opportunity to serve others by any invention of ours; and this we should do freely and generously. - Benjamin Franklin ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] [OT] gallery installation sound
We went to the Kimmel Center last semester in acoustics class, and this is exactly what they do. They have a huge foil on top that they raise or lower depending on the size of the ensemble. Now, they also have huge empty wells on both sides of the auditorium, and if they need wider reverb they open these huge walls in the auditorium so the sound can go all around- but I'm guessing that's beyond your means. I also like the impulse response idea, if nothing else you can learn from doing it. The only thing I can add is that if you try delaying the sound at one end of the room, you can make people feel like the sound is coming from the other end; then, maybe, they'll move towards that end and get more direct sound. -Chuckk On 2/7/07, Charles Henry [EMAIL PROTECTED] wrote: If you can (and it's a big if), try to suspend your acoustic dampening panels above the heads of people. This will have a big effect on your reverb problems without disrupting the space in the hallway. I like the suggestions on this thread. very insightful Chuck ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list -- Far and away the best prize that life has to offer is the chance to work hard at work worth doing. -Theodore Roosevelt ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Dynamic generation of $0-including objects?
Hahaha : ). It was generating odd messages here, like [test $-7614554]. But I'm on an intel mac using Pd-Extended autobuilds, so that's probably normal. Yes, I think a character escaping mechanism would be a good thing, though of course escaping is already used in the pd-fileformat so who knows what madness it would require. Thanks again! On 2/8/07, Chris McCormick [EMAIL PROTECTED] wrote: On Thu, Feb 08, 2007 at 12:16:02AM -0700, Luke Iannini (pd) wrote: Hm... I'm not sure if your patch was supposed to work or demonstrate my issue, Chris... thanks for making it regardless : ). It was supposed to solve your problem. Thanks to both of yas! Should probably add this to puredata.org or something for posterity. Or a bug report since it's obviously a kludge. If you consider it a kludge, then most of Pd is a kludge. ;) I don't think it's that bad, or at least no worse than any of the other dynamic patching stuff. Maybe slightly better would be a character escaping mechanism like [\$0( Best, Chris. --- [EMAIL PROTECTED] http://mccormick.cx ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
