Bug 449012
Summary: | audacity does not play sound | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Nadav Kavalerchik <nadavkav> |
Component: | pulseaudio | Assignee: | Lennart Poettering <lpoetter> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 8 | CC: | bugs.michael, lkundrak, pierre-bugzilla, rdtennent |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-11-26 11:27:36 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Nadav Kavalerchik
2008-05-29 21:23:23 UTC
compiling PulseAudio server 0.9.10 from sources did not solve this issue. (although i got some other improvements from upgrading, but this is besides the point :-) i opened a bug report upstream : http://www.pulseaudio.org/ticket/301 and requested support for PortAudio be added to PulseAudio. http://www.pulseaudio.org/ticket/300 Please retry with the newer Audacity from the updates-testing repo. https://admin.fedoraproject.org/updates/search/audacity I rebuilt an audacity-1.3.2 rpm using --with-portaudio=v19 --without-portmixer, as suggested in the audacity wiki to enable native ALSA support. This produces sound. Bob T. PortAudio v19 is the default. The wiki instructions you refer to are for Audacity 1.2.x, where PortAudio v19 was experimental. Please rebuild with upstream defaults and retest. One thing you could also try is building with JACK support to see whether that damages anything. I rebuilt audacity-1.3.2 adding just --with-mp3 --with-libmad=system. I got sound output from audacity but only when running as root. Running sudo audacity produced an error box complaining about needing a temporary directory. After I created that directory, audacity produced sound even as a non-root user. I don't understand what this means. "try building with JACK support" How do I do that? It's not a configure option. The LIBS variable has -ljack. If I do sudo jackd -d alsa before starting audacity, I get the error message "Error while opening sound device ..." when I try to play something. > I rebuilt audacity-1.3.2 adding just --with-mp3 --with-libmad=system
Such an rpm is provided at rpmfusion.org (or livna.org) and
contains both 1.3.2-beta and 1.3.5-beta in the same package.
It's called audacity-nonfree.
Enabling the mp3 decoder doesn't have any influence on
PortAudio v19 I/O.
JACK support is built in if you install "jack-audio-connection-kit-devel".
The upstream developers think about disabling it in the future,
as it doesn't get any/enough testing.
I'd just like to find out what exactly you think you changed
to fix anything. There is no special support for PulseAudio in
Audacity.
I've had jack-audio-connection-kit-devel installed all along. But if jackd -d alsa is running, audacity produces "Error while opening sound device ... " if I try to play anything. Running audacity using sudo seems to be problematic because it gets confused about whether the temporary directory it needs is owned by root or the original user. "I'd just like to find out what exactly you think you changed to fix anything." AFAIK it's by running audacity as root! Before that, I didn't get an error message but I didn't get sound either. I can't recall doing anything else that might be relevant. When I get home, I'll experiment on a box that doesn't yet have audacity installed and see if I can duplicate this behavior. "I'll experiment on a box that doesn't yet have audacity installed and see if I can duplicate this behavior." I did. I couldn't. Audacity produced sound immediately (running as a user). I can't explain why I initially got no sound on another system. Bob T. This message is a reminder that Fedora 8 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 8. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '8'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 8's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 8 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping It makes no sense to continue with this ticket. For issues like this reproducibility is the key. |