vst3_public_sdk
delimited
vst3_public_sdk | delimited | |
---|---|---|
2 | 2 | |
127 | 2 | |
4.7% | - | |
4.0 | 10.0 | |
11 days ago | about 8 years ago | |
C++ | C++ | |
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.
vst3_public_sdk
-
How hard is it to make a VST plugin? Whether a instrument or effect.
This is an example of one source file in an sample VST - https://github.com/steinbergmedia/vst3_public_sdk/blob/master/samples/vst/note_expression_synth/source/note_expression_synth_processor.cpp
-
Declarative, non-intrusive, compile-time C++ reflection for audio plug-ins
> it does generate something compatible with VST2.x and I've been working on VST3 this week-end (and pulling a few hairs, that API is horrendous, the smallest example is a few thousand lines of codes).
Oh that is awesome!!!
If you want a tip about the smallest possible VST3 implementation, (and maybe you already know this) there is a class called "SingleComponentEffect", and an example called "AGainSimple" that uses it and is a fully self-contained single file full VST3 plugin:
https://github.com/steinbergmedia/vst3_public_sdk/search?q=s...
Also, I spent some time trying to get VST3 SDK usable with vcpkg so you could just do:
// vcpkg.json
delimited
-
Monoio – A thread-per-core Rust async runtime with io_uring
Oh, I have written my own share of userspace C context switching libraries, I know all the gory the details :). For example see my minimalist [1] stackful coroutine library: the full context switching logic is three inline asm instructions (99% of the complexity in that code is to transparently support throwing exceptions across coroutine boundaries with no overhead in the happy path).
You need compiler help for the custom calling convention support and possibly to optimize away the context switching overhead for stackful coroutines, which is something that compilers can already do for stackless coroutines.
The duff device is just a way to simulate stackless coroutines (i.e. async/await or whateverer) in plain C, in a way that the compiler can still optimize quite well.
[1] https://github.com/gpderetta/delimited/blob/master/delimited...
-
Declarative, non-intrusive, compile-time C++ reflection for audio plug-ins
Using gcc extended asm you can pass literal constants to the asm and they will be expanded textually (or at least their address will). I don't think the details are fully documented anywhere and I had to use intel syntax to make it work, but it might be possible even wit AT&T syntax.
Take a look a this[1] for example. See how trampoline, the destructor and the size are passed in with the 'i' constraint and are referred to their value with the %cX constraint (yes, the code is write only and even with a lot of comments I have only the most vague idea of what I was trying to do here).
Probably more work is require for PIC though.
[1] https://github.com/gpderetta/delimited/blob/7e755d643ee45897...
What are some alternatives?
DPF - DISTRHO Plugin Framework
actix-net - A collection of lower-level libraries for composable network services.
essentia - C++ library for audio and music analysis, description and synthesis, including Python bindings
wg-async - Working group dedicated to improving the foundations of Async I/O in Rust
Vcpkg - C++ Library Manager for Windows, Linux, and MacOS
monoio - Rust async runtime based on io-uring.
q - C++ Library for Audio Digital Signal Processing
Fundamental
vst3sdk - VST 3 Plug-In SDK