Here's a case of an upstream dev absolutely not supporting pulseaudio in any way shape or form. Their code specifically disables pulseaudio any time they see it. The devs think there's no reason for pulseaudio to exist, and that it causes unresolvable problems for their goals (specifically regarding sync). Is pulseaudio capable of meeting this application's needs? Is there something on a social/documentation level that's lacking? Are the devs just being unreasonable? The only thing that I see is clear here is that the users of distros that go to pulseaudio are left out in the cold. On Wed, May 19, 2010 at 08:14, MythTV <mythtv at cvs.mythtv.org> wrote: > #8314: Seeking with pulseaudio enabled results in 100% volume > > ---------------------------------------------+------------------------------ > Reporter: Marc Randolph <mrand@?> | Owner: danielk > Type: defect | Status: closed > Priority: minor | Milestone: unknown > Component: MythTV - Audio Output | Version: 0.23rc1 > Severity: medium | Resolution: wontfix > Mlocked: 0 | > > ---------------------------------------------+------------------------------ > Changes (by danielk): > > * status: assigned => closed > * resolution: => wontfix > > > Comment: > > Unless there are patches ready for testing, I'm not fixing any pulse audio > issues. I highly recommend nuking all traces of pulseaudio from any system > where you intend to use audio. > > -- > Ticket URL: <http://svn.mythtv.org/trac/ticket/8314#comment:4> > MythTV <http://www.mythtv.org/> > MythTV > -- Jeremy Nickurak -= Email/XMPP: jeremy at nickurak.ca =- -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20100519/08ebc8cc/attachment.htm>
