Pd-dev August 2021

pd-dev@lists.iem.at

12 participants
17 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] plans for next Pd release
by Dan Wilcox 29 Sep '21

29 Sep '21

Howdy Miller, Let me know what areas I can help with. I saw a comment about having problems compiling d_soundfile_caf.c on windows? Also, there are a couple of things on macOS which should be updated, including checking if the latest Tcl/Tk Wish can be built natively for arm64. I last looked around February and it wouldn't build. > On Jul 13, 2021, at 8:57 PM, pd-dev-request(a)lists.iem.at wrote: > > Message: 1 > Date: Tue, 13 Jul 2021 10:22:17 -0700 > From: Miller Puckette <msp(a)ucsd.edu <mailto:msp@ucsd.edu>> > To: pd-dev(a)lists.iem.at <mailto:pd-dev@lists.iem.at> > Subject: [PD-dev] plans for next Pd release > Message-ID: <20210713172217.v4ch3b3dk7go7k5q(a)ucsd.edu <mailto:20210713172217.v4ch3b3dk7go7k5q@ucsd.edu>> > Content-Type: text/plain; charset=us-ascii > > (re-send - I had sent to pd-dev(a)iem.at <mailto:pd-dev@iem.at> but that now seems to be defunct...) -------- Dan Wilcox @danomatika <http://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>

4 6

New [command] external
by Roman Haefeli 23 Sep '21

23 Sep '21

Hey all, I am recently trying to dive into the C realm and revamped ggee's [shell] external. Because its API is different in many ways from the original, I decided to give it a new name. Before I publish this to a wider audience through Deken, I would like to make sure I do not destroy the world by releasing this. Any comments or suggestions are welcome. A first question I have is concerning the order of outlets. I kept the original order: STDOUT left, exit code right. However, since the exit code outlet fires always last, it probably would make sense the make it the left-most. Are there any similar precedent objects? https://github.com/pd-externals/command/ Thanks, Roman

3 5

"extra" folder is not showing its content in Pd's browser.
by Lucas Cordiviola 02 Sep '21

02 Sep '21

Building the current (571ad34) on Linux/Win the extra folder is not shown in Pd's Browser. -- Mensaje telepatico asistido por maquinas.

2 4

Re: [PD-dev] writing exploits in Pd (Re: [PD] [file])
by Christof Ressi 31 Aug '21

31 Aug '21

The exploit successfully changes my MIDI settings and adds search paths, but unfortunately it crashes with a completely wiped stack before showing me the Tk dialog :-( On 31.08.2021 14:33, IOhannes m zmoelnig wrote: > On 8/31/21 1:05 PM, IOhannes m zmoelnig wrote: >> >> ¹ i wonder whether it would be possible (with Pd>=0.42) to create a >> patch that creates a gui-plugin on the fly. >> if this is true, then you can already do everything that [file] >> allows you to do - and much more. > > > like with the attached patch. > > i've tested this on Linux, macOS and Windows (where i have an msys > installation and some folders that might make the exploit work - but > which might not be present on your machine). > > running the patch will add a few search-paths to your preferences and > probably modify your MIDI-settings. > apart from that, it shouldn't do any harm (though i wouldn't recommend > to run it if you have a show tonight). > use at your own risk. > > gmasdr > IOhannes > > _______________________________________________ > Pd-list(a)lists.iem.at mailing list > UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list

5 12

-verbose vs logpost() (IOhannes m zmoelnig)
by Dan Wilcox 26 Aug '21

26 Aug '21

Maybe an additional -loglevel which allows you set the level explicitly? -verbose to me would set the log level to verbose overall & -noverbose would set it back to the default. Also tangentially, I would also bring up the handling of some of these flags which affect the state: using -verbose also sets the verbose setting which is then saved wirh the user settings. I find this annoying as I would rather have the command line flags like this be *temporary* and not affect the actual setting itself. To me changing the value directly in the GUI should (as it does now). I believe I opened an issue about this already. > On Aug 26, 2021, at 12:00 PM, pd-dev-request(a)lists.iem.at wrote: > > with the latter in mind, we might even use multiple "-noverbose" flags > to lower the verbosity (at least of the stderr) below post() - so that > only errors would be visible. -------- Dan Wilcox @danomatika <http://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>

2 2

-verbose vs logpost()
by IOhannes m zmoelnig 25 Aug '21

25 Aug '21

the other question that is tightly related to the "unifying loglevels" thread is, how to deal with "-verbose" resp "-noverbose". currently the two concepts ("use of '-verbose'" vs "use of logpost()/verbose()") are obviously in the same realm but somewhat independent. raising verbosity with "-verbose" will: - (obviously) make Pd more chatty, regardless of loglevels. e.g. some errors will only printed (as errors!) is "-verbose" is given - verbose() is coupled with "-verbose", as it will only ever print anything if the verbose level is not bigger than the number of "-verbose" flags present. e.g. "verbose(0)" (aka 'PD_DEBUG') will print if no "-verbose" is given but "verbose(1)" (aka 'PD_VERBOSE') will only print if the "-verbose" flag is present and "verbose(2)" will only print if Pd is invoked with double-verbosity "-verbose -verbose" i actually think this is not a bad idea (barring the actual values, sede the other thread), as "-verbose" might generate a sufficient amount of traffic between Pd and Pd-GUI to choke the system. even if the output isn't displayed (as the user just uses loglevel "2 normal"). i wonder, whether we should use the "-verbose" flag, to also suppress logpost() messages. there's two reasons: - deprecate 'verbose()' in favour of 'logpost()' - so we only have to deal with a single beast - better control about what is displayed in "-stderr" mode. when running Pd with "-nogui" (or "-stderr"), the terminal is currently flooded with high-verbose messages (compared to the Pd-console). obviously this is a hyperbole and depends on the actual patch. i do find it annoying though with the latter in mind, we might even use multiple "-noverbose" flags to lower the verbosity (at least of the stderr) below post() - so that only errors would be visible. mgsdr IOhannes PS: i don't know whether there's a question in this mail. but the entire verbose-handling is a bit annoying and i would like to make it easier to grasp.

1 0

Re: [PD-dev] [ot] asiosdk2.3 gone from steinberg's website
by Dan Wilcox 25 Aug '21

25 Aug '21

That should be it. It looks like they moved their downloads to a subdomain and the new direct URL is on download.steinberg.net <http://download.steinberg.net/> so I you are scripting and want the 2.3 version specifically: https://download.steinberg.net/sdk_downloads/asiosdk2.3.zip <https://download.steinberg.net/sdk_downloads/asiosdk2.3.zip> Maybe add this info to the asio/README.txt: https://github.com/pure-data/pure-data/tree/master/asio <https://github.com/pure-data/pure-data/tree/master/asio> ie. "You can download a specific version using https://download.steinberg.net/sdk_downloads/asiosdk#.#.zip" etc > On Aug 25, 2021, at 12:00 PM, pd-dev-request(a)lists.iem.at wrote: > > Date: Wed, 25 Aug 2021 10:42:06 +0200 > From: IOhannes m zmoelnig <zmoelnig(a)iem.at <mailto:zmoelnig@iem.at>> > To: "pd-dev(a)lists.iem.at <mailto:pd-dev@lists.iem.at>" <pd-dev(a)lists.iem.at <mailto:pd-dev@lists.iem.at>> > Subject: [PD-dev] [ot] asiosdk2.3 gone from steinberg's website > Message-ID: <c98d37d7-fb61-659c-2525-ef74b6372356(a)iem.at <mailto:c98d37d7-fb61-659c-2525-ef74b6372356@iem.at>> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > i just found out on the CI that since yesterday, steinberg obviously > have removed the old asiosdk download? from their website. > > apparently a newer version can be obtained from > https://www.steinberg.net/asiosdk <https://www.steinberg.net/asiosdk> > > mgdasr > IOhannes > > ? http://www.steinberg.net/sdk_downloads/asiosdk2.3.zip <http://www.steinberg.net/sdk_downloads/asiosdk2.3.zip> -------- Dan Wilcox @danomatika <http://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>

1 0

Re: [PD-dev] unifying loglevels
by Dan Wilcox 25 Aug '21

25 Aug '21

Sounds good to me. I agree that 0 (CRITICAL) as the baseline and the levels as an unsigned int is better. With the enum, understanding the numeric values should not be an issue moving forward. I would suggest considering a compatibility mode / compile time option to preserve existing functionality for those that *really* need it, then it can be removed later on (hopefully). I can imagine someone quickly trying to run a project with old pre-compiled externals and getting flooded with prints which they could at the least disable via some compatibility flag, however the amount of time it might take for them to figure this out could make the point moot. OTOH if adding this ends up taking too much time/focus for little benefit, by all means don't do it. :) > On Aug 25, 2021, at 10:35 AM, pd-dev-request(a)lists.iem.at wrote: > > Date: Tue, 24 Aug 2021 15:59:34 +0200 > From: IOhannes m zmoelnig <zmoelnig(a)iem.at <mailto:zmoelnig@iem.at>> > To: Pd-dev(a)lists.iem.at <mailto:Pd-dev@lists.iem.at> > Subject: [PD-dev] unifying loglevels > Message-ID: <02113e2f-d09f-6cb4-bc88-c25201fc985b(a)iem.at <mailto:02113e2f-d09f-6cb4-bc88-c25201fc985b@iem.at>> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > TL;DR i'd like to propose to unify the loglevels as used by verbose() > and logpost() -------- Dan Wilcox @danomatika <http://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>

3 2

[ot] asiosdk2.3 gone from steinberg's website
by IOhannes m zmoelnig 25 Aug '21

25 Aug '21

i just found out on the CI that since yesterday, steinberg obviously have removed the old asiosdk download¹ from their website. apparently a newer version can be obtained from https://www.steinberg.net/asiosdk mgdasr IOhannes ¹ http://www.steinberg.net/sdk_downloads/asiosdk2.3.zip

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

Pd-dev August 2021