Re: [Jack-Devel] JACK in Chrome !!

PrevNext  Index
DateTue, 15 Jan 2013 23:30:22 +0100
From Stéphane Letz <[hidden] at grame dot fr>
ToAdrian Knoth <[hidden] at drcomp dot erfurt dot thur dot de>
Ccjack-devel <[hidden] at lists dot jackaudio dot org>
In-Reply-ToAdrian Knoth Re: [Jack-Devel] JACK in Chrome !!
Follow-UpSam Mulvey Re: [Jack-Devel] JACK in Chrome !!
Le 15 janv. 2013 à 22:45, Adrian Knoth a écrit :

> On 01/15/2013 10:24 PM, ∴ triune . wrote:
> 
>> https://sites.google.com/a/chromium.org/dev/chromium-os/chromiumos-design-docs/cras-chromeos-audio-server
>> The Chrome developers are adding a jack/pulseaudio
>> server to Chrome.
> 
> They are not. They borrow some concepts from pulseaudio and jackd, but
> they're effectively writing yet another audio server.
> 
> Some people would argue that the world doesn't need new audio servers,
> others would encourage them to try new ideas.
> 
> If they succeed, this might turn out as the long-awaited merge of
> pulseaudio and jack, that is, an approach similar to CoreAudio where
> consumer and producer apps share the same audio subsystem.
> 
> Let's see.
> 
> Jack-Devel mailing list
> [hidden]
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org


I really don't see the point.. It seems to me that their need is exactly the purpose of PulseAudio no? Moreover if their audio server is going to "take the audio card" (possibly a exclusive manner right?) how other audio applications (PA based or JACK based...) are going to work at the same time? Or do they want this new audio server to completely replace everything? A new audio API (!?!)

Hum....

Stéphane
PrevNext  Index

1358289033.1923_0.ltw:2, <4CCA1178-80C2-4A46-AA2E-A461C9E95D3A at grame dot fr>