>Yep, but sockets allow audio and other data to be streamed between machines,
>very useful live in a studio. The point is that different exchanges are
>suitable for different contexts.
Agreed. But JACK connects clients on the same host. There is nothing
to stop one of those clients having its ow
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Paul Davis
> Sent: 02 October 2001 23:12
[...]
> >Yep, but SHM isn't the only answer. Sockets provide a particularly useful
> >implementation.
>
> Sockets still force a data copy and they are bandwidth
>With respect I don't think Ardour could be made a plugin of *anything* ;) .
with respect, it already is :) the AudioEngine loads it as a shared object.
>As for JACK vs LADMEA within GStreamer, I'm still sitting on the fence as to
>which will be implemented first. The obvious answer is which fr
> >I'm not sure I agree here - I think the GStreamer team has a
> better grasp of
> >the real issues here than most. And by the way, why can't
> Ardour be turned
> >into a GStreamer plugin? The GStreamer team would probably
> appreciated the
> >changes required to make that happen.
With respec
>Yep, but SHM isn't the only answer. Sockets provide a particularly useful
>implementation.
Sockets still force a data copy and they are bandwidth limited as well
AFAIK. They also don't offer RT characteristics. Try to write a lot
of data to a socket, and the kernel will do a bunch of
non-determ
nt: 02 October 2001 21:31
> To: [EMAIL PROTECTED]
> Subject: RE: [linux-audio-dev] LADMEA revisited (was: LAAGA and
> supporting programs)
>
>
> On Tue, 2 Oct 2001, Richard W.E. Furse wrote:
>
> > > -Original Message-
> > [...]
> > > It i
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Paul Davis
> Sent: 30 September 2001 19:02
> To: [EMAIL PROTECTED]
> Subject: Re: [linux-audio-dev] LADMEA revisited (was: LAAGA and
> supporting programs)
>
>
> First of
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Paul Davis
> Sent: 01 October 2001 17:32
> To: Richard Guenther
> Cc: [EMAIL PROTECTED]
> Subject: Re: [linux-audio-dev] LADMEA revisited (was: LAAGA and
> supporting program
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Karl
> MacMillan
> Sent: 29 September 2001 23:37
> To: [EMAIL PROTECTED]
> Subject: Re: [linux-audio-dev] LADMEA revisited (was: LAAGA and
> supporting programs)
[...]
> It i
Richard Guenther wrote:
> I never looked into JACK, I just know LAAGA and Arts and what Richard
> posted about LAMEDA. JACK is the one used within Ardour?
I suppose 'lame' wasn't intentional ;)
Anyway, I - as a person with no votes - vote for the current path of
developmen
>I never looked into JACK, I just know LAAGA and Arts and what Richard
>posted about LAMEDA. JACK is the one used within Ardour?
JACK is the new name for LAAGA. People seem to like it better than
LAAGA, and I'm a person too :)
Ardour currently uses the AudioEngine to interact with audio h/w,
whi
>What Paul is voting for is to have just one "protocol" (at least for now),
>so we can drop the need for B and magically A turns (with some additional
>static cruft from the missing B) out to be LAAGA (or whatever).
>
>Richard is voting to have both APIs to allow maximum flexibility.
As insightfu
>I haven't kept up with the specifics of these design discussions, but it
>sounds like your goals are very close to the goals of the BeOS Media Kit.
>Have you read the Media Kit's documentation and API, and if so, have
>they influenced your design at all? If you haven't read them before,
>they're
>I haven't kept up with the specifics of these design discussions, but it
>sounds like your goals are very close to the goals of the BeOS Media Kit.
>Have you read the Media Kit's documentation and API, and if so, have
>they influenced your design at all? If you haven't read them before,
>they're
* Paul Davis ([EMAIL PROTECTED]) wrote:
> Lets just briefly review the goals here: we want streaming media
> (audio, MIDI, video, whatever) to be able to talk to each other.
I haven't kept up with the specifics of these design discussions, but it
sounds like your goals are very close to the goals
First of all, I'd like to thank Richard for his insightful and very
useful email. The LADMEA header file didn't make clear to me what his
concerns were; this email has.
>The essential idea is to extend from approaches like LAAGA/JACK, GStreamer
>or aRts where there is an all-encompassing audio in
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Paul Davis
> Sent: 28 September 2001 13:33
> To: [EMAIL PROTECTED]
> Subject: Re: [linux-audio-dev] LAAGA and supporting programs
>
>
> >When can we expect LAAGA to be stable enough (API-wise) and be su
17 matches
Mail list logo
