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

On Wed, January 16, 2013 9:21 pm, Adrian Knoth wrote:
> On Wed, Jan 16, 2013 at 02:58:53PM +1100, Patrick Shirkey wrote:
>
>> Here's my response on the chromium-os-discuss list:
>>
>> https://groups.google.com/a/chromium.org/forum/?fromgroups=#!topic/chromium-os-discuss/IHN8gzMfeLw
>
> Which is wrong on so many levels.
>
> Mostly, because the draft is about ChromeOS, not Linux in general.
>

ChromeOS runs on the Linux Audio stack. Further abstraction of the linux
Audio Stack is not necessary to achieve their goals.

> Second, because they don't want JACK, they just want to leverage JACK's
> concept of a callback-driven audio API. So your whole point of
> pulseaudio/jack integration is completely invalid.
>

I can understand that they may not want to deal with maintaining ongoing
support for pulse audio due to the large amount of deps that are required
to get it to compile. However that should not stop them from using JACK.

>
> They need some abstraction layer to route chrome-internal audio streams
> to different devices. They can do this with pulseaudio, but maybe they
> want something more lightweight, e.g., something with a chrome-internal
> HTML5 frontend.
>

Pulseaudio can be controlled with an html5 frontend. If that;s all they
want then why do they need to reinvent the Audio stack to achieve it?

>
> Those of us who understand the technical details might contribute an
> advice or two, but otherwise, this is none of other business.
>

Are you patronising me or just being rude?



--
Patrick Shirkey
Boost Hardware Ltd

1358347899.6518_0.ltw:2,a <54723.5.12.188.139.1358347892.squirrel at boosthardware dot com>