On Fri, Jul 19, 2002 at 11:31:32 +0200, Torben Hohn wrote:
> Well i consider the big parsers the bloat...
> XML is a great idea.
But they are dynamicaly linked, and so many things link against libxml
anyway...
> So you say i can implement support for the default hints ???
Yes, I allready promi
---
Torben Hohn --- [EMAIL PROTECTED]
- Original Message -
From: "Steve Harris" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, July 19, 2002 10:42 AM
Subject: Re: [linux-audio-dev] LADSPA Defaults via RDF
> On Fri, Jul 19, 2002 at 05:11:06
On Fri, Jul 19, 2002 at 05:11:06 +0200, Torben Hohn wrote:
> Please leave the default hints in the native-API. I only want an instatiated
> plugin to produce sound.
> Which is generally not the case when my defaults are 0 :-(
No, well thats what were trying to fix. it is definatly a problem.
> I
On Fri, Jul 19, 2002 at 11:56:02 +1000, Conrad Parker wrote:
> sure, this would only be for author-defined defaults, which would
> assumedly be minimal and available through getDefault(), and thus
> implicitly available on any architecture the plugin is available on.
Well, I'm currently planning
On Wed, Jul 17, 2002 at 12:37:00PM +0100, Steve Harris wrote:
> On Wed, Jul 17, 2002 at 10:28:10 +1000, Conrad Parker wrote:
> > My concerns are:
> > * bloat -- requiring all LADSPA hosts to link against libxml and
> ...
> > * licensing -- requiring all LADSPA hosts to link to GPL code
>
On Fri, Jul 19, 2002 at 05:11:06AM +0200, Torben Hohn wrote:
>BTW:
>I consider XML to be bloat.
At least it is portable bloat ;)
No, seriously, xml has advantages over plain ascii,
when you consider xslt, rdf, ... etc etc
regards
vini
> On Wed, Jul 17, 2002 at 06:49:05 +0200, Richard Guenther wrote:
> > Hi Steve!
> >
> > I really like it! Also it opens up a lot of other possibilities in the
> > future like GUI hints, etc.
>
> Yes, it should also provide a tree of plugin categories, but I haven't
> defined that yet.
>
> So, t
On Wed, Jul 17, 2002 at 08:26:53 +0200, Richard Guenther wrote:
> Thought the other comment was against dropping "native" defaults support
> with ladspa v1.1, not against RDF in general. As you noted RDF will be
> useful for stuff v1.1 does not handle, such as
> - presets
> - categories
> - exchan
On Wed, 17 Jul 2002, Steve Harris wrote:
> On Wed, Jul 17, 2002 at 06:49:05 +0200, Richard Guenther wrote:
> > Hi Steve!
> >
> > I really like it! Also it opens up a lot of other possibilities in the
> > future like GUI hints, etc.
>
> Yes, it should also provide a tree of plugin categories, bu
Steve Harris wrote:
> On Wed, Jul 17, 2002 at 06:49:05 +0200, Richard Guenther wrote:
>
>>Hi Steve!
>>
>>I really like it! Also it opens up a lot of other possibilities in the
>>future like GUI hints, etc.
>
>
> Yes, it should also provide a tree of plugin categories, but I haven't
> defined th
On Wed, Jul 17, 2002 at 06:49:05 +0200, Richard Guenther wrote:
> Hi Steve!
>
> I really like it! Also it opens up a lot of other possibilities in the
> future like GUI hints, etc.
Yes, it should also provide a tree of plugin categories, but I haven't
defined that yet.
So, that seems to be one
Hi Steve!
I really like it! Also it opens up a lot of other possibilities in the
future like GUI hints, etc.
Richard.
On Tue, Jul 16, 2002 at 06:44:59PM +0100, Steve Harris wrote:
> OK, I now have a minimal proof of concept for describing LADSPA plugins,
> presets and defaults with RDF (http://
On Wed, Jul 17, 2002 at 10:28:10 +1000, Conrad Parker wrote:
> For plugin (author-defined) defaults, I really can't see how any use of
> RDF/XML can be a good thing -- we really should be moving towards defining
> a getDefault() method in the API, and even dynamic parameter suggestions.
N.B. that
Hi Steve, all,
For plugin (author-defined) defaults, I really can't see how any use of
RDF/XML can be a good thing -- we really should be moving towards defining
a getDefault() method in the API, and even dynamic parameter suggestions.
My concerns are:
* bloat -- requiring all LADSPA hos
OK, I now have a minimal proof of concept for describing LADSPA plugins,
presets and defaults with RDF (http://w3c.org/RDF).
At this point I'd like to get some feedback so I can decide wether to cut
my losses or finish it (a usable library for hosts would be about another
weeks work, on and off).
15 matches
Mail list logo
