Pd-list

pd-list@lists.iem.at

19 participants
33278 discussions

Re: [PD] RIP Ed Kelly
by Dan Wilcox 14 Mar '24

14 Mar '24

5 7

[PD-announce] Accademia Chigiana: Live-Electronics e Sound and Music Computing seminar Siena Italy July 15-27 2024
by Nicola Bernardini 14 Mar '24

14 Mar '24

https://www.chigiana.org/en/live-electronics-2024/ LIVE ELECTRONICS SOUND AND MUSIC COMPUTING Performance and interpretation of electronic music in concert ALVISE VIDOLIN instructor NICOLA BERNARDINI co-instructor 15 JULY / 27 JULY GENERAL INFORMATION The course is aimed at composers, performers, and interpreters of electronic music, as well as sound engineers who wish to delve into theoretical, technical, and creative aspects related to the production of live electronic concerts. The online lessons are preparatory for the in-person course and will take place from 10:00 AM to 1:00 PM / 3:00 PM to 6:00 PM on the following days: May 10th, 17th, 24th, and 31st, as well as June 14th and 21st. 1. COMPOSITION TRACK For the admission exam, candidates must submit the scores of two recent compositions with electronic music parts, attaching any audio files and recordings of a performance (to be uploaded on YouTube in “unlisted” mode). The scores must reach the Secretariat of the Chigiana Academy through the online registration form by April 30. At the same time, the registration-exam fee must be paid. The Chigiana Academy will communicate the results of the selection made by the examining committee to all candidates. The course will have an analytical/theoretical nature in online lessons and laboratory sessions with daily meetings in face-to-face lessons. For a limited number of candidates, the possibility of enrolling as listening students is allowed. Actual students are required to submit, by the date of the first online meeting, a score (or sketches) of an original composition for voice and/or solo instrument with live electronics. The electronic part will be created during the lessons and performed in concert (July 27) by a student from the courses of the Chigiana Academy. 2. PERFORMANCE TRACK For the entrance exam, candidates must present the technical-performance plans for two pieces from the repertoire for voice or instrument or ensemble and live electronics by a well-known author, to be chosen by each candidate. These must be sent with the application form by April 30. The technical-performance plans must be finalized for performance in a hall of roughly 250 seats and approximate dimensions of m. 50 x 10 x 5(h), with live electronics preferably to be performed by a single person. To perform the work, the candidate may make use, as necessary, of components from the following audio system: 9 independent amplification channels with 9 full-range loudspeakers positioned on the boom at variable height and orientation; 1 subwoofer speaker positioned on the ground with independent amplification channel; wide variety of dynamic condenser, proximity, radio, microphones with rods and various supports; 1 analog or digital mixer of the candidate’s choice; 1 reverb generator of the candidate’s choice; 1 personal computer with multichannel audio interface and MIDI controller of the candidate’s choice, software chosen by the candidate (preferred: Max / MSP, PD, Supercollider, Csound, or Faust, which may also be interconnected with each other) power supply, audio and power cables, technician for installation support. The plan must include: data sheet; diagram of the connections between the various devices and their location in the Hall and/or in neighboring environments; detailed configuration of the mixer (inputs/outputs, internal programming); performance environment created by the computer using the chosen software; text describing the actions that the performer must perform during the performance, possibly accompanied by additional instructions inserted in the score. COURSE DETAILS Lessons on theory will deepen the student’s knowledge of the following topics: – the temporal eco-sustainability of musical works with electronic parts – the choice of technological equipment suitable for sustainability – the adaptation of past works made with technologies that are no longer available – the various semiographic notations useful for the reading, interpretation and reconstruction of electronic parts – the use of scripting and automation systems for the systematic creation of highly complex electronic scores These topics present challenging aspects that are still open to emerging research and will be addressed by highlighting the research and investigating the know-how and components necessary for in-depth realizations of past and future works. LESSONS AND WORKSHOPS IN-PERSON COURSE The practical lessons provide for the active participation of students in the performance of the electronic parts of the compositions listed below that will be performed within the concerts of the Chigiana International Festival & Summer Academy 2024: Dashow Soundings in pure duration n. 10 / Ipiece per Arturo Tallini Momi Vuoi che nel fuori for percussion trio and electronics Nono Omaggio a György Kurtàg / Post Praeludium n. 1 per Donau / Interludio Primo dal “Prometeo” Ligeti Artikulation Romitelli Natura morta con fiamme (1991) Ligeti Glissandi Manoury Pluton (1988) Letort Nautipoulpe ONLINE PREPARATORY LESSONS In the on-line preparatory lessons, the works with electronic parts to be performed in the aforementioned concerts will be analyzed and the executive environments planned. In the on-site laboratories, in addition to the execution of the electronic parts, the problems of recording, processing and spatialization of live sounds will be addressed, also as a function of documentation work to be carried out in post production. Through the preparation, rehearsal and performance of the pieces with electronics listed above, different playing techniques will be studied, using the SaMPL electroacoustic system based on d & b audiotechnik amplification, Yamaha DM1000 digital mixer and multi-channel spatialization in 8-channels. _______________________________________________ Pd-announce mailing list Pd-announce(a)lists.iem.at https://lists.puredata.info/listinfo/pd-announce

1 0

Re: [PD] hid objects on linux/mac/win? hidraw on linux? hidraw parsing?
by Peter P. 14 Mar '24

14 Mar '24

I am forwarding another helpful reply from Lucas below, which seems to have bypassed this list. Thank you Lucas for the information, this is much appreciated! P ----- Forwarded message from Lucas Cordiviola ----- Subject: Re: [PD] hid objects on linux/mac/win? hidraw on linux? hidraw parsing? Date: Wed, 13 Mar 2024 01:37:42 -0300 I don't wanna go to deep into HIDs as I know little about it. I came to [hidraw] because i needed something easy for Windows (iirc hids external were not working for me on Windows at that time) so I was writing my first externals as a training and decided to wrap https://github.com/libusb/hidapi. > I am a bit puzzled that I don't get any error message from [hidraw] when > trying 'listdevices'. Me too. I had tested on Windows and Debian and it worked. On macOS I tested it on a VM but i could not get "listed" devices. Someone at the time of the release reported it worked just fine on a real mac with a real joystick. > Understood. How can I tell which element of the list belongs to which > switch/dimension/etc? Are these floats somehow (binary) encoded? Yes they are encoded. There's a good side and a bad one. The good one is that no "symbols" are used and that's better at Pd's internal message side. The bad side is that each device has it's own implementation of this list of floats. https://github.com/libusb/hidapi just grabs them and spits them. In [hidio] and other better externals there's and OS layer involved that can tell canonically what "switch/dimension/etc" it has received. So these externals make your life easier and more realistic. But if you get the chance to open a device with [hidraw] you won't be much scared of the list of bytes. if you press one button you'll get say "0 11 0 0" and on release you'll get "0 0 0 0". if you press another one you'll get say "0 12 0 0".Â Each float on the list represent a byte (0 - 255) and each device has a different number of (fixed) items in the list.

2 1

[PD-announce] pmpd v 0.13
by cyrille henry 13 Mar '24

13 Mar '24

Hello, Thanks to all the help provide by Benjamin Wesch, pmpd (Physical Modelling for Pure Data) version 0.13 is ready. pmpd aim to provide physical modelling (mass/spring system) simulation to control data in natural ways. Audio synthesis is also possible, now in 2d or 3d thanks to the new objects : pmpd2d~ and pmpd3d~. It's on deken. Cheers Cyrille _______________________________________________ Pd-announce mailing list Pd-announce(a)lists.iem.at https://lists.puredata.info/listinfo/pd-announce

4 10

trying to test 'pdp library and 'pdp_scan~'
by Alexandre Torres Porres 12 Mar '24

12 Mar '24

When reading about 'Scanned synthesis' in https://en.wikipedia.org/wiki/Scanned_synthesis I see about the [pdp_scan~] external from 'pdp', but I can't use it... I can still try extended in my machine and it didn't really work back then, I get Applications/Pd-extended.app/Contents/Resources/extra/pdp/pdp.pd_darwin, 10): Library not loaded: /usr/X11R6/lib/libX11.6.dylib Referenced from: /Applications/Pd-extended.app/Contents/Resources/extra/pdp/pdp.pd_darwin Reason: image not found pdp: can't load library Purr Data can't load it either. The 'pdp' version in deken (0-0extended) doesn't work either and all print the same error. I wanted to check this object out, does anybody know where the source lives and if we can try and compile it? cheers

6 29

Re: [PD] RIP Ed Kelly
by Dan Wilcox 12 Mar '24

12 Mar '24

Howdy all, I wrote up a little RIP page with some pictures and video from Pd cons 2011 and 2016. A unique member of the community indeed: Ed Kelly and I bonded over computer music and a silly sense of humor. Although I only hung out with him a few times in person and we mainly communicated online over the years, it felt like I had always known him. I know things were not always easy for him, but he would push through with creative energy. He will be missed in the Pure Data community, through which I met him. Condolences to his friends and family in the UK and around the world. - Dan Wilcox http://danomatika.com/news/2024/rip-ed-kelly @Alex: Is there a condolences page to write to, specifically not on Facebook, etc? Maybe we can all write something to show his touch beyond in-person relationships. > It's a great shame, I remember him with great joy, I still remember the > anecdote about the dog. A great guy. > :/ > Jos? @Jos?: What was the anecdote? > On Mar 10, 2024, at 11:18 PM, pd-list-request(a)lists.iem.at wrote: > > Message: 1 > Date: Sun, 10 Mar 2024 14:49:26 -0300 > From: Alexandre Torres Porres <porres(a)gmail.com <mailto:porres@gmail.com>> > To: Pd-List <pd-list(a)lists.iem.at <mailto:pd-list@lists.iem.at>> > Subject: [PD] RIP Ed Kelly > Message-ID: > <CAEAsFmj3zNjSWMqKFcBYBYabd=zfVx-U+Fo7XXybCCrsPorHNg(a)mail.gmail.com <mailto:CAEAsFmj3zNjSWMqKFcBYBYabd=zfVx-U+Fo7XXybCCrsPorHNg@mail.gmail.com>> > Content-Type: text/plain; charset="utf-8" > > Tehomas Bow on facebook gave us the bad news. He had a stroke and fell, got > injured and passed away this friday. He leaves us soon, just before turning > 50. Ed was quite a fun character, I loved him, he'll be missed. Rest in > Peace. > > * March 29th, 1974 > ? March 8th, 2024 -------- Dan Wilcox danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>

3 3

help making sense of [readsf~]
by Alexandre Torres Porres 07 Mar '24

07 Mar '24

Hi, a discussion on facebook led me to revise the help file of [readsf~] and I'm making some edits and changes. It seems it wasn't all to clear how it works, making it seem it would load the file into an internal memory and not just read directly from the disk, and in fact I'm not really sure how it works. Also, the help has been saying forever how one should open a file "a bit" in advance, which is vague and it also doesn't make it clear why and how long soon... it also says it starts reading from the file right away, but doesn't play it until you say so... this is what makes it a bit confusing to people I guess, cause it seems to load into memory. Now, I believe there is some operation that is done in advance and then it adds some latency maybe, so if you do it in advance you get to manage this a bit better, is that it? Can we have and add a bit more information about it? Also, is it the case that this used to be a somewhat significant issue back in the day, which means this has become not significant all for a while? Last, but not least, I can't make much sense of the 2nd argument. I had a look at the code to see what is the default value (which is also the minimum allowed value), something I always put on the help files, and I wonder if this is some kind of memory buffer that we load the file into... Moreover, why would someone need a bigger buffer than the default value? I need this information well sorted to make this help file as nice as the others. Cheers!

2 15

help making sense of [readsf~]
by Christof Ressi 07 Mar '24

07 Mar '24

On 07.03.2024 01:33, Alexandre Torres Porres wrote: > Em qua., 6 de mar. de 2024 às 21:27, Alexandre Torres Porres > <porres(a)gmail.com> escreveu: > > I got this rather old 2013 macbook air, and using it with a delay > of only 5ms doesn't give me any noticeable dropout! > As I said, you likely don't notice it if the file is (still) cached by the OS. You need to test with files that aren't cached! On Windows you can manually clear the file cache (https://stackoverflow.com/a/9649439), but I don't know about macOS. > > btw, 4ms chokes and causes dropouts when testing audio with the > audio-mid test patch, just playing a sine wave... That's a problem with the scheduler. With my scheduler fixes, you should be able to go lower: https://github.com/pure-data/pure-data/pull/1756 But again, you should really test with uncached files and/or with a fairly high CPU load. Christof

1 0

Re: [PD] help making sense of [readsf~]
by Dan Wilcox 04 Mar '24

04 Mar '24

*This* is a good point and worth noting, not necessarily as a "always delay before playing" sort of thing but more a short description of how it works, then a note like "if you experience occasional dropouts on first accessing a file, consider adding a small delay after opening but *before* playing." > On Mar 4, 2024, at 1:01 PM, pd-list-request(a)lists.iem.at wrote: > > Message: 1 > Date: Mon, 4 Mar 2024 12:55:54 +0100 > From: Christof Ressi <info(a)christofressi.com <mailto:info@christofressi.com>> > To: pd-list(a)lists.iem.at <mailto:pd-list@lists.iem.at> > Subject: Re: [PD] help making sense of [readsf~] > Message-ID: <2176516f-edbe-4982-bcfa-b7002952abc1(a)christofressi.com <mailto:2176516f-edbe-4982-bcfa-b7002952abc1@christofressi.com>> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Actually, I forgot something important: > > Of course, the worker thread must also *open* the file! If the file is > not yet cached by the OS, this can indeed take a few milliseconds.If you > don't add some delay between "open" and "start", you might notice that > you get a dropout the very first time, but not on subsequent times. > > In fact, if you don't wait between "open" and "start", the perform > method almost certainly blocks. However, often we don't notice because > it may be "absorbed" by Pd's own ringbuffer (= "Delay" in the audio > settings). > > Anyway, I agree that the help needs some more clarification! (Just make > sure you really understand how the object works before changing the help > patch :) > > ?Christof -------- Dan Wilcox danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>

2 1

Re: [PD] help making sense of [readsf~]
by Dan Wilcox 04 Mar '24

04 Mar '24

To echo Christof, each object has a parallel worker thread as the file I/O could block Pd's audio thread. It takes time to read the beginning of the file (or from the start point) before it can be played back. IMO the warning / concern in the help file is really from a time of *much* slower media where the file I/O would take a lot longer, especially if a spinning hard drive has to access multiple files in multiple physical locations. Nowadays, speed and (pre-)caching make access times so much faster we don't necessarily think about it except for very large files we need to be able to randomly access. As Christof says, fine tuning the reader buffer size could be thought of as fine tuning the audio buffer length, ie. a 64 block size is faster but has less space/time if your patch does some really CPU intensive stuff. If you don't need super responsively, you can increase the block size. I have never personally needed to use anything but the default readsf~ buffer size. > On Mar 4, 2024, at 12:00 PM, pd-list-request(a)lists.iem.at wrote: > > Message: 2 > Date: Mon, 4 Mar 2024 06:23:16 +0100 > From: Christof Ressi <info(a)christofressi.com <mailto:info@christofressi.com>> > To: pd-list(a)lists.iem.at <mailto:pd-list@lists.iem.at> > Subject: Re: [PD] help making sense of [readsf~] > Message-ID: <93bd5dc6-baa9-4097-ac07-ae7683b75479(a)christofressi.com <mailto:93bd5dc6-baa9-4097-ac07-ae7683b75479@christofressi.com>> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Hi, > >> making it seem it would load the file into an internal memory and not >> just read directly from the disk > The help file says "soundfile playback from disk"... > > Here's how the object works: > > A worker thread is reading data from the given file and fills a buffer. > If the buffer is full, it waits until there is space. The thread starts > to do its job right after the [open( message. > > Once we send the [start( message, the perform method simply tries to > read a block of samples from the buffer and copy it to the outlets. If > there is not enough data in the buffer, the method blocks - which is > something we definitely want to avoid! This is exactly the reason why we > need to wait a little bit between the [open( message and the [start( > message; otherwise the perform routine might have to wait for the > buffer, causing a dropout. > > The second argument for [readsf~] is the size of the buffer. The default > value seems to be 262144 bytes (per channel). In single-precision Pd > that corresponds to 65536 samples, which should be more than enough. I > think this value comes from the times where everybody had slow HDDs with > unpredictable seek times; for modern SSDs it can be much smaller, but we > probably don't care about a few kilobytes. > > (BTW, I have no idea why the help patch uses a buffer size of 1 MB...) -------- Dan Wilcox danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>

2 1

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