[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Considering ConsoleKit and GSettings/DConf
From: |
Halim Sahin |
Subject: |
Considering ConsoleKit and GSettings/DConf |
Date: |
Thu, 12 Aug 2010 20:49:41 +0200 |
Hello,
On Do, Aug 12, 2010 at 02:27:27 -0400, Trevor Saunders wrote:
> Hi,
>
> > >>so important, but with ALSA and other audio output methods,
> > >>it's crucial since we block everyone else.
> > >Yes this is correct because the _mainstream_ soundserver uses the
> > >hardware directly and doesn't communicate over alsa's dmix
> > >infrastructure.
> > >If someone would add this options to the distros main soundconfiguraton,
> >
> > The reason why PulseAudio can't go through dmix is technical.
> > It couldn't get the timing right, and it does the job better than dmix.
> > At least the algorithm is better, I have my doubts about the current
> > implementation :)
>
> this is a pulse issue, but just no. That's not ok error handling. if pulse
> wants to
> do creepy things that mean it has an exclusive lock on alsa that's fine, but
> if
> it can't get that lock it *can* still work, it can fallback to using dmix. I
> would think the pulse developers would realize that suboptimal functioning is
> better than not at all.
Yeah. subscribe to their list and give them some sugestions.
I won't spent my time with this stuff any more.
Before you start with the operation read this:
http://www.mail-archive.com/pulseaudio-discuss at mail.0pointer.de/msg05948.html
Gru?
halim
- Considering ConsoleKit and GSettings/DConf, (continued)
Considering ConsoleKit and GSettings/DConf, Halim Sahin, 2010/08/11