[CinCV TNG] Audio VST plugins

Sam cinelerra at posteo.de
Mon May 14 11:36:45 CEST 2018

If such a test were technically feasible, it would be a good solution 
for Cinelerra and the users.

I tend to create an interface to Ardour via Jack or ALSA. As you say, 
Ardour has a lot of possibilities and a working GUI. The automatic LV2 
plugin test in Cinelerra would not be necessary because they would be 
outsourced and covered by Ardour.  All LV2 plugins could be integrated 
via Ardour. It's just an idea of mine if it would be technically 
feasible the developers have to decide.

Good Guy can certainly say more on this subject.


On 14.05.2018 10:05, Olaf wrote:
> You guys seem to misunderstand me. I hope it's just the translation.
> I don't (!) expect Cinelerra to include every single LV2 plugin in the development and to modify it manually. The plugins usually come in large packages (like Debian), there is something for everyone. I haven't tried many of them yet. Setting an "LV2_PATH={directory of "good" LV2 plugins}" would mean that the user has root privileges and re-sorts the package maintainer's given paths. Why should the user do this - provided the user is able to do so - when Ardour (in conjunction with Xjadeo) is already a comfortable graphical tool for sound recording and post-processing of films?
> Frankly, I don't understand why you guys want to make life difficult for yourselves. A simple test at runtime, i.e. during the start, true to the motto: "work / doesn't work" is perfectly sufficient. The plugin that doesn't work (with Cinelerra) is simply discarded. That's all I expect, I think that's quite enough.
> With best regards
> _______________________________________________
> Cinelerra mailing list
> Cinelerra at lists.cinelerra-cv.org
> http://lists.cinelerra-cv.org/cgi-bin/mailman/listinfo/cinelerra

More information about the Cinelerra mailing list