[LAD] Standalone resources browser - mockup, near of publishing, need discussion
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@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] Standalone resources browser - mockup, near of publishing, need discussion
On Thu, Jun 5, 2014 at 7:25 AM, Zlobin Nikita cook60020...@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. ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
[LAD] Open Source Audio Meeting in Cologne, Germany (User Group)
Dear musicians, programmers and normal people, I plan to create a user group, a regular meeting, in my home town Cologne, in Germany. The first meeting ever will be already on June 18th, 19:00. After that every two month or so. There are more dates on the website (see below). Here is a brief website with all the necessary information. http://cologne.linuxaudio.org/ (Any language is welcome but the chances are that most people will be from the area and therefore speak German. So the page is in German) If you intend to come you can put your name on this etherpad, but this is not required. Anybody can show up. http://yourpart.eu/p/linuxaudio-cologne Topics will be unorganized QA, showing off programs and music, sharing knowledge and tips and hopefully one day shorter or longer presentations, tutorials, workshops etc. I expect most people to use Linux but any OS is welcome, therefore I named it just Open Source Audio and not Linux Audio. So if you are in the area please join us! If you are not in the area but know people in the area, please tell them. Greetings, Nils http://cologne.linuxaudio.org/ http://www.nilsgey.de P.S. Despite the domain saying linuxaudio.org this is an independently and privately organized event. It is not intended to replace or get in conflict with the Linux Audio Conference. ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] Standalone resources browser - mockup, near of publishing, need discussion
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@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] Standalone resources browser - mockup, near of publishing, need discussion
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 cook60020...@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. ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] Standalone resources browser - mockup, near of publishing, need discussion
On Thu, Jun 5, 2014 at 6:28 PM, Zlobin Nikita cook60020...@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). ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
[LAD] Yet another io GNU/Linux iso released
Hi, A new 64bit iso is up ;) io GNU/Linux is a Live DVD/USB based on Debian Sid and focused on multimedia. Kernel 3.14.4, Jack2 as default sound server, e18 as desktop environment and a big collection of installed software... Full persistence for USB install (with encryption) and more cool stuff... A great nomade studio :) For more infos: manual, packages list, screenshots, video etc... Check: - http://manu.kebab.free.fr/iognulinux.html - https://sourceforge.net/projects/io-gnu-linux/ Feedbacks welcome, enjoy :) MK signature.asc Description: This is a digitally signed message part. ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
