4 ms·
There's a community, it's just very conservative. The problem (especially with PD) is that the community is hostile to anyone who says 'hey, this is great, but
by anigbrowl 4y ago
There's a community, it's just very conservative. The problem (especially with PD) is that the community is hostile to anyone who says 'hey, this is great, but hard to use.' It was true >20 years ago when I first became acquainted with PD and even more so now. Any criticism or unwelcome suggestions are treated as an insult to Miller Puckette and the proponent is attacked, ignored, or advised to implement it themselves (ie to go away and not come back).
PD's interface is stuck in the 1980s, with the monochrome graphics, lack of any support functionality (contextual menus or rearrangement/tidying functions, snapping) and idiosyncratic terminology (eg PD refers to module connectors as 'patch cords' just like on an analog modular synthesizer or mixer, but what synth people commonly call a pulse or a trigger is a 'bang' in PD). And its users mostly like it that way, the same way some people fetishize 8 bit videogames.
There have been more accessible versions of the same idea for a long time (ie the mid-90s), from Clavia's Nord Modular in hardware and Native Instrument's software synth Reaktor in the commercial space to solo projects like Ross Bencina's Audiomulch. The latter was very obviously inspired by PD but iterated on every aspect of the design, making it far more accessible and flexible.
PD's defenders (kinda like CSound's) emphasize how open-ended it is and that you can do anything, render any concept etc. In the audio synthesis world it's well understood that the more a manufacturer emphasizes unlimited creativity, massive patch storage, infinite potential etc., the less good the UI and the more basic the default quality of the sound engine. You can make it do anything, but unless you already have a very specific goals you will spend most of the time reinventing wheels in parameter space. If you want a mature technology stack for implementing an audio subsystem (eg in a game), it might be a very good choice. If you just want a flexible tool to make electronic music, it's best avoided.
- polyterative 4y ago> You can make it do anything, but unless you already have a very specific goals you will spend most of the time reinventing wheels in parameter space. If you want a mature technology stack for implementing an audio subsystem (eg in a game), it might be a very good choice. If you just want a flexible tool to make electronic music, it's best avoided. I agree so much. It's a cool tool but the curve to learn it is often not worth it
- usrusr 4y ago> In the audio synthesis world it's well understood that the more a manufacturer emphasizes unlimited creativity, massive patch storage, infinite potential etc., the less good the UI and the more basic the default quality of the sound engine. You can make it do anything, but unless you already have a very specific goals you will spend most of the time reinventing wheels in parameter space. Nicely illustrated by reductio ad absurdum: a "naked" Epyc with a few sticks of RAM, an NVMe and a pair of A/D in the upper kHz range would score quite well in "unlimited creativity, massive patch storage, infinite potential etc", but you'd spend quite some time reinventing wheels (e.g. this gets less bad if you add a compiler).
- anigbrowl 4y agoIf you're not hand-rolling your own resistors are you really trying?
- brudgers 4y agohey, this is great, but hard to use That’s the nature of many musical instruments. Not the kazoo of course, and if that’s your jam it’s cool by me. But it probably won’t get you to Carnegie Hall and that’s also cool by me. Which is to say that in a community of musicians, complaining that developing chops is hard work doesn’t have much traction. It doesn’t have much traction because even Garage Band requires commitment to achieve competence. It only produces slightly less poor to mediocre work easily. But I completely agree that 2500 patches is not necessarily better than 64…a lot of dance music was made with a 303. Live no less.
- spacechild1 4y ago> Any criticism or unwelcome suggestions are treated as an insult to Miller Puckette and the proponent is attacked, ignored, or advised to implement it themselves (ie to go away and not come back). I don't think this holds for the general case, but there a certainly a few users caught up in Stockholm Syndrome :-) I can assure you that the developer team (which I am a part of) is very well aware of Pd's limitations and problems. Pd has seen quite significant UX improvements over the last few years, but the pace of development is very slow. Anyway, if you have specific criticism, suggestions or feature requests, feel free to open a ticket on GitHub: https://github.com/pure-data/pure-data https://github.com/pure-data/pure-data. As a side note, the minimalistic GUI itself won't change since it is an intentional design decision by Miller, but there is some effort to abstract the core/GUI communication to allow alternative GUI implementations. (Personally, I really dislike the current Tcl/Tk GUI - not because it's minimalistic, but because it's slow and buggy.) > and idiosyncratic terminology (eg PD refers to module connectors as 'patch cords' just like on an analog modular synthesizer or mixer, but what synth people commonly call a pulse or a trigger is a 'bang' in PD). Pd's 'bang' belongs to the control/event domain, you can't really compare it to trigger/pulse in modular synthesizers. (FWIW, there are several Pd externals that implement audio-rate triggers.) > You can make it do anything, but unless you already have a very specific goals you will spend most of the time reinventing wheels in parameter space. That's a fair point. It's important for people to understand that Pd vanilla is really a programming environment with only a minimal set of built-in objects that allow you to build higher-level abstractions. You definitely need a set of "abstractions" or libraries to be productive. Fortunately, there are many existing Pd libraries and they can be easily installed with Pd's package manager "Deken". The most extensive one is "ELSE" with nearly 500 objects, containing everything from band-limited ocillators, filters, sequencers, GUIs, etc. Personally, I have my own collection of abstractions that I made over the last years. That being said, I would agree that you should always pick the right tool for the job. Just as you wouldn't write your website in C, you wouldn't pick Pd for typical EDM stuff (unless you have a very good reason). But for prototyping and experimental electronics it's a fantastic tool, I think.