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

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Zlobin Nikita <cook60020tmp@...>
Cc: linux-audio-user <linux-audio-user@...>, linux-audio-dev@lists.linuxaudio.org <linux-audio-dev@...>
Date: Thursday, June 5, 2014 - 1:09 pm

--001a11c16878bc0b3904fb167120
Content-Type: text/plain; charset=UTF-8

On Thu, Jun 5, 2014 at 7:25 AM, Zlobin Nikita wrote:

>

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

indeed.

> Not implemented:

VAMP is not a realtime plugin API. VAMP plugins are for feature analysis
not audio processing.

--001a11c16878bc0b3904fb167120
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Jun 5, 2014 at 7:25 AM, Zlobin Nikita &lt=
;cook60020tmp@mai=
l.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 w=
here the host has its own reasons to filter the list presented to the user.=

=C2=A0
Dragging to jack patchbay canvas may be used to load plugin in single host<=
br>
(not sure, what about instrument, since there is usually separate sampler
engine, usually managing all instruments).<=
div>indeed.

Not implemented:
Just have to learn VAMP and =C2=A0somehow try VST - for some completeness.<=
br>VAMP is not a realtime plugin API. VAMP=
plugins are for feature analysis not audio processing.=C2=
=A0

--001a11c16878bc0b3904fb167120--

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [LAD] Standalone resources browser - mockup, near of pub..., Paul Davis, (Thu Jun 5, 1:09 pm)