Fons Adriaensen wrote:
On Fri, May 14, 2004 at 05:55:07PM +0200, Marcus Andersson wrote:
Alfons Adriaensen wrote:
Another point. I've defended the adoption of simple integer enumerations
(corresponding to a C switch) using the argument that it is the single
missing essential feature in the
On Fri, May 14, 2004 at 10:50:31PM +0100, Steve Harris wrote:
> I dont really see the avantage of this - control and description are
> seperate tasks, and not even closely related.
Very closely related if you consider that the ultimate purpose of a
description is to control something. Why should
On Fri, May 14, 2004 at 02:21:46PM -0400, Paul Davis wrote:
> >> stable library interface. I don't know anyone now who *ever* writes X
> >> protocol code, and I've never met anyone (except a few people I once
> >> knew who worked on a commercial X server, and even that was more than
> >> 15 years a
On Fri, May 14, 2004 at 02:48:18 -0500, Jack O'Quin wrote:
> Steve Harris <[EMAIL PROTECTED]> writes:
>
> > *cough* its not my scheme, its a W3C standard.
>
> That's nice. How about a pointer to where it's defined?
NTriples is defined in
http://www.w3.org/TR/rdf-testcases/#ntriples
General RDF
On Fri, May 14, 2004 at 02:46:19 -0500, Jack O'Quin wrote:
> Libxml2 is even bigger, almost a meg. I wonder how many LADSPA hosts
> already use it for some other reason? I see that ardour, jamin and
> hydrogen do...
I do really like XML - it's probably saved me more programming time than
another
On Fri, May 14, 2004 at 11:28:42 +0200, Fons Adriaensen wrote:
> For example:
>
> ( stands for the unique name of a plugin)
>
> //addport
> //port//range 0 10
> //port//default 5
> //port//unit octaves
>
> This is a trivial example of course, for a real format we'll have to
> think ab
On Fri, May 14, 2004 at 04:03:55PM -0400, Dave Robillard wrote:
> On Fri, 2004-05-14 at 14:09, Fons Adriaensen wrote:
> > > I suppose the question is _why_ would you "fiercely resist" this good
> > > design practise?
> >
> > System interfaces are often defined by an API (and even that is
> > quest
On Fri, May 14, 2004 at 08:10:32PM +0100, Steve Harris wrote:
> On Fri, May 14, 2004 at 07:07:59 +0200, Fons Adriaensen wrote:
> > On Fri, May 14, 2004 at 12:01:01PM -0400, Paul Davis wrote:
> > > >I don't mind *IFF* the metadata file has a simple, human readable
> > > >syntax (no XML please) that
On Fri, 2004-05-14 at 14:09, Fons Adriaensen wrote:
> > I suppose the question is _why_ would you "fiercely resist" this good
> > design practise?
>
> System interfaces are often defined by an API (and even that is
> questionable since it imposes a language), but file formats and
> network protoc
jaromil <[EMAIL PROTECTED]> writes:
> would have been a good choice since the beginning, to have it as a lib?
Maybe so. But, it's important to keep this in perspective.
LADSPA has been a great success, and simplicity was one of the main
reasons. Now that the concept is proven, people are willi
Fons Adriaensen <[EMAIL PROTECTED]> writes:
> On Fri, May 14, 2004 at 11:31:01AM -0500, Jack O'Quin wrote:
>
> > I'm having trouble figuring out Fons' original point here, though I'm
> > sure he has one. Simple and human readable are worthwhile goals, but
> > hard to reconcile.
>
> Strange.. I'
Steve Harris <[EMAIL PROTECTED]> writes:
> *cough* its not my scheme, its a W3C standard.
That's nice. How about a pointer to where it's defined?
--
joq
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
re,
On Fri, May 14, 2004 at 08:17:30PM +0100, Steve Harris wrote:
> On Fri, May 14, 2004 at 05:45:58 +0100, Mike Rawes wrote:
> > > Will it be possible for the same plugin to implement both v1 and
> > > v2?
> > >
> > > (I would have thought that was
On Fri, May 14, 2004 at 05:45:58 +0100, Mike Rawes wrote:
> > Will it be possible for the same plugin to implement both v1 and v2?
> >
> > (I would have thought that was probably a necessity, but then I don't write
> > plugins.)
>
> Ooh. That's a good point...
>
> I've written a few plugins, an
On Fri, May 14, 2004 at 05:08:53 +0100, Mike Rawes wrote:
> Minor nitpick regarding what is carried over as metadata from 1.x: Can we get
> rid of the label? - I never did see the use for it. The ID is sufficient for
> identifying plugins, and the name (as metadata) for presenting in a UI.
Actuall
On Fri, May 14, 2004 at 12:45:34 -0400, Paul Davis wrote:
> >Why rule out XML? It's one of the few widely-used language groups
> >that actually sorta meets both those requirements (*fairly* simple and
> >*somewhat* human-readable). ;-)
>
> Reactions to XML can be as strong as your feelings about
On Fri, May 14, 2004 at 07:07:59 +0200, Fons Adriaensen wrote:
> On Fri, May 14, 2004 at 12:01:01PM -0400, Paul Davis wrote:
> > >I don't mind *IFF* the metadata file has a simple, human readable
> > >syntax (no XML please) that can be parsed line by line.
> >
> > no XML, and yes, parsable line by
>> stable library interface. I don't know anyone now who *ever* writes X
>> protocol code, and I've never met anyone (except a few people I once
>> knew who worked on a commercial X server, and even that was more than
>> 15 years ago).
>
>This is irrelevant. Xrm has nothing to do with the X protoca
On Fri, May 14, 2004 at 01:19:11PM -0400, Paul Davis wrote:
> >On Fri, May 14, 2004 at 12:01:01PM -0400, Paul Davis wrote:
> >> >I don't mind *IFF* the metadata file has a simple, human readable
> >> >syntax (no XML please) that can be parsed line by line.
> >>
> >> no XML, and yes, parsable line
On Fri, May 14, 2004 at 01:15:37PM -0400, Dave Robillard wrote:
> On Fri, 2004-05-14 at 13:07, Fons Adriaensen wrote:
> > > no XML, and yes, parsable line by line, and yes, human readable. *but*
> > > the plan should be to use the supplied library to get and set
> > > values. nobody should be doing
On Fri, May 14, 2004 at 11:31:01AM -0500, Jack O'Quin wrote:
> I'm having trouble figuring out Fons' original point here, though I'm
> sure he has one. Simple and human readable are worthwhile goals, but
> hard to reconcile.
Strange.. I'd think these two would go hand in hand...
Whit 'simple' a
>On Fri, May 14, 2004 at 12:01:01PM -0400, Paul Davis wrote:
>> >I don't mind *IFF* the metadata file has a simple, human readable
>> >syntax (no XML please) that can be parsed line by line.
>>
>> no XML, and yes, parsable line by line, and yes, human readable. *but*
>> the plan should be to use t
On Fri, 2004-05-14 at 13:07, Fons Adriaensen wrote:
> > no XML, and yes, parsable line by line, and yes, human readable. *but*
> > the plan should be to use the supplied library to get and set
> > values. nobody should be doing it themselves otherwise we end up with
> > an almighty mess.
>
> ??? N
--- Chris Cannam <[EMAIL PROTECTED]> wrote: > On Friday 14 May 2004
15:33, [EMAIL PROTECTED] wrote:
> > we should make sure that the v2plugin metadata contains a hint which
> > v1 plugin is made obsolete by this v2plugin
>
> Will it be possible for the same plugin to implement both v1 and v2?
>
On Fri, May 14, 2004 at 04:53:53PM +0100, Steve Harris wrote:
> Yes, but xrm misses most of the desirable feaures of metadata languages
> (agreed semantics, extensibility and so on). We could just use the syntax,
> but its pretty complex for non-X11 apps that want to parse it.
Actually, it's very
On Fri, May 14, 2004 at 12:01:01PM -0400, Paul Davis wrote:
> >I don't mind *IFF* the metadata file has a simple, human readable
> >syntax (no XML please) that can be parsed line by line.
>
> no XML, and yes, parsable line by line, and yes, human readable. *but*
> the plan should be to use the sup
>Why rule out XML? It's one of the few widely-used language groups
>that actually sorta meets both those requirements (*fairly* simple and
>*somewhat* human-readable). ;-)
Reactions to XML can be as strong as your feelings about C++ :)
Personally, I am fan of both of them, but I don't think tha
On Fri, May 14, 2004 at 05:55:07PM +0200, Marcus Andersson wrote:
> Alfons Adriaensen wrote:
>
> >Another point. I've defended the adoption of simple integer enumerations
> >
> >(corresponding to a C switch) using the argument that it is the single
> >missing essential feature in the port informat
Steve Harris <[EMAIL PROTECTED]> writes:
> On Fri, May 14, 2004 at 04:50:31 +0200, Alfons Adriaensen wrote:
> > I don't mind *IFF* the metadata file has a simple, human readable
> > syntax (no XML please) that can be parsed line by line.
>
> Human readable and line by line parsable are pretty muc
--- Paul Davis <[EMAIL PROTECTED]> wrote:
> well, it appears that there is little to no response to the proposal
> from the LADSPA meeting at ZKM. just to be sure that the silence is an
> accurate reflection of what people think, i want to take a harsh
> stance on the proposal and see if it gener
>I don't mind *IFF* the metadata file has a simple, human readable
>syntax (no XML please) that can be parsed line by line.
no XML, and yes, parsable line by line, and yes, human readable. *but*
the plan should be to use the supplied library to get and set
values. nobody should be doing it themsel
Alfons Adriaensen wrote:
Another point. I've defended the adoption of simple integer enumerations
(corresponding to a C switch) using the argument that it is the single
missing essential feature in the port information. At the Karlsruhe BOF
it was said that this is not true, as the LOGARITHMIC hi
On Fri, May 14, 2004 at 04:50:31 +0200, Alfons Adriaensen wrote:
> I don't mind *IFF* the metadata file has a simple, human readable
> syntax (no XML please) that can be parsed line by line.
Human readable and line by line parsable are pretty much mutually
exclusive - try expressing any complex st
On Friday 14 May 2004 15:33, [EMAIL PROTECTED] wrote:
> we should make sure that the v2plugin metadata contains a hint which
> v1 plugin is made obsolete by this v2plugin
Will it be possible for the same plugin to implement both v1 and v2?
(I would have thought that was probably a necessity, but
On Fri, May 14, 2004 at 08:36:24AM -0400, Paul Davis wrote:
> well, it appears that there is little to no response to the proposal
> from the LADSPA meeting at ZKM. just to be sure that the silence is an
> accurate reflection of what people think, i want to take a harsh
> stance on the proposal and
On Fri, May 14, 2004 at 08:36:24AM -0400, Paul Davis wrote:
> well, it appears that there is little to no response to the proposal
> from the LADSPA meeting at ZKM. just to be sure that the silence is an
> accurate reflection of what people think, i want to take a harsh
> stance on the proposal an
Paul Davis <[EMAIL PROTECTED]> writes:
> personally, i think its worth going through this pain. we will end up
> with a system in which new LADSPA extensions do not require changes to
> the API, which is a great thing. but it will be painful to get there,
> and i want to check that people don't mi
well, it appears that there is little to no response to the proposal
from the LADSPA meeting at ZKM. just to be sure that the silence is an
accurate reflection of what people think, i want to take a harsh
stance on the proposal and see if it generates any response...
if we follow through with the
Dear all,
after the successful 2. Linux Audio Conference, ZKM has offered to host the
conference again next year. We have now fixed the date for the event:
3. Linux Audio Conference
21.-24. April 2005
ZKM, Karlsruhe, Germany
Detailed "Call for papers" and "Call for music"
Hi,
msAlsaSeq, an ALSA driver for the Linux version of Grame's MidiShare
(http://www.grame.fr/MidiShare/), is now available in MidiShare cvs
(http://www.grame.fr/MidiShare/SCPP/dev.html). You can find it in the
development branch (-r dev) in the src/linux/drivers/alsa directory.
The driver let
40 matches
Mail list logo
