[SUGGESTION] WINE, autodisable/ask to disable PulseAudio

[rautamiekka]

Since PulseAudio causes much trouble alot, why not make WINE to either

• 1) autodisable
  2) ask to disable

PulseAudio when running something ?


By my understanding if this would be implemented, either of the following is done:

• 1) When executing wine theprogramname.exe it first calls to WINE, which then query the system for PA. Then if PA is found, WINE adds padsp to the commandline and continues executing theprogramname.exe

• • (how this technically is done, I'd make WINE to store the wine theprogramname.exe to a string variable, then combine padsp and wine theprogramname.exe string variables into one. Then WINE executes the string variable's content as command)

• 2) When WINE is being installed, the installer query the system for PA. Then if PA is found, the installer adds padsp to each wine theprogramname.exe to make it look like padsp wine theprogramname.exe

Personally I'd prefer the second approach cuz it sounds less resource-hungry.

[Daemon]

Since PulseAudio causes much trouble alot,

then why not disable PA in your system?

/etc/pulse/client.conf
autospawn = no

[rautamiekka]

Since PulseAudio causes much trouble alot,

then why not disable PA in your system?

/etc/pulse/client.conf
autospawn = no

Not bad idea of yours, but it again requires either an Admin or an user to perform that.

[Cloudef]

/etc/pulse/client.conf
autospawn = no

That disables all processes autospawning, i would do rather

Code: Select all

sudo apt-get remove pulseaudio
sudo apt-get install esound

[Lockywolf]

>>sudo apt-get install esound

Why?

What do you use a sound server for?

Once i discovered dmix, i removed all sound servers. Just don't need them.

[PleegWat]

rautamiekka wrote:

Since PulseAudio causes much trouble alot, why not make WINE to either
1) autodisable
2) ask to disablePulseAudio when running something ?


By my understanding if this would be implemented, either of the following is done:
1) When executing wine theprogramname.exe it first calls to WINE, which then query the system for PA. Then if PA is found, WINE adds padsp to the commandline and continues executing theprogramname.exe(how this technically is done, I'd make WINE to store the wine theprogramname.exe to a string variable, then combine padsp and wine theprogramname.exe string variables into one. Then WINE executes the string variable's content as command)2) When WINE is being installed, the installer query the system for PA. Then if PA is found, the installer adds padsp to each wine theprogramname.exe to make it look like padsp wine theprogramname.exe

Personally I'd prefer the second approach cuz it sounds less resource-hungry.

You can do this yourself, by creating a script to override the default
'wine' command.

1) In your home directory, create a directory called 'bin' (may already
exist)
2) In that directory, create a file (script) called 'wine', and make it
executable
3) Give that file the following contents:

#!/bin/sh
padsp /usr/local/bin/wine "$@"

Now, whenever the 'wine' command is run, your version is used instead of
the standard 'wine' command. To verify your version is being used, enter
'type wine' on the command line.

PleegWat

[Freakazo]

Is all the pulseaudio problems caused by the poor way pulseaudio is installed with some distributions (like ubuntu)?

Wouldn't it be more helpful if wine recommends you to a guide if it detects that pulse audio isn't set up correctly?

[oiaohm]

Ok pasuspender in theory should work. Problem it don't. Wine depend on the existence of a Mixer. Under alsa this is a just presume. Because if a video card does not have a mixer dmix is there to be loaded instead.

Developer of pulseaudio has refused to fix the pasuspender script by the way.

Problem pulseaudio is a mixer when you double stack two mixers you get crap performance. So to have pulseaudio enabled distribution disable alsa dmix. Pasuspender does not load dmix if sound card has no mixer. So wine has issues. That is why pasuspender works with some sound cards and not others. Any sound card with a built on mixer pasuspender removes wine problem. So a magic script wrapping pasuspender to load dmix when its required would truly fix the problem. Bar upsetting users that there pulseaudio system turns into a paper weight.

Next padsp with wine use oss link problem oss part of wine does not support a huge number of applications. So it nothing more than a hack that only sometimes works.

Pulseaudio has cpu and crashing under load usage problems that cause programs to have unstable runtime performance even when they have pulseaudio drivers. That pulseaudio developers are trying to fix buy the way. No sane distribution should have it active by default.

So basically we screwed nothing is going to make pulseaudio users happy every path is broken somewhere. Either we disable or remove pulseaudio or have other errors from pulse that users fail to detect as a pulseaudio failure not a wine one.

[oiaohm]

I don't know why I got video and sound mixed up for a moment but it does make a good laugh.

[John Drescher]

Is all the pulseaudio problems caused by the poor way pulseaudio is installed with some distributions (like ubuntu)?

This is not about poor installation and more about an instability in
pulseaudio itself.

John