[LAD] Standalone resources browser - mockup, near of publishing, need discussion

Zlobin Nikita cook60020tmp at mail.ru
Thu Jun 5 22:28:58 UTC 2014

What do you mean by filtering? If some plugin type is not supported by drag 
target, than it obviously should reject it.

> On Thu, Jun 5, 2014 at 7:25 AM, Zlobin Nikita <cook60020tmp at mail.ru> wrote:
> > As for plugins: currently each audio application has own plugin browser.
> > In
> > some cases it is very handy (ingen, carla), sometimes awful (audacity, may
> > be
> > more). My hope is to make it external with filemanager-like workflow.
> then you'd better be considering cases where the host has its own reasons
> to filter the list presented to the user.
> > Dragging to jack patchbay canvas may be used to load plugin in single host
> > (not sure, what about instrument, since there is usually separate sampler
> > engine, usually managing all instruments).
> indeed.
> > Not implemented:
> > Just have to learn VAMP and  somehow try VST - for some completeness.
> VAMP is not a realtime plugin API. VAMP plugins are for feature analysis
> not audio processing.

And about realtime - some processing plugins are not marked as realtime-
capable (TAP plugins), as well as RT may be used for non-realtime work.

Any sample editor, like audacity, mhwaveedit, could also accept them for non-
realtime operations. Btw, hopely, there could appear even video plugins. Of 
course, if there are some standards appart gstreamer plugins.

More information about the Linux-audio-dev mailing list