pure-data
scheme-for-pd
pure-data | scheme-for-pd | |
---|---|---|
3 | 8 | |
8 | 63 | |
- | - | |
0.0 | 0.0 | |
about 1 month ago | over 2 years ago | |
C | C | |
GNU General Public License v3.0 or later | BSD 3-clause "New" or "Revised" License |
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.
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...).
-
Show HN: Glicol(Graph-Oriented Live Coding Language) and DSP Lib Written in Rust
FWIW, Pd and Max/MSP always had sample-level control in the sense that subpatches can be reblocked. For example, if you put a [block~ 1] object in a Pd subpatch, the process function will be called for every sample, so you can have single-sample feedback paths. Pd also has the [fexpr~] object which allows users to write FIR and IIR filters in a simple expression-syntax. Finally, Max/MSP offers the very powerful [gen~] object. You can check it out for inspiration (if you haven't already).
Pd (and Max/MSP) also allow to upsample/resample subpatches, which is important for minimizing aliasing (caused by certain kinds of processing, such as distortion).
Pd also uses the reblocking mechanism to implement FFT processing. The output of [rfft~] is just an ordinary signal that can be manipulated by the usual signal objects. You can also write the output to a table, manipulate it in the control domain with [bang~], and then read it back in the next DSP tick. IMO, this is a very powerful and elegant approach. SuperCollider, on the other hand, only supports a single global blocksize and samplerate which prevents temporary upsampling + anti-aliasing, severly limits single-sample feedback and leads to a rather awkward FFT implementation (you need dedicated PV_* objects for the most basic operations, such as addition and multiplication).
Another thing to think about is multi-threaded DSP. With Supernova, Tim Blechmann miraculously managed to retrofit multi-threading onto scsynth. Max/MSP offers some support for multi-threading (IIRC, top level patches and poly~ instances run in parallel). Recently, I have been working on adding multi-threading to Pd (it's working, but still very much experimental): https://github.com/Spacechild1/pure-data/tree/multi-threadin.... If you design an audio engine in 2022, multi-threading should be considered from the start; you don't have to implement it yet, but at least leave the door open to do it at a later stage.
---
I'm not sure how far you want to go with Glicol. I guess for the typical Algorave live coder all these things are probably not important. But if you want Glicol to be a flexible modern audio engine/library, you will have to think about FFT, upsampling, single-sample feedback, multi-processing etc. at some point. My advice is to not leave these things as an afterthought; you should at least think about it from the start while designing your engine - if you want to avoid some of the mistakes that other existing audio engines made. This is just a word of "warning" from someone having spent countless of hours in Pd and SuperCollider source code :-)
-
How a Single Line of Code Made a 24-Core Server Slower Than a Laptop
Great write up!
What I like about Pd is that you can freely reblock and resample any subpatch. Want some section with single-sample-feedback? Just put a [block~ 1]. You can also increase the blocksize. Usually, this is done for upsampling and FFT processing. Finally, reblocking can be nested, meaning that you can reblock to 1024 samples and inside have another subpatch running at 1 sample blocksize.
SuperCollider, on the other hand, has a fixed global blocksize and samplerate, which I think is one of its biggest limitations. (Needless to say, there are many things it does better than Pd!)
---
In the last few days I have been experimenting with adding multi-threading support to Pd (https://github.com/Spacechild1/pure-data/tree/multi-threadin...). With the usual blocksize of 64 sample, you can definitely observe the scheduling overhead in the CPU meter. If you have a few (heavy-weight) subpatches running in parallel, the overhead is neglible. But for [clone] with a high number of (light-weight) copies, the overhead becomes rather noticable. In my quick tests, reblocking to 256 samples already reduces the overhead significantly, at the cost of increased latency, of course.
---
Also, in my plugin host for Pd/Supercollider (https://git.iem.at/pd/vstplugin/) I have a multi-threading and bridging/sandboxing option. If the plugin itself is rather lightweight and the blocksize is small, the scheduling overhead becomes quite noticable. In Pd you can just put [vstplugin~] in a subpatch + [block~]. For the SuperCollider version I have added a "reblock" argument to process the plugin at a higher blocksize, at the cost of increased latency.
scheme-for-pd
-
Best livecoding software if I primarily want to manipulate the MIDI in my DAW
I have also made a pure data version is you need it to be free to run, though that is less full featured. https://github.com/iainctduncan/scheme-for-pd
- Pure Data as a plugin, with a new GUI
- Scheme for Max (and Live) 0.4 beta release up.
- Scheme-y music software
- The Haskell School of Music (book) [pdf]
-
Scheme for Pd 0.1 available as binary packages for OSX and Windows
Scheme for Pd is a Pd port of (most of) Scheme for Max. It enables you to script and live code Pd with s7 Scheme, including working with the scheduler, hot reloading code, and dynamically running Scheme code in Pd built from messages. I'm pretty sure I've done the right thing for win32 and win64, one should be able to download the zip file, expand in your externals directory, add this directory to your Pd file paths, and be good to go. It would be lovely if a windows user can try this out and let me know either way. Project page: https://github.com/iainctduncan/scheme-for-pd Release: https://github.com/iainctduncan/scheme-for-pd/releases/tag/0.1-beta
-
Linux/open source - what to connect orca to?
No, but Pure Data is. I have ported Scheme for Max to PureData as more minimal version, but it's newer and does require building from source. I'll be doing more work on the Pd version over the next few months though, and I'd say 80-90% fo the examples and docs for Scheme for Max work identically (or with very little alteration) on Pd. The Pd project is here: https://github.com/iainctduncan/scheme-for-pd
-
Extension languages?
I just heard about https://github.com/iainctduncan/scheme-for-pd (it seems to be a place holder & a port of the Scheme for Max project)
What are some alternatives?
faustgen-supercollider - Livecode Faust in SuperCollider using an embedded Faust compiler.
plugdata - Pure Data as a plugin, with a new GUI
egui_baseview_test_vst2 - Barebones egui_baseview vst2 plugin with basic parameter control
Orca - Esoteric Programming Language
ddwChucklib-livecode - A live-coding interface for chucklib objects
pd-lua - Lua bindings for Pd, updated for Lua 5.3+
ixilang - A live coding language. An extension to SuperCollider, currently Cocoa only.
scheme-for-max - Max/MSP external for scripting and live coding Max with s7 Scheme Lisp
hvcc - The heavy hvcc compiler for Pure Data patches.
pure-data - Pure Data - a free real-time computer music system
egui_node_graph - Build your node graph applications in Rust, using egui
cl-patterns - Library for writing patterns to generate or process (a)musical sequences of mathematically (un)related (non-)compound values in Lisp.