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

You've almost capture what I was about to add, Sam:

In ChromeOS, the only thing talking to the sound card is Chrome... you
can't install any local apps (apps in the traditional sense... not web
apps). So, there is no contention between different apps, just Chrome. At
the moment, all they are doing is having Chrome talk to the ALSA driver.
So, this is a step up from that very simple implementation.

On Tue, Jan 15, 2013 at 5:33 PM, Sam Mulvey <[hidden]> wrote:

>
> On Jan 15, 2013, at 2:30 PM, Stéphane Letz wrote:
>
> 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....
>
>
> If this is the ChromeOS in the new chromebooks, I think the idea is that
> there aren't going to be a lot of applications requesting the sound card,
> and most of it is going to be stuff written for ChromeOS.    For the most
> part, ChromeOS is just enough of an operating system to run the browser.
>
> -Sam
>
> 
> Jack-Devel mailing list
> [hidden]
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
>
> --
> ∴*triune.*
> <http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org>

1358289658.2866_0.ltw:2,a <CADcjGi5vidnNqYgZo-_ZPwth_X00_=1D3YgkVC5pnnAJTVkQrw at mail dot gmail dot com>