Kargo automates promotion across dev, staging, and prod with approval gates and verification. Open source, built by the team behind Argo CD. Download now. Learn more →
Top 23 C Plugin Projects
-
> Having separate parameter queues for sample-accurate automation requires plugins to treat their parameters in a very specific way (basically, you need audio-rate buffers for your parameter values that are as long as the maximum host block) in order to be written efficiently.
Oh I forgot about parameters. In VST3, the parameter changes use linear interpolation. So the DAW can predict how the plugin would interpret parameter value between changes and use this to create the best piece-wise linear approximation for automation curve (not merely sampling the curve every N samples uniformly which is not perfect).
CLAP has no defined interpolation method, and every plugin would interpolate the values in its own, unique and unpredictable way (and if you don't interpolate, there might be clicks). It is more difficult for a host to create an approximation for an automation curve. So with CLAP "sample-precise" might be not actually sample-precise.
I didn't find anything about interpolation in the spec, but it mentions interpolation for note expressions [1]:
> A plugin may make a choice to smooth note expression streams.
Also, I thought that maybe CLAP should have used the same event for parameters and note expessions? Aren't they very similar?
> duped's comment about needing to create "dummy" parameters which get mapped to MIDI CCs is spot-on as well. JUCE does this. 2048 additional parameters (128 controllers * 16 channels) just to receive CCs. At least JUCE handles those parameters sample-accurately!
What is the purpose of this? Why does plugin (unless it is a MIDI effect) need values for all controllers? Also, MIDI2 has more than 128 controllers anyway so this is a poor solution.
[1] https://github.com/free-audio/clap/blob/main/include/clap/ev...
-
Kargo
Stop Scripting Promotions. Start Shipping with Kargo. Kargo automates promotion across dev, staging, and prod with approval gates and verification. Open source, built by the team behind Argo CD. Download now.
-
-
-
I've used [batch editing in GIMP before](https://github.com/alessandrofrancesconi/gimp-plugin-bimp), to resize a folder of images, so the feature is there. Granted it is a plugin, not a built-in feature.
I do agree though, even the revamped UI does not have a great look and feel, but I'm used to it so I don't mind.
-
-
-
-
AppSignal
Monitoring that respects your time & budget. APM, error tracking, and dashboards for modern web apps. Ten-minute setup, transparent flat pricing, and support from engineers who actually use the product.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
C Plugin discussion
C Plugin related posts
-
Gimp Source Code
-
Postgres Webhooks with Pgstream
-
Tired of This
-
Streaming on Linux: Beginner
-
what this hole do?
-
Is there really no way to edit all layers at once? Do I seriously have to make colour corrections on every single individual layer?
-
On the performance of REPLICA IDENTITY FULL in Postgres
-
A note from our sponsor - Kargo
akuity.io | 11 Sep 2026
Index
What are some of the best open-source Plugin projects in C? This list will help you:
| # | Project | Stars |
|---|---|---|
| 1 | clap | 2,340 |
| 2 | wal2json | 1,511 |
| 3 | vlc-pause-click-plugin | 1,188 |
| 4 | gimp-plugin-bimp | 1,014 |
| 5 | obs-gstreamer | 402 |
| 6 | dlfcn-win32 | 342 |
| 7 | slack-libpurple | 289 |
| 8 | ds4vita | 182 |
| 9 | obs-vaapi | 145 |
| 10 | LuaScript | 129 |
| 11 | rep | 111 |
| 12 | BigFiles | 54 |
| 13 | SecurePad | 45 |
| 14 | 8BitVita | 43 |
| 15 | ifavif | 42 |
| 16 | Manhunt.PluginMH | 37 |
| 17 | joysens | 27 |
| 18 | xfce4-kbdleds-plugin | 27 |
| 19 | plugin-gimp-fourier | 27 |
| 20 | sqlite-wlx | 25 |
| 21 | ifjxl | 22 |
| 22 | quick_breakpad | 20 |
| 23 | matrixmixer.lv2 | 10 |