[pulseaudio and 0ad on linux]

Not really sure what is going on, but looks like an OpenAL-alsa-Pulseaudio problem.

AL lib: alsa.c:388: Could not open playback device 'alsa': No such file or directory

SND| alc_init: success, using OSS Software

Maybe better to set OpenAL to use OSS directly with "drivers = oss". With "drivers = pulse" 0 ad will not start at all (black screen).

There is a bug track here suggesting to upgrade alsa. I will try later.

Edit: No I will not try. As far as it works really well with the "drivers = oss" there is no problem.

[pulseaudio and 0ad on linux]

Ok solved problem with crackling. Crystal clear sound now all the way.

following this guide:

In the terminal:

sudo gedit /etc/openal/alsoft.conf

change the divice line form Alasa backend stuff to this:

## ALSA backend stuff

##

[alsa]

## device:

# Sets the device name for the default playback device.

device = alsa

remember to un coment it.

Hope this helps.

[pulseaudio and 0ad on linux]

Hello all. My first post on forum

I also have problems with sound and popling/crackling using Ubuntu (Karmic).

First I got error:

bt_audio_service_open: connect() failed: Connection refused (111)

popling/crackling and then no sound.

Also I got low fps problem running the game.

I did:

sudo apt-get install libasound2-plugins padevchooser libsdl1.2debian-pulseaudio

sudo apt-get purge bluez-alsa

After reboot sitation is a bit better. I got rid of the "Connection refused (111)" message and low fps complaints. The sound is still crackling but it does not shut down. Also the sound becomes clear if I do nothing, and if I for instance click a unit crackling starts. (?)

I am not familiar with 0 A.D. and do not know how the audio pipe goes (sdl? connection to libasound2.so?). So stumbling and try to learn

Please bear with me....

Guess the "bt" in "bt_audio_service_open" refers to bluetooth?