(In reply to comment #169)
> Any sound system that's supposed to be configuration-free shouldn't need a wiki
> page like this:
Sure, that's why there is the new Volume Controle in GNOME 2.28, making use of PulseAudio's capability to be reconfigured on runtime.
Give it a try.
(In reply to comment #170)
> Personal opinions about PulseAudio aside, the way to get a PulseAudio driver
> into Wine would be to first fix Wine's audio driver architecture, and implement
> the driver afterwards.
Why would the first part be a prereuisite?
Sure, it's the nice way of doing it, but there are people waiting to use Wine. Those would really apreaciate a stop-gap solution like the working, existing winepulse.drv.
(In reply to comment #169)
> Any sound system that's supposed to be configuration-free shouldn't need a wiki
> page like this:
Sure, that's why there is the new Volume Controle in GNOME 2.28, making use of PulseAudio's capability to be reconfigured on runtime.
Give it a try.
(In reply to comment #170)
> Personal opinions about PulseAudio aside, the way to get a PulseAudio driver
> into Wine would be to first fix Wine's audio driver architecture, and implement
> the driver afterwards.
Why would the first part be a prereuisite?
Sure, it's the nice way of doing it, but there are people waiting to use Wine. Those would really apreaciate a stop-gap solution like the working, existing winepulse.drv.