20 Apr
2006
20 Apr
'06
5:30 p.m.
Hi,
It is widely felt that the LADSPA plugins are becoming difficult for
average users to manage due to the number of available plugins and the
many different packages available.
There is also a problem that developers face when managing different
plugins as UniqueIds are not assigned by a central authority so it is
possible that there can be double ups.
I am volunteering my time to code a new web portal with the express
purpose of providing a single place to get all known LADSPA plugins and
packages. It will be hosted at ladspa.linuxaudio.org. it will also serve
as a central automated authority for assigning UniqueIds.
I would like to use this thread to discuss the finer details of the
functionality of the site and how to make a package of all Plugins which
will also be hosted on the site. The site will be run with a MYSQL DB. I
intend to code it in AJAX style with a PHP+MYSQL backend.
It will be a fully automated web portal and administrative interface.
Here are the features:
---------------
- Add new plugin/s via batch or manual upload/insert
- Automated assigning of UniqueIds
- Create complete package tarball automatically
- Administrative interface for managing plugins and developer profiles
etc...
- User friendly frontend with accessibility: css, java, php, html, xml
----------------
I will appreciate your indepth analysis of the best methods to allow the
above features for the portal. At this stage the most important points
to discuss are how to manage the plugins efficiently and with minimal
overhead and assigning UniqueIds automatically.
Cheers.
--
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org/LAU/guide/ - The Linux Audio Users guide
========================================
"Anything your mind can see you can manifest physically, then it will
become reality" - Macka B
20 Apr
20 Apr
5:48 p.m.
On Fri, 2006-04-21 at 02:30 +0700, Patrick Shirkey wrote:
It is widely felt that the LADSPA plugins are becoming
difficult for
average users to manage due to the number of available plugins and the
many different packages available.
There is also a problem that developers face when managing different
plugins as UniqueIds are not assigned by a central authority so it is
possible that there can be double ups.
I am volunteering my time to code a new web portal with the express
purpose of providing a single place to get all known LADSPA plugins and
packages. It will be hosted at ladspa.linuxaudio.org. it will also serve
as a central automated authority for assigning UniqueIds.
I would like to use this thread to discuss the finer details of the
functionality of the site and how to make a package of all Plugins which
will also be hosted on the site. The site will be run with a MYSQL DB. I
intend to code it in AJAX style with a PHP+MYSQL backend.
It will be a fully automated web portal and administrative interface.
Here are the features:
---------------
- Add new plugin/s via batch or manual upload/insert
- Automated assigning of UniqueIds
- Create complete package tarball automatically
- Administrative interface for managing plugins and developer profiles
etc...
- User friendly frontend with accessibility: css, java, php, html, xml
----------------
I will appreciate your indepth analysis of the best methods to allow the
above features for the portal. At this stage the most important points
to discuss are how to manage the plugins efficiently and with minimal
overhead and assigning UniqueIds automatically.
How about a machine-friendly interface for searching and downloading
plugin tarballs (or references to distribution packages) so one could
write a tool like CPAN for LADSPAs? An automated way to download and
install plugins would be really useful if it could be integrated into
software like Om, Ardour, JACK-rack etc. Scenario: you try to load a new
Om patch that you downloaded from the net, you get the message "You
don't have the 'foo' plugin, do you want to install it?", click Yes, and
a few seconds (or minutes) later the plugin is installed and the patch
is loaded.
--
Lars Luthman
PGP key: http://www.student.nada.kth.se/~d00-llu/pgp_key.php
Fingerprint: FCA7 C790 19B9 322D EB7A E1B3 4371 4650 04C7 7E2E
6:01 p.m.
On Thu, 2006-04-20 at 21:48 +0200, Lars Luthman wrote:
How about a machine-friendly interface for searching
and downloading
plugin tarballs (or references to distribution packages) so one could
write a tool like CPAN for LADSPAs?
Wouldn't this have the same problem of poor integration with the
distro's package management that CPAN has? How about just getting the
distros to package all the useful plugins?
Lee
6:08 p.m.
On Thu, 2006-04-20 at 16:01 -0400, Lee Revell wrote:
On Thu, 2006-04-20 at 21:48 +0200, Lars Luthman
wrote:
Thus the references to distribution packages. You could query this
hypothetical LADSPA database for the name of the Mandriva package that
contains the "chief executive oscillator" plugin (caps) or the name of
the Gentoo ebuild for the Mvclpf-4 plugin (mcp-plugins) or, as a
fallback, the URL to a source tarball for a plugin.
--
Lars Luthman
PGP key: http://www.student.nada.kth.se/~d00-llu/pgp_key.php
Fingerprint: FCA7 C790 19B9 322D EB7A E1B3 4371 4650 04C7 7E2E
How about a machine-friendly interface for
searching and downloading
plugin tarballs (or references to distribution packages) so one could
write a tool like CPAN for LADSPAs?
Wouldn't this have the same problem of poor integration with the
distro's package management that CPAN has? How about just getting the
distros to package all the useful plugins? 
21 Apr
21 Apr
4:58 a.m.
On Thu, Apr 20, 2006 at 04:01:17PM -0400, Lee Revell wrote:
On Thu, 2006-04-20 at 21:48 +0200, Lars Luthman
wrote:
Amen!
Asbjørn
How about a machine-friendly interface for
searching and downloading
plugin tarballs (or references to distribution packages) so one could
write a tool like CPAN for LADSPAs?
Wouldn't this have the same problem of poor integration with the
distro's package management that CPAN has? How about just getting the
distros to package all the useful plugins? 
5:14 a.m.
Am Donnerstag, den 20.04.2006, 21:48 +0200 schrieb Lars Luthman:
How about a machine-friendly interface for searching
and downloading
plugin tarballs (or references to distribution packages) so one could
write a tool like CPAN for LADSPAs? An automated way to download and
install plugins would be really useful if it could be integrated into
software like Om, Ardour, JACK-rack etc. Scenario: you try to load a new
Om patch that you downloaded from the net, you get the message "You
don't have the 'foo' plugin, do you want to install it?", click Yes,
and
a few seconds (or minutes) later the plugin is installed and the patch
is loaded.
AFAIK most plugins don't have any dependencies. Is there anything wrong
with distributing them in binary form as a convenience? Just drop them
somewhere in your LADSPA_PATH and you're done. That's what plugins are
meant for, no?
22 Apr
22 Apr
6:57 p.m.
Hi,
Thanks for the feedback so far.
Here are the main concerns for me at this point:
- Can we force a central repository on developers. Would developers
support a Firefox style plugin portal? The site will fail if it requires
manual updating by the site maintainer. The onus would have to be on
each developer to update and add to the repository as they create or
update their code.
- Could we automate the xml schema to remove that hassle for developers?
This would allow changes to be made to the schema without requiring
manual updates for every plugin.
- I think the most effective way to manage and package the repository
would be if each plugin was catalogued independantly. This would allow
for a single package to be created using one install procedure. We could
even go further and provide a daemon/app that could install/update
plugins as they are added to the repository.
I appreciate your thoughts.
Cheers.
--
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org/LAU/guide/ - The Linux Audio Users guide
========================================
"Anything your mind can see you can manifest physically, then it will
become reality" - Macka B
7:21 p.m.
On Sun, 2006-04-23 at 03:56 +0700, Patrick Shirkey wrote:
Hi,
Thanks for the feedback so far.
Here are the main concerns for me at this point:
- Can we force a central repository on developers. Would developers
support a Firefox style plugin portal? The site will fail if it requires
manual updating by the site maintainer. The onus would have to be on
each developer to update and add to the repository as they create or
update their code.
- Could we automate the xml schema to remove that hassle for developers?
This would allow changes to be made to the schema without requiring
manual updates for every plugin.
I think this is something that should be a primary concern addressed
with LADSPA2. There really aren't /that/ many LADSPA plugins around, I
think making LADSPA2 plugins suitable for a repository like this and
just porting plugins is a better plan than having an overly complicated
repository that tries to work around LADSPA1's unsuitability for it.
Plugins having URI's and some sort of standard package format (that
Steve has already proposed) is all that's needed. I personally promise
to port the lesser known unmaintained plugins to LADSPA2 if it will
solve the Big Maintainer-Based Package Problem (which causes
considerable grief in Om land) and make a repository like this possible.
That said, I think an approach like Arch might be best here - with a
standard package format, a plugin "repository" could just be a directory
on a server somewhere and apps could resolve (resolvable) URIs to grab
any plugins they need. Devs could handle their own package
"repositories" rather than be forced to deal with a centralized site, as
I'm sure some of the bigger names would probably rather do.
A central site would still be a good thing though, on the user end of
things.
-DR-
30 Apr
30 Apr
8:52 p.m.
Jan Weil wrote:
Am Donnerstag, den 20.04.2006, 21:48 +0200 schrieb
Lars Luthman:
DSSI ones may do. It depends what toolkit their GUI was written in.
Gordon
How about a machine-friendly interface for
searching and downloading
plugin tarballs (or references to distribution packages) so one could
write a tool like CPAN for LADSPAs? An automated way to download and
install plugins would be really useful if it could be integrated into
software like Om, Ardour, JACK-rack etc. Scenario: you try to load a new
Om patch that you downloaded from the net, you get the message "You
don't have the 'foo' plugin, do you want to install it?", click Yes,
and
a few seconds (or minutes) later the plugin is installed and the patch
is loaded.
AFAIK most plugins don't have any dependencies. Is there anything wrong 
1 May
1 May
7:42 a.m.
On Sun, Apr 30, 2006 at 11:49:32PM +0100, Gordonjcp wrote:
Jan Weil wrote:
Sorry, I missed the earlier message, but many plugins also link to FFTW,
and I wouldn't be supprised to find some that link to DSP libraries.
- Steve
Am Donnerstag, den 20.04.2006, 21:48 +0200 schrieb
Lars Luthman:
DSSI ones may do. It depends what toolkit their GUI was written in. How about a machine-friendly interface for
searching and downloading
plugin tarballs (or references to distribution packages) so one could
write a tool like CPAN for LADSPAs? An automated way to download and
install plugins would be really useful if it could be integrated into
software like Om, Ardour, JACK-rack etc. Scenario: you try to load a new
Om patch that you downloaded from the net, you get the message "You
don't have the 'foo' plugin, do you want to install it?", click Yes, and
a few seconds (or minutes) later the plugin is installed and the patch
is loaded.
AFAIK most plugins don't have any dependencies. Is there anything wrong 
21 Apr
21 Apr
1:24 a.m.
On Apr 20, 2006, at 3:30 PM, Patrick Shirkey wrote:
I am volunteering my time to code a new web portal with the express
purpose of providing a single place to get all known LADSPA plugins
and packages. It will be hosted at ladspa.linuxaudio.org. it will
also serve as a central automated authority for assigning UniqueIds.
I recommend http://drupal.org as a good codebase to start off of.
Taybin
6778
days inactive
6789
days old
linux-audio-dev@lists.linuxaudio.org
10 comments
9 participants
participants (9)
-
Asbjørn Sæbø -
Dave Robillard -
Gordonjcp -
Jan Weil -
Lars Luthman -
Lee Revell -
Patrick Shirkey -
Steve Harris -
Taybin Rutkin