Introduce ladspa::Adapter and GVerb unit - #82
Open
markandrus wants to merge 1 commit into
Open
Conversation
markandrus
marked this pull request as ready for review
December 5, 2025 14:00
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces a mod for LADSPA units. Build it like this:
There is an adapter, ladspa::Adapter, and a sample GVerb unit copied from Steve Harris' LADSPA plugins. It would be interesting to port the remainder of Steve Harris' plugins and the CMT Library Plugins. Are there any other good LADSPA plugin sources?
Also, I believe the LADSPA_Descriptor contains enough information to generate the GVerb.cpp and GVerbUnit.lua. I don't know what this would look like yet…
Warning
I think this approach may have licensing problems. The LADSPA header is LGPL, which AFAIK can be statically linked in er-301 builds; but GVerb and the adapter are GPL, which AFAIK cannot. If these were built and loaded separately, I think it would not be a problem.
Note
I started working on a version of this that will dynamically load pre-compiled LADSPA plugins (
dlopen). That should resolve the licensing problems, and also improve maintainability.Building for and testing on the hardware
I built it for the hardware by running
makein Docker (thanks, @tmfset, for the image):After testing it, I see the GVerb unit takes approximately 15% of CPU (the CPU was at 5% before I loaded the GVerb unit):
er-301-ladspa-gverb.mov