audacity does not play a sound since Gutsy upgrade
Bug #162594 reported by
Timmie
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.
Changed in audacity: | |
importance: | Undecided → Low |
status: | New → Confirmed |
To post a comment you must log in.
Check if anything else has the sound device file open. card0/pcm0p/ info
less /proc/asound/
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)