On Mon, 2010-06-28 at 21:22 +0100, Chris G wrote:
..... but there's no sound, which is rather fundamental for a phone application! And there's no way to diagnose it at all, no simple tests to play a sound, nothing, nada. How is one meant to configure and test sound setup on Linux (Ubuntu 10.04 in this case) with no simple tests to try out.
I've found that simple setups just seem to work but configuring ALSA for something more complicated is just that - complicated.
One of the issues has always been sound card sharing. It seems the default under Linux has always been not to share sound devices so if two application try to open the same output device and play a sound the second one either fails or blocks until the first one finished.
I am running Ubuntu 10.04 too and as initially configured it uses PulseAudio. This means the pulseaudio daemon will open the ALSA playback device and other applications will normally send their output to PulseAudio which will then mix everything together and send in on to ALSA to be played on the sound card.
I don't know twinke so I don't know if it has the option to output to PulseAudio. If so that is probably the easiest answer. If not you could try the mechanism whereby ALSA presents what appears to be a device but actually sends the output to pulse audio. For me if I run aplay -L the first few entries returned are:
null Discard all samples (playback) or generate zero samples (capture) pulse Playback/recording through the PulseAudio sound server front:CARD=NVidia,DEV=0 HDA NVidia, VT1708B Analog Front speakers
So it would be trying 'pulse' as an ALSA destination name in the twinkle config.
You could also run a test to see if paplay can play a simple WAV file.
Steve.