OK …
This LV2 works in REAPER on my RPi 5, but when installed Ardour fails to open .
Shuts down on scanning LV2s . When I remove the plugins files manually Ardour opens as supposed .
Need help here .
/ T .
OK …
This LV2 works in REAPER on my RPi 5, but when installed Ardour fails to open .
Shuts down on scanning LV2s . When I remove the plugins files manually Ardour opens as supposed .
Need help here .
/ T .
The plugin doesn’t conform to the LV2 specification, in ways which Ardour checks and Reaper does not.
There is a proposed change that someone has made which would handle this, but we are debating whether we should adopt this, or ask the plugin developer to do things the right way.
Is it at least possible to fix the part where Ardour just falls over and won’t open?
Yes. You still won’t be able to use the plugin though ![]()
That’s fine, I’m not particularly in favor of Ardour working around dodgy plugins, but at least if Ardour doesn’t crash you can figure out which plugin didn’t scan properly and know that you can’t use it.
I agree that you should not do this. Fixing YOUR code to accept a 3rd party bug usually will ALWAYS bite you on the ass eventually. Fixing the source is always the correct solution.
While attempting to fix a recent bug in my FreeFactory project, I spent 3 days trying to track down a bug, then I wrote many lines of code in an attempt to fix a (later discovered) simple typo. DOH! Boy did I feel like a complete big dumbass! ![]()
The next release will stop us from crashing when loading ToobAmp (due to its use of a non-URI based extension).