Pd-list October 2001

pd-list@lists.iem.at

55 participants
74 discussions

[Fwd: [eu-gene] Open Source software for Generative Music ?]
by Bo.T 15 Oct '01

15 Oct '01

Is this of relevance for someone on this list? aplologies if you have all already seen this... -------- Original Message -------- Subject: [eu-gene] Open Source software for Generative Music ? Date: Sat, 13 Oct 2001 13:26:52 +0200 (MET DST) From: Zeljko Blace <zblace(a)alu.hr> Reply-To: eu-gene(a)generative.net To: eu-gene(a)generative.net Hi! I've spent some time on this list as trying to get a hand on interesting material and production projects for the exhibition I am planing on Generative art in May 2002 in Zagreb; Croatia. It is annual exhibition of Multimedia Institute and is therefore main event in computer arts in Croatia;) I plan to attend Next meeting in December to get some real contacts "beyond e-mail" and equire more depth-in knowledge on the subject. For the event we would like to raise money for Open Source Software development that would be used in practical workshops and that would generaly help this field to come closer to the desktop user... Is there anyone who is developing Open Source transplaform software with simple interface (so no CSound ;)... which can be recomended. Prefered model would be XML file format, .ogg for samples and clean code (easly portable to both Win/MacOS and Linux/BeOS). Maybe simple version of Open format by SSeyo can be used? PD or jMax code might be usefull for some of the sound processing (but building nice wrapper around it, something closer to SSEYO Koan products would be nice). Money in stake is up to 800$ + travell to Croatia and yes I know it is not big money for software development, so we are adressing enthusiasts and academic community firstly. Best, Zeljko Blace. Please contact me if you wanna know more details. -- "<AOL>" To unsubscribe from eu-gene visit http://www.generative.net/mailman/listinfo/eu-gene

1 0

framestein 0.20
by Juha Vehviläinen 15 Oct '01

15 Oct '01

framestein 0.20: - add: send_auto to automate sending frames thru network. works like send but keeps sending frames on each flip until you give it send_manual - add: BETA of fs.browser, use file formats that run in the browser like java or flash. see example-browser.pd - fix: execution order of events was reversed. what was i thinking? - fix: most plugins now work on displays other than 16 bits - more meaningless plugins: copy_vert http://framestein.org juha

1 0

how to receive keyboard inputs
by andychen5018 15 Oct '01

15 Oct '01

Hi, Does anyone know how to detect keyboard inputs for PD externs? For my PD externs, i want it to be want to respond a keyboard inputs, such as CTL-X or CTL-Y or some other combinations of keys. Thx Andy Chen

2 1

How to receive keyboard input
by andychen5018 15 Oct '01

15 Oct '01

Hi, This e-mail is to clarify one of my previous (very confusing) e-mail. Does anyone know how to detect keyboard inputs for PD externs? For my PD externs, i want it to be able to respond a keyboard inputs, such as CTL-X or CTL-Y or some other combinations of keys. For example, if I have a clock running, and I want to stop the clock with a keypress. And turns on the clock again with the same keypress. My main problems is that I am not sure how to implement it so that my c source code can detect and reponse to the keypress. Thx Andy Chen

2 1

super newbie question
by nathan drdul 13 Oct '01

13 Oct '01

I just installed PD for the first time,using mandrake 8.1, installed PD with pd-0.34-1.i386.rpm The test tones all work fine, in the documentation I can load up the first sinewave.pd and hear the tone fine. When i load up amplitude.pd I can't hear anything unless I connect the osc straight into the output. Then i hear the 440 sine.... Pretty much every other patch I have tried is silent. any help would be great, never had much luck with PD on win98, cant wait to hear what it can do. thanks nate __________________________________________________ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com

2 1

[devel/externals] handling anything[s] in several inlets ?
by CK 12 Oct '01

12 Oct '01

hi, I'm kind of stuck trying to handle several data types in right inlets ? any pointers to sourcecode ? thx, x -- chris(a)lo-res.org Postmodernism is german romanticism with better http://pilot.fm/ special effects. (Jeff Keuss / via ctheory.com)

2 2

[gem][announce] GemPlus-v0.2
by IOhannes m zmoelnig 10 Oct '01

10 Oct '01

i just put gemplus-0.2 on the web http://umlaeute.mur.at/gem pix_histo : andreas, is this what you wanted ??? pix_curve : what everybody needs pix_biquad: time-domain filtering pix_diff pix_takealpha are these of any use ? mfg.c.sadf IOhannes

2 1

pix_digivd & pix_1394
by Ulrich Kehrer 10 Oct '01

10 Oct '01

hi johannes & list, an object for pixel-processing digital video like mov, mpeg, avi,... would be very nice especially in conjunction with pix_dump/pix_set. concerning the naming issue pix_digitalvideo comes to my mind which is too long of course. pix_dv is short enough but DV is already taken in the global game of brand names (on the other hand...why care about it?). a compromise would be pix_digvid. another great object would be one that can talk IEEE 1394. is it possible to route the gemwin to a firewire-port? imagine putting out gem-work to a dv-recorder or a projector with a pix_1394 object... regards, ulrich

1 0

[devel] reentrant qlist revisited
by Krzysztof Czaja 09 Oct '01

09 Oct '01

hi, after proposing midifile<->qlist addition I thought I would check the recently changed qlist version. First of all, it still gives an error while running ... <target> next; <delay> <target> ... sequence, if <target>'s output is connected to qlist's input. I am now looking at the code, and suspect that the added x_reentered flag-field is meant to break infinite loops, occuring when a qlist object is self-feeding itself with a 'rewind' message. Well, reading code is misleading most of the time, so I may be wrong, but if not, then it is rather a `restarted' flag. So my question is this: what about recursive `next' message? Can we simply say, that it should not be used? Maybe so, but maybe there is even simpler solution. What happens now is that: 1. qlist_donext() in passes 1 to n of its main loop reads all not delayed messages up to a recursive `next'; 2. recursive `next' causes invocation of a child-call of qlist_donext(); 3. a child-call reads remaining messages up to a float (delay) and quits; 4. in pass n+1 of the main loop of parent-call, qlist_donext() reuses a previous target, passing it a new target as a message selector -- error. Target reusing should happen iff a new message is preceded by a comma -- or am I completely wrong here? If I am right, then maybe instead of checking, if we are going to read a new target, ie. instead of using a `semicolon-flag', it would be better to use a `comma-flag', ie. to check, if we are going to use a previous target. This change would protect from semicolon-swallowing recursion. Btw. what is the policy about adding pointers to qlists? It is now possible, but 1) pointer values cannot be saved in a file, and 2) in the current implementation pointers act as `comments', ie. everything starting from the pointer and up to a comma or a semicolon is ignored. Krzysztof

2 2

midifile interface to qlist
by Krzysztof Czaja 09 Oct '01

09 Oct '01

hi, a prototype midifile interface to qlist is almost ready now. Still, before releasing, I would like to do some of my own pre-alpha testing first, but this will need to wait until my teaching duties ease a little. There is a preliminary version snapshot available as three files (s_mf.h, s_mf.c, and x_qlist.c.diff) you can preview at suita.chopin.edu.pl/~czaja/midifile/. Have a quick look, if you like, but please remember this is a pre-release, ie. it is not meant to be used yet. I wait for any comments that would help me avoid silly mistakes. The implementation was done from scratch, following Standard MIDI Files 1.0 Draft specification, to make shure it closely obeys the basic standard, conforms to the `PureData coding style', and easily and naturally integrates with Pd code. Anyway, the basic parsing is pretty simple, the hard parts are specific to Pd and/or not covered in libraries I know of (but I know much too little). Besides, I prefer to deal with my own bugs, rather than to propagate other's. In this prototype version I wanted to keep changes to x_qlist.c as minimal and localized, as possible. Therefore, instead of adding `mf' file format to qlist's `read' and `write' messages (and providing automatic format detection in case a user had not specified read format), I have choosen a quick and dirty way of adding separate `mfread' and `mfwrite' messages. I think the interface should be integrated with plain read/write in the final version. There is much more to say, mainly about general feasibility of using qlist as a sequencing tool (but I prefer not to go into that, yet...) Krzysztof

1 0

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 2001