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

PrevNext  Index
DateWed, 16 Jan 2013 11:21:50 +0100
From Adrian Knoth <[hidden] at drcomp dot erfurt dot thur dot de>
To[hidden] at lists dot jackaudio dot org
In-Reply-ToPatrick Shirkey Re: [Jack-Devel] JACK in Chrome !!
Follow-UpPatrick Shirkey Re: [Jack-Devel] JACK in Chrome !!
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.

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.


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.


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



Cheers

-- 
mail: [hidden]  	http://adi.thur.de	PGP/GPG: key via keyserver
PrevNext  Index

1358331717.10600_0.ltw:2,a <20130116102150.GR28562 at ltw dot loris dot tv>