audacity does not play a sound since Gutsy upgrade

Bug #162594 reported by Timmie
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
audacity (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: audacity

I did a upgrade to gutsy on 10./11.11.2007.
Among others, Audacity was upgraded to 1.3.3-beta. Since that there is no output to my loudspeakers anymore.
I had a slef-compiled beta version (1.3.3) with a execuatble suffix running on feisty along with the stable version on feisty (1.2.6). On feisty both did produce a output.
I set my output device to "Alsa (default)".

I had to switch to the Windows OS to produce my audio files. Therefore a help is needed.

Revision history for this message
Peter Cordes (peter-cordes) wrote :

Check if anything else has the sound device file open.
less /proc/asound/card0/pcm0p/info
and look at subdevices_avail (at the end of the file)
If avail is 0, then something already has your sound card open. (This might not be a problem, depending on the drivers/hardware; e.g. My Intel HDA, w/ Sigmatel STAC9271D codec, shows 1 subdevice, and 0 avail when anything is playing. It allows apparently unlimited stereo output streams (at 48kHz only), or a single multichannel stream at any sample rate.)

You can check what processes have the card open, with
lsof /dev/snd/pcmC0D0p

 I found audacity kept switching to using the digital output of my sound card, which isn't hooked up. But you did say you set it to Alsa (default), which should work.

 Other ALSA programs work for you, right? e.g. aplay, or mplayer -ao alsa, or whatever.
(check with lsof while the programs running to make sure it's opened the sound device directly instead of starting artsd or something)

Revision history for this message
Peter Retief (peterretief-gmail) wrote :

I have had the same problem, many games also stopped working (No sound - could not open device etc)
A productivity killer that gives OS's a bad name - I don't have time to fiddle
I tried the steps above with no success

Peter

Revision history for this message
Peter Cordes (peter-cordes) wrote :

AFAIK, Ubuntu wants everything that outputs sound to go through pulseaudio. (a software mixing daemon). Not everything supports pulse, though, and will find the audio device unavailable if something else already has it open through pulse.

sudo lsof /dev/snd/*

will almost always tell you what process you need to stop to free up the audio device, if you don't want to convert everything to pulseaudio.

 Or I think it's appropriate to report bugs on any program that doesn't/can't use pulseaudio by default.

Revision history for this message
Laurent Dinclaux (dreadlox) wrote :

Same in intrepid.

Revision history for this message
Laurent Dinclaux (dreadlox) wrote :

Hello,

It works using audacity 1.3.6 getdeb.net package.

Please update it in repositories.

Regards

Daniel T Chen (crimsun)
Changed in audacity:
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Fernando Miguel (fernandomiguel) wrote :

this is now fixed in jaunty (for both audacity and PulseAudio)

Revision history for this message
David Henningsson (diwic) wrote :

This problem appears fixed according to the bug comments, settings status accordingly. If the bug can be reproduced on Jaunty, please open a new bug.

Changed in audacity:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.