Live-Coding-Toolkit-for-Pure-Data
pure-data
Live-Coding-Toolkit-for-Pure-Data | pure-data | |
---|---|---|
1 | 8 | |
61 | 1,463 | |
- | 2.0% | |
5.5 | 9.7 | |
6 days ago | 1 day ago | |
C | ||
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Live-Coding-Toolkit-for-Pure-Data
-
Pure Data as a plugin, with a new GUI
I had a look at automationism, but don't really like how it imposes the CV concept in an environment where it doesn't make much sense (to me) - but is still fun to fiddle with. I came across a toolkit[1] yesterday which is similar but doesn't impose analogue concepts on the workflow in the same manner. Also not as polished in the GUI sense either mind you, but the guy who wrote it makes really good occasional pd tutorials on youtube as well[2]
[1] https://github.com/algomusic/Live-Coding-Toolkit-for-Pure-Da...
pure-data
-
pure-data VS midica - a user suggested alternative
2 projects | 12 Aug 2023
-
How to get in touch with maintainers in PD - Running PD on phone
Report bugs on the pd github https://github.com/pure-data/pure-data
-
A brief interview with Tcl creator John Ousterhout
You might be interested in clicking through the puredata source code.
https://github.com/pure-data/pure-data
-
Pure Data as a plugin, with a new GUI
> The other advantage is because these things were implemented in the 80s
Pd was developed in the mid 90s
> they are very computationally efficient
Not as efficient as it could be, though. For example, instead of proper SIMD instructions, the DSP perform routines only use manual loop unrolling, praying that the compiler will auto-vectorize it.
Finally, everything is single-threaded, leaving lots of performance on the table. FWIW, I have a PR for an asynchronous task API (https://github.com/pure-data/pure-data/pull/1357) and also a branch for multi-threaded DSP (https://github.com/Spacechild1/pure-data/tree/multi-threadin...).
-
Pure Data: an open source visual language for multimedia
> 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.
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.
- Implementing Cosine in C from Scratch
- [P] Pure Data patch learning and automation