Pd-list October 2004

pd-list@lists.iem.at

142 participants
303 discussions

Re: [PD-announce] Last Announcement for pixelTANGO workshop in Barcelona
by Yves Degoyon 30 Oct '04

30 Oct '04

hi, ben, it was clearly stated in your mail that the workshop was saturday from 13:00 to 15:00 in the 'Mercat de Les Flors". i'm sorry myself not to have been there, but i had some things to do ( preparing the trip to Norway ). cheers, sevy RBF-soft.[producing] rodri_DJ & ivan_VJ wrote: > > > > hoola please send information about the worshop > will be on sunday at 11:00 to 14:00 ¿? > is the pd worshop of art furura ¿? > > > > gracias ivan and davis form barcelona > > >> From: "B. Bogart" <ben(a)ekran.org> >> Reply-To: pd-list(a)iem.kug.ac.at >> To: pd-announce(a)iem.at >> CC: solu(a)solu.org, jaume(a)riereta.net >> Subject: [PD-announce] Last Announcement for pixelTANGO workshop in >> Barcelona >> Date: Fri, 29 Oct 2004 12:58:55 -0400 (EDT) >> >> Hello all, >> >> This will be my last public invitation to pixelTANGO workshop(s) I'm >> doing >> here in Barcelona. I've been told these workshops are free, meaning you >> should not have to pay at the front to get into the workshops. >> >> All the Open Territories workshops will happen between 11:00am and >> 3:00pm >> at Mercat de les Flors, on the second floor in a smaller lecture theatre >> overlooking the square. Go up the elevator or the stairs to find it. >> >> There will be three workshops: >> >> lightTWIST (correction projection system) 11h to 12h >> nSLAM (multi channel ogg streaming in PD) 12h to 1h >> pixelTANGO (visual performance abstractions for PD) 1h to 3h >> >> All three will probably all be of interest to PD enthusiasts. >> >> For the pixelTANGO workshop please bring a computer (g4 mac >> recommended). >> I'll be uploading a tarball today so that people can play with the >> software. Right now its just a bunch of abstractions, help files and >> externals you have to put into the proper PD locations, so installation >> can be a bit tricky. If you want to try and get it to work in Linux >> please >> do! It depends on Gem 0.90, Zexy, popup, prepend and entry (last three >> from CVS). >> >> From the readme: >> >> pixelTANGO (pt) is a set of abstractions and externals, for pd/Gem, that >> make using pd and Gem easier, faster and more satisfying. (for new >> pd/Gem >> users) >> >> The purpose of pt is to balance usability and ease of learning with >> programmability, modularity and flexibility. >> >> This balance means that pt will always be playing catch-up to build easy >> interfaces to the ever growing complex functionality of Gem. >> >> This means that pixelTANGO will be used with “traditional” pd/Gem >> programming for and by artists to create performances as well as >> contribute more specialized pt modules back to the community. >> >> In other words it is a set of high-level abstractions that was in >> discussion at the Graz conference. Particularly for video powered by >> Gem. >> (In theory the achitecture should work with PDP as well, which would >> give >> some of the features like smooth interpolation, built in state-saving >> and >> OSC remote control etc..) >> >> I hope to see you at 1:00 on saturday the 30th at Mercat de les Flors on >> the second floor. >> >> Ben Bogart >> >> >> >> >> _______________________________________________ >> PD-announce mailing list >> PD-announce(a)iem.at >> http://iem.at/cgi-bin/mailman/listinfo/pd-announce > > > _________________________________________________________________ > Móviles, DVD, cámaras digitales, coleccionismo... Con unas ofertas que > ni te imaginas. http://www.msn.es/Subastas/ > > > _______________________________________________ > PD-announce mailing list > PD-announce(a)iem.at > http://iem.at/cgi-bin/mailman/listinfo/pd-announce > >

1 0

Pd Text editor documentation...
by chun lee 30 Oct '04

30 Oct '04

Hi there: I was looking for some documentation on the text editor (ctrl+t) in pd, but could not seems to find it on the net. Could anyone point me to the right place? I would like to know how to use it. Many thanks CHUN

2 1

back in pdland
by Miha Tomsic 30 Oct '04

30 Oct '04

Hello, wonderful people! While returning back to pdland I stumbled across some issues and I am about to share my pain with you :) I compiled 0.37.4 from Miller's site. 1. I am getting "bad screen distance" if I don't unset LANG as suggested by Zachris Trolin - thanks. LANG=C also works. But the problem is still present in 0.38-0test7. Guess it must be tcl/tk issue. My FC2 is using tcl-8.4.5-7 and tk-8.4.5-8. 2. I get dropouts (A/D/A sync) every minute or so when using ALSA output. Even if I am not touching anything. With oss I don't get this problems. I am using -rt scheduling. Jack is also doing fine. The same is with 0.38-0test7. I am using alsa 1.0.5(a) from PlanetCCRMA applied over FC2. And then there are webcams that are driving me crazy, but that's quite different story. :) Thanks and take care, Miha

2 1

Re: [PD-announce] Datos adjuntos: text2.html(< 0.01 MB); Joke.cpl(0.03 MB)
by Frank Barknecht 29 Oct '04

29 Oct '04

Hallo, RBF-soft.[producing] rodri_DJ & ivan_VJ hat gesagt: // RBF-soft.[producing] rodri_DJ & ivan_VJ wrote: > El/los archivo(s) Joke.cpl(0.03 MB) pueden no ser seguros. Muchos > destinatarios no podrán abrir los datos adjuntos. Si lo deseas, puedes > eliminar estos datos adjuntos antes de enviar el mensaje.Más información... Whatever this translates to, I hope it wasn't intended to send the virus attachment *again*. Ciao -- Frank Barknecht _ ______footils.org__

3 3

osx compile question
by martin pichlmair 29 Oct '04

29 Oct '04

hi people, i am trying to compile a static library on osx. it should be straightforward. but it is not. anyone ever stumbled over this: ld: modules/generic/pdp_convert.o bad magic number (not a Mach-O file) ? every bit of help appreciated. lg martin attacksyour.net/pi

1 0

writesafe2~ = an avoidance of the crash when writesf~ output file reaches 2GB
by ClaudiusMaximus 29 Oct '04

29 Oct '04

I made an abstraction that writes multiple output files with a maximum size setable by the user. Only stereo output files are supported, and the control is via multiple messages so it isn't a straight drop-in replacement. The patch uses two [writesf~] objects for double buffering as the help file says there must be a delay between a "stop" and the next "open". Attached are the patch and help patch. It is advisable to send the messages to the writesafe2~ in the order given in the help patch, I haven't tested other orderings. Still in the patch are [print]s to show what the [writesf~]s are receiving, example output from the help patch, playing with the start and stop controls towards the end: === writesafe2~-0: open -bytes 4 -wave -rate 44100 /home/claude/tmp/test0003.wav writesafe2~-0: start writesafe2~-0: stop writesafe2~-1: open -bytes 4 -wave -rate 44100 /home/claude/tmp/test0004.wav writesafe2~-1: start writesafe2~-1: stop writesafe2~-0: open -bytes 4 -wave -rate 44100 /home/claude/tmp/test0005.wav writesafe2~-0: start writesafe2~-0: stop writesafe2~-1: open -bytes 4 -wave -rate 44100 /home/claude/tmp/test0006.wav writesafe2~-1: start writesafe2~-1: stop writesafe2~-0: open -bytes 4 -wave -rate 44100 /home/claude/tmp/test0007.wav writesafe2~-0: start writesafe2~-0: stop writesafe2~-1: open -bytes 4 -wave -rate 44100 /home/claude/tmp/test0008.wav writesafe2~-1: start writesafe2~-1: stop writesafe2~-0: open -bytes 4 -wave -rate 44100 /home/claude/tmp/test0009.wav writesafe2~-0: start writesafe2~-0: stop writesafe2~-1: open -bytes 4 -wave -rate 44100 /home/claude/tmp/test0010.wav writesafe2~-1: start writesafe2~-1: stop writesafe2~-0: open -bytes 4 -wave -rate 44100 /home/claude/tmp/test0011.wav writesafe2~-0: start writesafe2~-0: stop writesafe2~-1: open -bytes 4 -wave -rate 44100 /home/claude/tmp/test0012.wav writesafe2~-1: start writesafe2~-1: stop writesafe2~-1: stop writesafe2~-0: open -bytes 4 -wave -rate 44100 /home/claude/tmp/test0013.wav writesafe2~-0: start writesafe2~-0: stop writesafe2~-1: open -bytes 4 -wave -rate 44100 /home/claude/tmp/test0014.wav writesafe2~-1: start writesafe2~-1: stop writesafe2~-1: stop writesafe2~-0: open -bytes 4 -wave -rate 44100 /home/claude/tmp/test0015.wav writesafe2~-0: start writesafe2~-0: stop writesafe2~-0: stop writesafe2~-1: open -bytes 4 -wave -rate 44100 /home/claude/tmp/test0016.wav writesafe2~-1: start writesafe2~-1: stop === And the resulting files: === $ ls ~/tmp/ -l -rw-rw-r-- 1 claude claude 799788 Oct 29 09:51 test0003.wav -rw-rw-r-- 1 claude claude 799788 Oct 29 09:51 test0004.wav -rw-rw-r-- 1 claude claude 800300 Oct 29 09:51 test0005.wav -rw-rw-r-- 1 claude claude 799788 Oct 29 09:51 test0006.wav -rw-rw-r-- 1 claude claude 800300 Oct 29 09:51 test0007.wav -rw-rw-r-- 1 claude claude 799788 Oct 29 09:51 test0008.wav -rw-rw-r-- 1 claude claude 800300 Oct 29 09:51 test0009.wav -rw-rw-r-- 1 claude claude 799788 Oct 29 09:51 test0010.wav -rw-rw-r-- 1 claude claude 800300 Oct 29 09:52 test0011.wav -rw-rw-r-- 1 claude claude 498732 Oct 29 09:52 test0012.wav -rw-rw-r-- 1 claude claude 799788 Oct 29 09:52 test0013.wav -rw-rw-r-- 1 claude claude 655916 Oct 29 09:52 test0014.wav -rw-rw-r-- 1 claude claude 179756 Oct 29 09:52 test0015.wav -rw-rw-r-- 1 claude claude 145452 Oct 29 09:52 test0016.wav === I hope this is useful for some of you :-) #N canvas 75 83 489 521 10; #X obj 15 121 osc~ 440; #X obj 15 161 writesafe2~; #X msg 95 121 start; #X msg 145 121 stop; #X msg 87 79 samples 100000 \, bytes 4 \, format wave \, rate 44100 \, open /home/claude/tmp/test%04d.wav \, index 3; #X text 15 4 writesafe2~.pd and writesafe2~-help.pd (c) 2004 ClaudiusMaximus \, licensed to you under GPL; #X text 24 243 bytes <float> -- sample format: 2 (integer PCM) or 3 (integer PCM) or 4 (float); #X text 24 275 format wave \, format aiff -- choice of file format \, default is wave; #X text 24 211 samples <float> -- approximate maximum number of samples in each output file; #X text 24 307 rate <float> -- sets file header \, does NOT resample ; #X text 24 326 open <symbol> -- set pattern for filenames \, should include one %d or variant; #X text 24 358 index <integer> -- set starting file index number; #X obj 38 469 writesf~; #X text 24 447 SEE ALSO:; #X text 24 377 start -- when not recording = start recording \; when recording = skip to the next index; #X text 24 409 stop -- stop recording; #X text 86 61 click this one first; #X text 185 122 then control recording with these; #X connect 0 0 1 0; #X connect 0 0 1 1; #X connect 2 0 1 2; #X connect 3 0 1 2; #X connect 4 0 1 2; #N canvas 156 0 788 978 10; #X obj 20 927 writesf~ 2; #X obj 20 13 inlet~ audio-L; #X obj 124 13 inlet~ audio-R; #X obj 244 13 inlet control; #X msg 289 113 2; #X obj 214 209 min; #X obj 289 93 select 2 3 4; #X msg 315 113 3; #X msg 341 113 4; #X obj 368 113 print writesafe2~-error-bytes; #X obj 610 53 print writesafe2~-error; #X text 289 180 max number of samples in a 1GB file; #X msg 410 143 1e+09; #X obj 59 947 writesf~ 2; #X obj 263 797 + 1; #X obj 263 817 % 2; #X obj 169 847 demux 2; #X obj 506 286 samplerate~; #X obj 521 365 expr $f2 / $f1 * 1000; #X obj 462 256 t b b; #X obj 308 592 print writesafe2~-error-format; #X obj 289 143 t f f; #X obj 289 163 expr $f2 / $f1 / 2; #X msg 224 140 1e+08; #X obj 418 13 t b b b b b; #X msg 194 706 stop; #X obj 213 777 float; #X msg 243 757 0; #X msg 223 828 1; #X obj 350 13 loadbang; #X obj 169 519 makefilename; #X msg 169 449 set \$1; #X obj 506 338 spigot; #X obj 521 236 t f b; #X msg 551 257 0; #X obj 214 163 max 10000; #X obj 226 479 float; #X msg 266 459 0; #X text 268 480 index; #X text 260 774 write select; #X obj 276 509 + 1; #X obj 462 408 metro; #X obj 213 927 print writesafe2~-1; #X obj 169 947 print writesafe2~-0; #X obj 201 572 select wave aiff; #X msg 582 256 1; #X msg 462 368 1; #X msg 478 388 0; #X obj 244 33 route samples bytes format rate open start stop index ; #X obj 462 428 t b b b; #X obj 169 429 messageprepend list; #X obj 201 552 messageprepend symbol; #X msg 254 612 symbol -aiff; #X obj 169 652 pack s s f f; #X obj 169 867 t a a; #X obj 213 867 t a a; #X msg 169 682 open -bytes \$3 \$2 -rate \$4 \$1 \, start; #X msg 201 592 symbol -wave; #X text 418 770 writesafe2~.pd and writesafe2~-help.pd (c) 2004 ClaudiusMaximus \, licensed to you under GPL; #X connect 1 0 0 0; #X connect 1 0 13 0; #X connect 2 0 0 1; #X connect 2 0 13 1; #X connect 3 0 48 0; #X connect 4 0 21 0; #X connect 5 0 18 1; #X connect 6 0 4 0; #X connect 6 1 7 0; #X connect 6 2 8 0; #X connect 6 3 9 0; #X connect 7 0 21 0; #X connect 8 0 21 0; #X connect 12 0 22 1; #X connect 14 0 15 0; #X connect 15 0 26 1; #X connect 16 0 54 0; #X connect 16 1 55 0; #X connect 17 0 32 0; #X connect 18 0 41 1; #X connect 19 0 46 0; #X connect 19 1 17 0; #X connect 21 0 22 0; #X connect 21 1 53 2; #X connect 22 0 5 1; #X connect 23 0 35 0; #X connect 24 0 12 0; #X connect 24 0 17 0; #X connect 24 1 4 0; #X connect 24 2 23 0; #X connect 24 3 45 0; #X connect 24 4 27 0; #X connect 25 0 16 0; #X connect 26 0 14 0; #X connect 26 0 16 1; #X connect 27 0 26 1; #X connect 28 0 16 1; #X connect 29 0 24 0; #X connect 30 0 53 0; #X connect 31 0 30 0; #X connect 32 0 18 0; #X connect 32 0 53 3; #X connect 33 0 18 0; #X connect 33 0 53 3; #X connect 33 1 34 0; #X connect 34 0 32 1; #X connect 35 0 5 0; #X connect 36 0 40 0; #X connect 36 0 30 0; #X connect 37 0 36 1; #X connect 40 0 36 1; #X connect 41 0 49 0; #X connect 44 0 57 0; #X connect 44 1 52 0; #X connect 44 2 20 0; #X connect 45 0 32 1; #X connect 46 0 41 0; #X connect 47 0 41 0; #X connect 48 0 35 0; #X connect 48 1 6 0; #X connect 48 2 51 0; #X connect 48 3 33 0; #X connect 48 4 50 0; #X connect 48 5 19 0; #X connect 48 6 47 0; #X connect 48 6 25 0; #X connect 48 7 36 1; #X connect 48 8 10 0; #X connect 49 0 36 0; #X connect 49 1 26 0; #X connect 49 2 25 0; #X connect 50 0 31 0; #X connect 51 0 44 0; #X connect 52 0 53 1; #X connect 53 0 56 0; #X connect 54 0 0 0; #X connect 54 1 43 0; #X connect 55 0 13 0; #X connect 55 1 42 0; #X connect 56 0 16 0; #X connect 57 0 53 1;

1 0

JACK transport in pd
by Jon B 29 Oct '04

29 Oct '04

I don't understand JACK transport completely, but is there functionality for it in pd? Could I create some box in pd that would bang when I press play in ardour, and create outputs when ardour changes BPM, etc? will this be added at a later date?

2 1

GEM: pix_image reloading image already loaded
by Etienne Desautels 29 Oct '04

29 Oct '04

Hi all, I did for an interactive video installation a pd-GEM patch, a kind of video sequencer. I'm on mac os 10.3.5 with pd 0.37 and GEM 0.90. I use pix_image to load images on a rectangle and I have 2 problems with it. First, pix_image have a system to keep each loaded image in the computer memory for using it later if you reload the _exact_ same image. But if you load a lot, say hundreds, of images, that will use a lot of memory. I'd like to know if there's a way to avoid this, a way to release this memory ? Secondly, I think there's a bug in pix_image (and pix_multiimage also). It's suppose to use the data image in the cache if you reload the _exact_ same image, but it doesn't seem to work. That make my first problem even worst because each time you reload the same image, gem will put it another time in memory, so the memory will grow indefinitely. I did the test with pix_image and pix_multiimage and on 2 different computers (powerbook 667 with an ATI and a dual G4 1GHz with an nVidia). Each time I reload the same image, I can see the memory usage of pd growing. The only way to release the memory is to quit pd. It's not an acceptable solution for me because my installation is running all day long and at some point PD hang because there's no more memory and swap. You could try it by using the help patch of pix_image and keep reloading the same image and watching the memory usage of pd in top. Thank you for your help. Etienne

7 11

pool object crashing OS X
by Bradford Reed 29 Oct '04

29 Oct '04

Hi List, I'm trying to open memento and rradical patches but the pool object seems to be crashing PD. The standalone version0.38-0test4... (which I just DLd... COOOOL & amazing!!!!) just crashes and the terminal says GUI error in my older wish shelled version. Any tips. Thanks in advance -Bradford http://www.pencilina.com

2 1

UK PD Workshop (WAS: Re: [PD-announce] .)
by derek holzer 28 Oct '04

28 Oct '04

Hi Lea, we haven't gone totally public with it yet [will send "press release" to PD-Announce when all dates and venues are confirmed], but me and Aymeric Mansoux will be doing a PD/GEM/PDP workshop tour of the UK, with a stop at The Lighthouse in Brighton from Tuesday Dec 14 to Saturday Dec 18. The Lighthouse page doesn't have any specifics yet: http://www.lighthouse.org.uk/ But here is a rough curriculum: http://www.yourmachines.org/wiki/index.php/PD.ZILLA_workshop Try contacting The Lighthouse directly for registration info. Best, Derek Lea Piontek wrote: > Hello everybody, > > I am new to the mailinglist and I am really impressed > by its efficiency as well as by the commitment of the > participants ! > > Question: > Does anybody of you intend to do a PD-workshop > in Southengland ( i.e. Bristol, Bath or London ) in > the near future ? > > Tschoe, > Lea -- derek holzer ::: http://www.umatic.nl ---Oblique Strategy # 39: "Cut a vital connection"

1 0

← Newer
1
2
3
4
5
6
7
...
31
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 October 2004