Pd-dev April 2021

pd-dev@lists.iem.at

12 participants
7 discussions

Doppler effect implementation
by Frodo Jedi 01 May '22

01 May '22

Hi all, I am searching for a Pd implementation of a doppler effect as realistic as possible. Any recommendations? Any patch/external already made and well tested? Cheers FJ

9 15

Re: [PD-dev] Polling: Execute a function every X ms from within the external.
by Dan Wilcox 30 Apr '21

30 Apr '21

Maybe this is a good example to add somewhere? > On Apr 30, 2021, at 12:00 PM, pd-dev-request(a)lists.iem.at wrote: > > Message: 2 > Date: Thu, 29 Apr 2021 23:12:12 +0200 > From: Christof Ressi <info(a)christofressi.com <mailto:info@christofressi.com>> > To: pd-dev <pd-dev(a)lists.iem.at <mailto:pd-dev@lists.iem.at>> > Subject: Re: [PD-dev] Polling: Execute a function every X ms from > within the external. > Message-ID: <eb2b0430-8d03-96ed-45de-2555e9321b73(a)christofressi.com <mailto:eb2b0430-8d03-96ed-45de-2555e9321b73@christofressi.com>> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Here's how: -------- Dan Wilcox @danomatika <http://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>

2 2

Polling: Execute a function every X ms from within the external.
by Kyriakos Charalampides 29 Apr '21

29 Apr '21

I recently started learning how to write some custom pd externals. It has been quite fun until now, but its been a few days I am stuck in a loop. I want to read a buffer coming from an external device every 1 ms. I could do that with a metro but this can cause several issues with this buffer. My initial though was to use a for loop but this was obviously a horrible idea since pd will stuck in the for loop and hang. Then I though to use a clock to execute my reading function but all examples with clock and clock_delay seem to be based on for and while loops. What I would really like to achieve is to execute the reading function every 1ms and interrupt this process every time that a new message is coming from pd. Any tips or ideas will be highly appreciated. All best, Kyr

2 1

signal graph processing
by David Rush 28 Apr '21

28 Apr '21

Hi All - I'm trying to figure out where to look in the code to try and understand the signal rate processing better. Specifically, I want to understand how the graph gets optimized - I've read a rumour that [*~ 0] can cause a whole signal chain to stop being computed, and I would like to verify that in the code and understand the whole process a bit better. Where should I start looking? TIA - d -- GPG Public key at http://cyber-rush.org/drr/gpg-public-key.txt

3 2

multi-architecture deken packages
by IOhannes m zmölnig 15 Apr '21

15 Apr '21

this all started as a thread on github: https://github.com/ericlyon/pd-fftease/issues/45 since i think it is of general interest (and i'm pretty sure i will never ever find the relevant info under the "time for a new release? (FFTease-3.1)" thread again, i'm taking this discussion here. the thread mainly revolves around how to create a single deken-package that contains binaries for all the relevant architectures. i'm too lazy to recap it here. the current discussion state is, how to deal with all those arm-variants out there. if somebody has more insight into the arm architectures, please shed a light :-) :::::: it's not complicated: the 32bit arm variants `armv6`, `armv7`, `armv8` (aka `aarm32`),... are backwards compatible. - you can run a binary compiled for `armv6` on any `armv7` or `armv8` CPU. - you can run a binary compiled for `armv7` on any `armv8` CPU. - but you cannot run a binary compiled for `armv8` on the older `armv7` resp `armv6` CPUs (missing instruction set) - similarly, you cannot run a binary compiled for `armv7` on the older `armv6` CPU. it's very similar to `i386` and `i686` and `Pentium-i7` and the like. typically, the newer CPUs will have instruction sets that outperform the older CPUs (`MMX/SSE/AVX` on the `x86` platform; `NEON` on `arm`). however, if you have a modern `Pentium-i7` and you are running an `i386`-compatible binary you will probably still get decent performance, because the processor is so much faster. with `arm`-chipsets it is a bit different, as they are much less powerful, so you hit the limitations sooner. @porres wrote: > I'm confused now, does this mean Raspbian is just for RPi Zero/1? it means that you can use Raspbian on the RPi Zero/1/2/3 and 4. however, you will get sub-optimal performance on the RPi2 and above. if you enable the normal Debian repositories on the RPi, you will get into trouble on the RPi Zero/1, as the binaries might (and most likely: will) have instructions that the RPi Zero/1 lacks. > so i'm confused, is the organelle a rasp 1? it all depends on which version you have. the [current specs](https://www.critterandguitari.com/organelle#design-specs) mention a `ARM Cortex A53` which is an `aarch64` processor (`armv8`) @emviveros wrote > "compute module" are not important since **RPizero variants are important**, so armv6 should be disponible. i'm not sure i understand what you mean. i tried to say, that i believe that - "compute module" is not important - RPi/zero is of (limited) importance - because of the RPi/zero we probably want to support `armv6` i guess you are saying the same(?) and > My first annoying is how to name armv6, armv7 and armv8 (aarch64) binaries to create a unified deken package for arm compilations. i don't know what this means either. however, i think we should forget about a unified `arm32` deken package. > armv6 = ?? (maybe .pd_linux) > armv7 = .l_arm > armv8 = .l_arm64 to which @porres answered: > anyway, let's just have these 3 together and I guess there won't be any issues :) at least for me, `armv8` is not the same as `aarch64`. most `armv8` are capable of both 32bit (`aarch32`) and 64bit (`aarch64`) instruction sets, but the 64bit part is optional. i'd prefer to use the `armv8` name for the 32bit variant *only*. when talking about the 64bit variant, we should use `aarch64`. regarding `armv6` and `armv7` in a single folder, i'm not sure whether this would work: - if a `Pd-armv7` happens to see the `armv6` external first, it will just load it (and never try to `armv7` binary) - if a `Pd-armv6` happens to see the `armv7` external first, it will just try load it: and i think the *loading* would succeed, leading to crashes whenever an illegal (armv7-)instruction is encountered. but as i've written above: the `armv6` is a very limited platform. you probably do not want to install any binaries that you cannot use on it anyhow. so i'd suggest to cram all the architectures into a fat deken package with the exception of `armv6` which you should package separately. mgfds IOhannes

5 17

example external code to browse?
by Iain Duncan 12 Apr '21

12 Apr '21

Hi everyone, I'm working now on a PureData port of Scheme For Max, but am hitting some obstacles and am wondering if anyone can point me at sample external code that can be browsed somewhere? (I'm very new to Pd). Specifically I'm looking for stuff that involves event oriented handling and dynamic methods, symbols, etc. (basically all the non-dsp stuff). I've seen the github how to but that's not covering much in the way of working with symbols extensively. thanks! iain

2 2

Modified [partconv~] and issues with fftw3
by Gloria Dal Santo 07 Apr '21

07 Apr '21

Hi everyone! I’m trying to create a sort of 3d audio reproduction system by convolving the dry sound with the BRIRs of a room. The patch I’m working on will be connected to a head-tracker so that I can change BRIR depending on the position of the listener. To achieve this I tried to use bsaylor’s [partconv~] but unfortunately, when I set a new impulse response, I have a short dead time. To fix this I tried to cross fade the output of two [partconv~] but this messes up the binaural cues, it is not the right approach. My idea is that of modifying the .c code of the external to get what I need. Usually, I work on Code::Blocks, MinGW compiler, Win10. I’ve already built some super simple externals, but this time I’m facing a problem that I’ve never encountered before: to perform the Fourier transform, partconv~.c uses the fftw3 library, and I couldn’t find a way to add it to the Linker Options. >From what I’ve understood online, fftw3 is a dynamic library, therefore there’s no .lib file. On Code::Blocks Settings -> Compiler -> Linker Settings -> Link libraries I cannot load a .dll dynamic library. I tried different solutions that I found online but none of those worked. I get “undefined reference to” errors when calling all the fftw3 functions. Can any of you help me somehow? If you were able to write an external that referred to the fftw3 library, how was your setup? Moreover, I saw that in the bsaylor’s library folder there are also files of the type .dsp, .dsw, .o. Once I modify the .c code, should I update those as well? I hope that I stated my issue clearly, if now please ask me for further details. Thank you in advance for your time. Gloria

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Pd-dev April 2021