hvcc
pure-data
hvcc | pure-data | |
---|---|---|
3 | 8 | |
350 | 1,463 | |
- | 2.0% | |
0.0 | 9.7 | |
7 months ago | 1 day ago | |
Python | C | |
GNU General Public License v3.0 only | 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.
hvcc
-
Pure Data as a plugin, with a new GUI
Also check this project:
https://github.com/enzienaudio/hvcc
The heavy hvcc compiler for Pure Data patches. Very useful for working with embedded devices, which is also my current focus.
-
What frustrates you?
There was this https://github.com/enzienaudio/hvcc
-
Is anyone using and programming the Electrosmith Daisy Patch?
FYI, you can't run SuperCollider on microcontrollers, it requires a desktop OS. So usually modules that run it have some SOC with Linux. Also, PureData on MCUs is not the same thing that you run on desktop, it's using a compiler called Heavy that has some restrictions (not every object is supported)
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
What are some alternatives?
spitback - A simple synth and drum machine patch intended for use with libpd
supercollider - An audio server, programming language, and IDE for sound synthesis and algorithmic composition.
MLB-StatsAPI - Python wrapper for MLB Stats API
plugdata - Pure Data as a plugin, with a new GUI
Oscilloscope-Mushrooms - Getting Started with Pure Data: Oscilloscope Mushrooms
PureeData - PuréeData is a browser-based GUI interface for a remote PureData server, allowing real-time collaborative patching for anyone, anywhere.
TypeRig - Proxy API and Font Development Toolkit for FontLab
wefx - Basic WASM graphics package to draw to an HTML Canvas using C. In the style of the gfx library
catwiki - CatWiki is a simple wiki that stores its articles as text files
musl - unofficial musl mirror git://git.musl-libc.org/musl
vfjLib - A low-level VFJ reader and writer.
v7unix - Version 7 Unix for a POSIX world