the thing is it is capable, it can just be alot of work… and so much effort and attention have been given to VSTs that alot of people just cannot give them up to learn how to build a from-scratch reverb.
the Erbe-Verb , named after another UCSD professor, Tom Erbe, is a digital reverb unit for eurorack but before he coded the algorithm in C, he designed and built it for testing and fine-tuning in Pd.
Pd, much like any synthesis programming language is plenty capable… its just that it requires alot of work which, for some, is very irritating office-feeling-kinda-work and not making music… Pd is like that for some people… and so Pd is really not worth getting into if it does not provide you with some option or ability that you could get more easily with a plugin… especially if plugins are your jam to begin with!
I’m mostly interested in generative music right now and I haven’t made music for a while (not that I ever made music, I’m the kind of person that gets into a lot of stuff all the time, then drops it, then get into it again and so on).
I was curious about trying some plugins but at the same time, not being that invested, I don’t want to spend money or have to learn other tools other than Pd (which I’m really enjoying, even the more tedious “spend half an hour trying to understand how to do this basic thing” side of it).
The answer will probably be “it depends”, but I wonder what most people use Pd for and what they rely on plugins for
for reference, here is a video regarding getting VST plugins inside of Pd. https://youtu.be/Cs0NPime0kU
this guy has some excellent videos regarding Pd in general…
although he hypes-up “dangers” of Pd regarding feedback, the clip~ object will nullify that
the thing is it is capable, it can just be alot of work… and so much effort and attention have been given to VSTs that alot of people just cannot give them up to learn how to build a from-scratch reverb.
the Erbe-Verb , named after another UCSD professor, Tom Erbe, is a digital reverb unit for eurorack but before he coded the algorithm in C, he designed and built it for testing and fine-tuning in Pd. Pd, much like any synthesis programming language is plenty capable… its just that it requires alot of work which, for some, is very irritating office-feeling-kinda-work and not making music… Pd is like that for some people… and so Pd is really not worth getting into if it does not provide you with some option or ability that you could get more easily with a plugin… especially if plugins are your jam to begin with!
i hope that babbling helps!
Thanks for the answer!
I’m mostly interested in generative music right now and I haven’t made music for a while (not that I ever made music, I’m the kind of person that gets into a lot of stuff all the time, then drops it, then get into it again and so on).
I was curious about trying some plugins but at the same time, not being that invested, I don’t want to spend money or have to learn other tools other than Pd (which I’m really enjoying, even the more tedious “spend half an hour trying to understand how to do this basic thing” side of it).
The answer will probably be “it depends”, but I wonder what most people use Pd for and what they rely on plugins for
for reference, here is a video regarding getting VST plugins inside of Pd.
https://youtu.be/Cs0NPime0kU this guy has some excellent videos regarding Pd in general… although he hypes-up “dangers” of Pd regarding feedback, the clip~ object will nullify that