I *think* my reasoning back then was that it can break existing patches,
notably those that do [loadbang] -> [samplerate~] and expect 44100. (I
used to do that myself in the past when I didn't know better :)
If the user didn't save the audio device, this would now output 48000.
But such patches are wrong anyway and personally I don't care much anymore.
In the meantime, Alex has also updated samplerate~-help.pd, which now
explains how to properly use "pd-dsp-started". *)
So from my side it would be ok to switch to 48000. But as Lucas noted,
we should also update the included WAV files.
Christof
*) I think there could be an explicit warning not to rely on [loadbang]
-> [samplerate~].
On 28.05.2025 10:26, Lucas Cordiviola wrote:
Christof and I were for 44.1k because of the wav files in the
examples. also most chances are that if you open a wav file is for
44.1k and readsf~ wont resample.
But I think someday we should take the plunge... are there still
good reasons to wait on this?
that was the reason but idk if is still good.
:)
---
pd-dev@lists.iem.at - the Pd developers' mailinglist
https://lists.iem.at/hyperkitty/list/pd-dev@lists.iem.at/message/OM7KU6J25RNLKW3LCLUJJDR2TOTPLGDA/
