Comment 407 for bug 371897

(In reply to comment #228)

>
> That is not true for the obvious reasons even a non-programmer can understand.
> Here are some "pictures" of the path that the audio data have to travel on a
> PulseAudio-enabled system when using different Wine subdrivers:
>
> winealsa:
> [App]->[Wine]->[Pulse compatibility layer for ALSA]->[Pulse]->[Sound Backend,
> most probably ALSA or OSS kernel driver]
>
> wineopenal:
> 1st variant: [App]->[Wine]->[OpenAL-soft]->[OpenAL PulseAudio
> backend]->[Pulse]->[SB]
> 2nd variant: [App]->[Wine]->[OpenAL-soft]->[OpenAL ALSA backend]->[Pulse ALSA
> compat]->[Pulse]->[SB]
>
> winepulse:
> [App]->[Wine]->[Pulse]->[SB]
>

the correct topology is

[winealsa]:
[App] -> [Wine] -> [winealsa] -> [Alsa driver] -> [Sound card]

wineopenal:
[App] -> [Wine] -> [openal-soft] -> [Alsa driver] -> [Sound card]

winepulse:
[Appl] -> [Wine] -> [winepulse] -> [PA server] -> [Alsa driver] -> [Sound card]