Re: [ecasound] LV2 Plugin Support
Brought to you by:
kaiv
From: Jeremy S. <jer...@gm...> - 2011-10-04 02:49:55
|
Okay, so I did a little more work on it. now trying to test it out. Unfortunately, the git version of ecasound (before I make any changes to it) is giving me... $ echo "ladspa-register" | ecasound -c ******************************************************************************** * ecasound v2.8.1+dev (C) 1997-2011 Kai Vehmanen and others ******************************************************************************** (eca-chainsetup) Chainsetup "untitled-chainsetup" (eca-session) NOTE: Unable to create a valid chainsetup from the command-line arguments. ecasound ('h' for help)> (eca-control) Registered LADSPA plugins: ecasound ('h' for help)> ecasound ('h' for help)> --- ecasound: Exiting... Whereas the Debian package will list all the LADSPA plugins installed on my system with the same command. So at this point, I am a bit troubled as to how I can test my LV2 support, as I have nothing to compare it to. If anyone is interested in seeing what the problem is, I have put up a git repository of my work: https://github.com/jeremysalwen/Ecasound-LV2 the branch "master" is just the current ecasound branch. The branch "LV2" is the one I did work on. You still need to modify lilvmm.hpp if you want it to compile. Just change const char* uri_to_path(const char* uri) { ... to static const char* uri_to_path(const char* uri) {... wherever it is installed in your system. Also, any help with understanding why ecasound won't list the LADSPA plugins when I build it from source would be great. (As a note, I get this error system installed ladspa.h, or the one bundled with ecasound) Jeremy On Mon, Oct 3, 2011 at 9:47 PM, Jeremy Salwen <jer...@gm...>wrote: > Hi, > > Thanks for this email...Otherwise the code probably would have sat around > forever while I contemplated it. > > Basically, I wrote up a preliminary draft of the code, but then I started > to run into issues with how I wanted to use lilvmm. I thought that there > could be a nicer way to wrap the lilv library in C++ objects than is > currently done (and I still believe so today). I started writing up a draft > of my would-be nicer C++ wrapper, but in hindsight, I realize that this is > probably not going to work out for ecasound, 1) because it requires > unique_ptr, which is provided by Boost or C++0x, neither of which you > probably want brought into the ecasound codebase. 2) It would still take a > bit more work and testing to make it ready for prime time. > > So basically, having a shock to my system was enough to make me realize > that I should give up what I was doing (at least temporarily), and implement > LV2 support with manual memory management. > > At this point, a major bug in lilvmm makes it so that it will only link if > I make a modification to a library header... But once I think the basic > functionality is working, I'll release an alpha version. > > Jeremy > > > On Mon, Oct 3, 2011 at 5:10 PM, S. Massy <li...@wo...> wrote: > >> Hello, >> >> Let us know when you're ready for some alpha testing. I'm sure some of >> us would be glad to help. >> >> Cheers, >> S.M. >> >> -- >> > > |