5 Jun
2014
5 Jun
'14
1:25 p.m.
Goal of this tool is to allow to search for audio plugins and for other
resources types (sampler banks, instrument definitions, probably more)
independently of application, needing it. I'm still thinking about final name
for it, before to publish (since it should support not only plugins, but also
instruments), and unsure even where to create home page for it (will describe
in bottom).
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.
Currently there is one implemented way to select plugins: dragging. Drag
object is some resource URL, which should be enough for drag receiver to
exactly find pointed resource. But unlike file managers, it is threated as
text - text editors just paste it instead of try to open and konsole - same,
instead of to ask, what to do, as it always does for dropped files. Of course,
applications are free, how to threat such resources, and apps could check for
content before to decide, what to do with it - i.e., check, is it url, etc.
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).
Proposals about drag object format and url types for each resources are
welcomed. I have idea, how to implement for ladspa/dssi, but unsure for lv2.
Currently there are following formats:
LADSPA: ladspa:/<path to library>/<label>
DSSI: same, but begining with "dssi:/"
LV2: lv2 plugin url (i don't know, is it possible to load plugin from specific
library, and they recommend to identify plugins only by URL - at least
remember URL's for database, used across sessions).
Not implemented:
Just have to learn VAMP and somehow try VST - for some completeness.
For soundfonts, gig banks, and instrument definitions there may be same way as
for ladspa/dssi. Sampler banks mode should be handy for
linuxsampler/fluidsynth gui, not providing any instrument browser (qsampler
doesn't have it, and linuxsampler database supports only gig format).
Screenshot: http://wstaw.org/m/2014/06/05/plasma-desktopau6238.png
About publishing. I have account on savannah, and want to publish it there.
But i'm going to add vst support, and i'm not sure, is it possible (even if
licensing is kept, how about fact itself, that it supports this feature)?
5 Jun
5 Jun
3:08 p.m.
New subject: Standalone resources browser - mockup, near of publishing, need discussion
On Thu, Jun 5, 2014 at 7:25 AM, Zlobin Nikita <cook60020tmp(a)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.
6 Jun
6 Jun
12:29 a.m.
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(a)mail.ru> wrote:
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.
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.
12:36 a.m.
New subject: Standalone resources browser - mockup, near of publishing, need discussion
On Thu, Jun 5, 2014 at 6:28 PM, Zlobin Nikita <cook60020tmp(a)mail.ru> wrote:
What do you mean by filtering? If some plugin type is
not supported by drag
target, than it obviously should reject it.
i guess i don't understand what you're attempting to do.
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.
let me restate that. the whole design of audio analysis plugin APIs has
important differences when compared with processing plugin APIs, even
though they overlap to some extent.
most notable: the output of a VAMP plugin is NOT audio (nor any streaming
data of any kind at all).
5 Jun
5 Jun
11:10 p.m.
Pushed: https://repo.or.cz/w/resorg.git
Goal of this tool is to allow to search for audio
plugins and for other
resources types (sampler banks, instrument definitions, probably more)
independently of application, needing it. I'm still thinking about final
name for it, before to publish (since it should support not only plugins,
but also instruments), and unsure even where to create home page for it
(will describe in bottom).
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.
Currently there is one implemented way to select plugins: dragging. Drag
object is some resource URL, which should be enough for drag receiver to
exactly find pointed resource. But unlike file managers, it is threated as
text - text editors just paste it instead of try to open and konsole - same,
instead of to ask, what to do, as it always does for dropped files. Of
course, applications are free, how to threat such resources, and apps could
check for content before to decide, what to do with it - i.e., check, is it
url, etc.
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).
Proposals about drag object format and url types for each resources are
welcomed. I have idea, how to implement for ladspa/dssi, but unsure for lv2.
Currently there are following formats:
LADSPA: ladspa:/<path to library>/<label>
DSSI: same, but begining with "dssi:/"
LV2: lv2 plugin url (i don't know, is it possible to load plugin from
specific library, and they recommend to identify plugins only by URL - at
least remember URL's for database, used across sessions).
Not implemented:
Just have to learn VAMP and somehow try VST - for some completeness.
For soundfonts, gig banks, and instrument definitions there may be same way
as for ladspa/dssi. Sampler banks mode should be handy for
linuxsampler/fluidsynth gui, not providing any instrument browser (qsampler
doesn't have it, and linuxsampler database supports only gig format).
Screenshot: http://wstaw.org/m/2014/06/05/plasma-desktopau6238.png
About publishing. I have account on savannah, and want to publish it there.
But i'm going to add vst support, and i'm not sure, is it possible (even if
licensing is kept, how about fact itself, that it supports this feature)?
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev
3747
days inactive
3747
days old
linux-audio-dev@lists.linuxaudio.org
4 comments
2 participants
participants (2)
-
Paul Davis -
Zlobin Nikita