On 02/06/2010 10:58 PM, fons@xxxxxxxxxxxxxxx wrote: > On Sat, Feb 06, 2010 at 10:23:24PM +0000, Rui Nuno Capela wrote: > >> in pure plugin sense, ardour is the host and it will care for all midi >> and audio handling, internally. thus, you won't see any jack client nor >> ports associated to the linuxsampler as a plugin, be that through >> qjackctl or any other jack-aware patchbay application, afaics. > > I don't know how the LS 'plugin' integrates in Ardour3, > but things don't have to be as you describe. > > Even if something is loaded from an .so and thus > runs in the host's process, that does not imply > that it has to use the host's audio infrastucture, > or anything else provided by the host. > > As an example, I have a collection of Jack apps > (Ambdec, Jconvolver, Jkmeter, and some others that > I've not (yet) released as standalone apps) that > are implemented as Python classes. You can use > them in Python scripts, or interactively as I > often do. Like all C/C++ extensions for Python > they are just an .so that gets loaded by an > 'import' statement, and then you create as many > instances as you need. > > So technically these are plugins. But each of them > is a separte Jack client, there is no common audio > infrastructure apart from Jack. Those that do have > a GUI are also a separate X11 client each. > yes, that's correct. i was referring to plugins in the "pure" aka "traditional" sense, like ladspa, vst, dssi or lv2. as a standalone jack client, linuxsampler should be available all the time. you just talk to its lscp server via tcp to provide all the jack client and port devices you want. however, Dave has already mentioned that it's the lv2 plugin he's tallking about. so i guess infrastructure is supplied by the lv2 host here, ardour not jack. byee -- rncbc aka Rui Nuno Capela rncbc@xxxxxxxxx _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
