<br><br><div class="gmail_quote">On Wed, Sep 28, 2011 at 5:17 AM, Mark Brown <span dir="ltr"><<a href="mailto:broonie@opensource.wolfsonmicro.com">broonie@opensource.wolfsonmicro.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Wed, Sep 28, 2011 at 10:02:49AM +0100, Colin Guthrie wrote:<br>
> 'Twas brillig, and Taylor Hutt at 27/09/11 21:56 did gyre and gimble:<br>
> > Hello folks,<br>
<br></div></blockquote><div><br><snip><br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">
</div><br><div class="im">
> > Since we have decided not to use Pulse, prior to my time, it seemed<br>
> > prudent to continue with that decision.<br>
<br>
> I'll be blunt. This is a mistake. Revisit it. Do your own evaluation. We<br></div></blockquote><div><br>That's not bad advice, but it's not always prudent. <br><br>In this case, I am part of a team working to make a shipping product, and there are time constraints which <br>
do not afford the time necessary to do that, _and_ to make forward progress to get the sound system working <br>across a constantly increasing variety of hardware. <br><br>The door has not categorically closed on Pulse for all time, but it has closed for the time being. <br>
We've got a lot of work to get Chromium and Chromium OS to a point where ship with the desired features, and<br>I don't presently have the time to re-investigate Pulse across our set of hardware.<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
> > As far as I understand it,<br><div class="im">
> > Pulse also doesn't cope well with dynamic devices -- it's more suited to<br>
> > a desktop system than to a system which will have devices dynamically<br>
> > inserted & removed.<br>
<br>
> This is a grave misunderstanding. PA copes *very* well with dynamic<br>
> devices. It's one of the key parts of what we do. Policy modules allow<br></div></blockquote><div></div><div></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">
> things to happen automatically (for example when I have a voip stream<br></div></blockquote><div></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">
> and I enable my bluetooth headset, a policy module kicks in and knows<br>
> that I want voip on bluetooth. This is all customisable, but at the end<br>
> of the day, this is very much a key part of the platform.<br>
<br></div></blockquote><div><br>Can you explain how Pulse copes with devices that have not been seen before and <br>for which no configuration has been written?<br><br>Does Pulse work with HDMI audio and video?<br></div>
<div><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im"><br>
> This is good news as it means you still have time to make the right<br>
> decision. I strongly suggest you take some time to read up a bit more<br>
> about PA and chat to us about it.<br>
<br></div></blockquote><div><br>Point me to the definitive documentation, please.<br><br>thutt<br></div></div>