Add TAP Plugins to the Open Audio Stack registry
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 5
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Hello!
We are curating a list of open-source audio software at [Open Audio Stack](https://github.com/open-audio-stack/open-audio-stack-registry). We've created an open registry and package manager for installing/upgrading audio plugins, apps, presets and projects (think npm/Homebrew, but for audio software). We'd like to include **TAP Plugins**, but it requires a few small changes.
**Requirements checklist:** _(last checked 2026-07-18)_
- [x] License [specified](https://choosealicense.com/appendix/) as a `LICENSE` file, SPDX/REUSE annotations, or a clear statement in the README — GPL-2.0, `COPYING` file present
- [ ] GitHub release with downloadable binaries (zip/tar/exe/dmg/deb — source-only releases don't count), tagged with a fixed date or semantic version — no GitHub releases; LADSPA plugins built from source (`.c` files + `Makefile`) only
- [ ] Preview image in the README or repo — a UI screenshot, or a logo/icon if the project is headless — none found anywhere in the repo
Once everything above is checked off, TAP Plugins can be added automatically — no further action needed from your side beyond that. If any box looks wrong (e.g. we missed an existing license or image), add a comment to this issue and we'll correct it. And if you'd rather this project not be listed at all, feel free to close this issue — we'll leave it alone.
Thanks!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the LADSPA .c files and Makefile to understand how TAP Plugins is built, then check the repository README and GitHub release requirements. Done means providing a dated or semver release with downloadable binaries and adding a preview image to the README or repository so the registry checklist can be completed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- audio-video-rtc, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100