Comment 352 for bug 371897

Revision history for this message
In , Rotbart van Dainig (rotbart-van-dainig) wrote :

(In reply to comment #239)
> It is the reality of it, though.

That doesn't make it less pointless.

(In reply to comment #239)
> It's also the reason why arts and esd died.

Not really - both were superseded by Phonon and PulseAudio... after quite some time. Of course, wine continues to drag the corpses of winearts and wineesd around, refusing to let go, too.

(In reply to comment #239)
> wineopenal would fix that, but you reject that idea.

I don't reject the idea, I reject the fact that until this happens, wine on systemes with PulseAudio has broken sound:
If wine throws away all of the sound drivers anyway later up the road, there is no point in not merging winepulse now, use it as a stop-gap solution, then ditch it with all the rest.

> "sudo aptitude purge pulseaudio" or equivalent is not difficult.

Which just breaks sound for most of the system and leaves the user to reconfigure one part, then install different packages for sinks for most apps. Easy, rrright.

> No, it's the most pertinent point regarding the necessity of winepulse.

No. It is pointless to ask for the proof of need of a solution to a use case, when it's the only one currently working.

> Since an OpenAL plugin will allow Wine to work with pulse, as soon as serious
> work starts on wineopenal begins then this bug can be CLOSED INVALID.
>
> Or, alternatively, when/if wineopenal gets merged upstream,

..and is working on PulseAudio, indeed.

> (In reply to comment #237)
> > And hardware sound is dead.
>
> Yeah [...]

Thank you for at least agreeing with me on that one. If not now - when you go shopping for a new system, at the very least.