Pd-list August 2007

pd-list@lists.iem.at

117 participants
152 discussions

Re: [PD] Newbie having problems with Pduino
by Alex Lucas 12 Aug '07

12 Aug '07

Hi Marius, Thanks very much for the file it worked straight away! I'll have to put you on my Christmas card list. Thanks Alex

1 0

Re: [PD] Newbie having problems with Pduino
by Alex Lucas 12 Aug '07

12 Aug '07

I've been reading about the implications of the Diecimila's Automatic (Software) Reset feature here; http://www.arduino.cc/en/Main/ArduinoBoardDiecimila it says "If a sketch running on the board receives one-time configuration or other data when it first starts, make sure that the software with which it communicates waits a second after opening the connection and before sending this data" would this apply to Pd? Thanks Alex

2 1

Newbie having problems with Pduino
by Alex Lucas 12 Aug '07

12 Aug '07

Hi All, I've uploaded the Pd_Firmware 1.32 to a new Arduino Diecimila board. I've been trying to get the board to communicate with Pd 0.39.3-extended-rc5 on Ubuntu Studio but unfortunately haven't had any joy. Pd will recognise the ttyUSB0 device file and the RX light on the board will flash when "pulse all outputs" is selected within arduino-test.pd, although the mounted LED on pin 13 doesn't respond. It seems that the analogue inputs aren't working either. It's probably something I've overlooked but If anyone has any suggestions it would be great to hear from you. Thanks Alex

1 0

[PD-announce] Dorkbot Mtl @ PureData Convention 07
by Martin Renaud 12 Aug '07

12 Aug '07

(Traduction française à la suite) Dorkbot-MTL makes an open invitation to anyone attending or involved with *L'Œuvre ouverte | PureData Convention 07* to present work, ideas, work in progress to others interested in creative uses of electricity, in a relaxed, open show-and-tell setting at our upcoming PD themed Dorkbot- MTL 4. If you would like to present your work, contact us at: dorkbotmtl(a)dorkbot.org Location: SAT, 1195 boul. Saint-Laurent Date: Saturday August 25th Time: 3pm-5pm More info, FAQ, at: http://www.dorkbot.org/dorkbotmtl/ --- Dorkbot-MTL invite quiconque participant ou assistant à *L'Œuvre ouverte | Congrès PureData 07,* à présenter et expliquer son travail ou ses idées, à d'autres personnes intéressées à l'utilisation créative de l'électricité, dans une atmosphère décontractée. Cette édition de Dorkbot sera consacrée à PureData. Si vous voulez présenter votre travail, contactez-nous à : dorkbotmtl(a)dorkbot.org Lieu: SAT, 1195 boul. Saint-Laurent Date: Saturday August 25th Heure: 15h -17h Plus d'information, FAQ, à : http://www.dorkbot.org/dorkbotmtl/ Martin Renaud Responsable des communications L'Œuvre ouverte | Congrès PureData Convention 07 www.pure-data.ca Tél. : (514)796-4770 Courriel : com.pd(a)artengine.ca _______________________________________________ PD-announce mailing list PD-announce(a)iem.at http://lists.puredata.info/listinfo/pd-announce

1 0

Re: [PD] writesf~ question
by David F. Place 11 Aug '07

11 Aug '07

On Aug 11, 2007, at 3:23 PM, pd-list-request(a)iem.at wrote: > > For now you could also schedule a "stop" message to [writesf~] with a > [delay <maxlength>] object that's bang'd whenever you "start" > recording. > > Wrap this it into an abstraction and you should have your feature > request fulfilled. Thanks. That's what I'll do. Also, the control to "stop" the recording must also send a stop to cancel the delay. Failing to do so could lead to some very hard to debug behavior. ___________________ (---o-------o-o-o---o-o-o----( David F. Place mailto:d@vidplace.com

2 2

PolyPoly - tricky to modify
by Phil Stone 11 Aug '07

11 Aug '07

I have been using Frank B.'s wonderful abstraction [polypoly] (which is a revision and improvement of [nqpoly]) and getting great results with it. In fact, I'll publish a synth based on it very soon now -- just as soon as I work out this final issue. I added an extra inlet to [polypoly] in order to be able to send a "clear" message to the [poly] object within it, which manages all the dynamically-created voices. I did this because imperfect input can sometimes drop a note-off and leave a note hanging, and it never gets de-allocated or released by [poly] -- that's what the "clear" message accomplishes. This actually worked great, with one small problem -- the $0-poly subpatch, which is where the magic of [polypoly] mostly seems to occur, doesn't respond well to editing of its parent. There's dynamic instantiation using $0- variables going on here, and I think that's what is getting messed up by editing -- these extra lines appear in the edited version: #X obj 50 60 r 1002-in1; #X obj 199 60 r 1002-in2; #X obj 50 200 throw~ 1002-out0; #X obj 199 200 throw~ 1002-out1; and the subpatch invocation is this: #N canvas 7 455 362 318 1002-poly 0; (edited) instead of: #N canvas 7 455 362 318 \$0-poly 0; (original) These cause startup errors, although after that, everything seems to work fine. I'm not sure how to correctly edit self-modifying patches such as this. What's the trick? Should I just edit the text directly? I've attached the modified version of [polypoly]. By the way, Frank, will [polypoly] be made available from CVS? I think it's the best thing since sliced bread. Phil Stone UC Davis

2 4

writesf~ question
by David F. Place 11 Aug '07

11 Aug '07

Hello: This seems like it must be a FAQ, but I have not been able to find the answer searching the archives. What is the behavior of writesf~ if you accidentally forget to turn it off? Will it eat up all the disk space on your computer and crash the system? Is there a way to tell it to quit if a file exceeds a maximum size? Thanks. Cheers, David ___________________ (---o-------o-o-o---o-o-o----( David F. Place mailto:d@vidplace.com

4 6

PolyPoly - tricky to modify
by Phil Stone 10 Aug '07

10 Aug '07

(This time, attachment is *really* attached - sorry!) I have been using Frank B.'s wonderful abstraction [polypoly] (which is a revision and improvement of [nqpoly]) and getting great results with it. In fact, I'll publish a synth based on it very soon now -- just as soon as I work out this final issue. I added an extra inlet to [polypoly] in order to be able to send a "clear" message to the [poly] object within it, which manages all the dynamically-created voices. I did this because imperfect input can sometimes drop a note-off and leave a note hanging, and it never gets de-allocated or released by [poly] -- that's what the "clear" message accomplishes. This actually worked great, with one small problem -- the $0-poly subpatch, which is where the magic of [polypoly] mostly seems to occur, doesn't respond well to editing of its parent. There's dynamic instantiation using $0- variables going on here, and I think that's what is getting messed up by editing -- these extra lines appear in the edited version: #X obj 50 60 r 1002-in1; #X obj 199 60 r 1002-in2; #X obj 50 200 throw~ 1002-out0; #X obj 199 200 throw~ 1002-out1; and the subpatch invocation is this: #N canvas 7 455 362 318 1002-poly 0; (edited) instead of: #N canvas 7 455 362 318 \$0-poly 0; (original) These cause startup errors, although after that, everything seems to work fine. I'm not sure how to correctly edit self-modifying patches such as this. What's the trick? Should I just edit the text directly? I've attached the modified version of [polypoly]. By the way, Frank, will [polypoly] be made available from CVS? I think it's the best thing since sliced bread. Phil Stone UC Davis #N canvas 211 82 943 658 10; #X obj 36 31 inlet; #X obj 292 200 moses 1; #X text 567 49 your abstraction is ultimately called with the parameters: <index> <number of objects> <arg1> <arg2> <arg3> <arg4>; #N canvas 7 455 362 318 1002-poly 0; #X obj 50 60 r 1002-in1; #X obj 199 60 r 1002-in2; #X obj 50 200 throw~ 1002-out0; #X obj 199 200 throw~ 1002-out1; #X restore 36 254 pd \$0-poly; #X obj 36 227 s \$0-in1; #N canvas 220 112 751 428 init 0; #X obj 197 139 symbol \$0-poly; #X obj 197 163 makefilename pd-%s; #X obj 197 187 pack s \$0; #X msg 204 118 bang; #X text 154 317 This will clear the subpatch and create fake "in/outlets" as senders and receivers.; #X obj 103 206 s \$0-subname; #X obj 197 92 b; #X obj 197 69 r \$0-init; #X msg 197 230 \; \$1 clear \; \$1 obj 50 60 r \$2-in1 \; \$1 obj 199 60 r \$2-in2 \; \$1 obj 50 200 throw~ \$2-out0 \; \$1 obj 199 200 throw~ \$2-out1 \;; #X connect 0 0 1 0; #X connect 1 0 2 0; #X connect 1 0 5 0; #X connect 2 0 8 0; #X connect 3 0 0 0; #X connect 6 0 0 0; #X connect 7 0 6 0; #X restore 343 108 pd init; #X obj 139 31 inlet; #X obj 256 63 loadbang; #X obj 256 108 f \$1; #N canvas 0 22 692 559 last-two 0; #X obj 153 175 cnv 15 150 80 empty empty empty 20 12 0 14 -233017 -66577 0; #X text 378 110 first reset (b) \, then set new length (f).; #X text 311 195 Right outlet is responsible to first fill the list ; #X text 312 211 Left outlet then only lets the smaller list pass.; #X obj 180 183 list; #X obj 228 113 inlet; #X obj 180 149 inlet; #X obj 180 302 outlet; #X obj 180 228 list split 2; #X obj 228 149 b; #X connect 4 0 8 0; #X connect 5 0 9 0; #X connect 6 0 4 0; #X connect 8 0 4 1; #X connect 8 0 7 0; #X connect 8 2 4 1; #X connect 9 0 4 1; #X restore 386 521 pd last-two; #X obj 386 562 list prepend; #X msg 386 589 \; \$1 connect \$3 0 \$2 0 \;; #X obj 434 359 r \$0-subname; #X obj 465 541 r \$0-subname; #N canvas 183 178 858 457 finish 0; #X obj 121 185 until; #X obj 156 212 + 1; #X obj 121 284 list prepend; #X obj 121 162 t a b; #X obj 200 255 r \$0-subname; #X obj 452 126 r \$0-subname; #X obj 77 31 inlet; #X obj 77 67 moses 1; #X text 412 238 Connect [r \$0-in1] to first object's first inlet; #X obj 168 185 4; #X obj 121 211 f 4; #X text 167 163 first 4 objects are xlets; #X msg 415 196 \; \$1 connect 0 0 4 0 \;; #X msg 121 318 \; \$1 connect 1 0 \$2 1 \; \$1 connect \$2 1 2 0 \; \$1 connect \$2 2 3 0 \;; #X obj 415 165 symbol; #X obj 121 98 t a b; #X text 276 344 Connect all wrapper's middle signal outlet to [s~ \$0-out0] ; #X text 276 330 Connect all wrapper's right inlet to [r \$0-in2]; #X text 276 359 Connect all wrapper's left signal outlet to [s~ \$0-out1] ; #X connect 0 0 10 0; #X connect 1 0 10 1; #X connect 2 0 13 0; #X connect 3 0 0 0; #X connect 3 1 9 0; #X connect 4 0 2 1; #X connect 5 0 14 1; #X connect 6 0 7 0; #X connect 7 1 15 0; #X connect 9 0 10 1; #X connect 10 0 1 0; #X connect 10 0 2 0; #X connect 14 0 12 0; #X connect 15 0 3 0; #X connect 15 1 14 0; #X restore 274 260 pd finish; #X text 612 116 based on: nqpoly (v4) - pix.test.at; #X obj 343 135 s \$0-init; #X obj 458 494 r \$0-init; #X text 612 140 changes: fbar at footils.org 2006; #X obj 408 390 pack f s s f; #X msg 408 444 \; \$2 obj 50 100 polypoly-wrap \$3 \$1 \$4 \$5 \$6 \$7 \$8 \;; #X obj 256 135 t b a a a b; #X obj 386 273 t a a b; #X obj 395 31 inlet; #X obj 36 167 pack 0 0 0; #X obj 36 140 - 1; #X obj 36 344 outlet~; #X obj 460 332 symbol \$3; #X obj 408 417 list append \$4 \$5 \$6 \$7; #X obj 386 494 + 4; #X obj 139 344 outlet~; #X obj 36 287 catch~ \$0-out0; #X obj 139 287 catch~ \$0-out1; #X text 567 12 usage: polypoly <number of objects> <voice stealing: 0/1> <abstraction name> <up to 4 creation args>; #X obj 36 113 poly \$1 \$2; #N canvas 0 22 382 282 loadbang 0; #X obj 130 64 inlet; #X obj 130 86 b; #X msg 130 141 \; \$1 loadbang; #X obj 167 86 r \$0-subname; #X obj 130 113 symbol; #X connect 0 0 1 0; #X connect 1 0 4 0; #X connect 3 0 4 1; #X connect 4 0 2 0; #X restore 256 287 pd loadbang; #X obj 139 227 s \$0-in2; #X obj 395 58 unpack f s; #N canvas 0 22 227 234 countto 0; #X obj 60 97 until; #X obj 95 124 + 1; #X obj 60 124 f; #X obj 107 97 0; #X obj 60 77 t a b; #X obj 60 54 inlet; #X obj 60 145 outlet; #X connect 0 0 2 0; #X connect 1 0 2 1; #X connect 2 0 1 0; #X connect 2 0 6 0; #X connect 3 0 2 1; #X connect 4 0 0 0; #X connect 4 1 3 0; #X connect 5 0 4 0; #X restore 386 246 pd countto; #X obj 487 216 f; #X obj 476 33 inlet; #X msg 476 57 clear; #X connect 0 0 34 0; #X connect 1 1 38 0; #X connect 6 0 36 0; #X connect 7 0 8 0; #X connect 8 0 21 0; #X connect 9 0 10 0; #X connect 10 0 11 0; #X connect 12 0 19 1; #X connect 13 0 10 1; #X connect 17 0 9 1; #X connect 19 0 28 0; #X connect 21 0 35 0; #X connect 21 1 14 0; #X connect 21 2 1 0; #X connect 21 3 39 0; #X connect 21 4 16 0; #X connect 22 0 29 0; #X connect 22 1 19 0; #X connect 22 2 27 0; #X connect 23 0 37 0; #X connect 24 0 4 0; #X connect 25 0 24 0; #X connect 27 0 19 2; #X connect 28 0 20 0; #X connect 29 0 9 0; #X connect 31 0 26 0; #X connect 32 0 30 0; #X connect 34 0 25 0; #X connect 34 1 24 1; #X connect 34 2 24 2; #X connect 37 0 8 0; #X connect 37 1 27 0; #X connect 38 0 22 0; #X connect 39 0 19 3; #X connect 40 0 41 0; #X connect 41 0 34 0;

1 0

[Pd] toxy, cyclone on 64-bit
by Chuckk Hubbard 10 Aug '07

10 Aug '07

Does anyone know if these libraries will compile on 64-bit Linux? If so... how do I compile them? Thanks! -Chuckk -- http://www.badmuthahubbard.com

3 8

text editor on osx
by marius schebella 10 Aug '07

10 Aug '07

hi, I wonder if anyone else has the same problem? when I select some text and press apple+'t' I don't get the text editor, but the font bomb tool. that happens with pd-extended-39.3-rc5 on intel mac. I am having no problems with pd 0.40. and also not with the old pd-extended versions (rc2). marius.

4 8

← Newer
1
...
8
9
10
11
12
13
14
15
16
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

Pd-list August 2007