** Changed in: audacity
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/687689
Title:
Audacity ruins bluetooth
To manage notifications about this bug go to:
Closed due to no response.
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/687689
Title:
Audacity ruins bluetooth
To manage
Thank you for reporting this bug to Ubuntu.
Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: pulseaudio (Ubuntu)
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: portaudio (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/687689
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pulseaudio (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/687689
Title:
I mean audacity can just list the devices, and user can decide if it
should used and probed.
I think this would be a good idea. Also, I *think* the current
recommendation is to use snd_device_name_hint API over the
snd_config_xxx API for device list enumeration.
This may also speedup the
Launchpad has imported 3 comments from the remote bug at
http://bugzilla.audacityteam.org/show_bug.cgi?id=270.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
Thanks for your reply. Sorry it took so long for mine. And I apologize
for my negative tone before. I was pretty irritated at the time and it
was rude.
I am pleased to say that with a fresh install of the 11.04 Ubuntu Alpha
3 release I was able to try out bluetooth again on my new PC and it
seems
Part of the problem is Audacity using snd_config_xxx api:s to enumerate
devices, then tries to open all of them in all ways possible.
Try temporarily move /usr/share/alsa/bluetooth.conf somewhere else, so it can't
be used, then reboot your computer.
Is bluetooth now working both before and after
Response from upstream (Richard Ash):
(Note using the abbreviation PA is highly confusing - please don't).
Jack is I'm fairly sure irrelevant to this discussion. The core is that
Audacity actively probes all available ALSA devices, which upsets the
tower-of-babel that has been built on top of
2. Fix the ALSA emulation in PulseAudio and Ubuntu's ALSA configuration so
that
what Audacity does is acceptable and doesn't crash things. This might include
hiding the real ALSA devices so only the faked ones are visible, and ensuring
that the full ALSA API works (or at least doesn't crash
** Bug watch added: Audacity Bugzilla #270
http://bugzilla.audacityteam.org/show_bug.cgi?id=270
** Also affects: audacity via
http://bugzilla.audacityteam.org/show_bug.cgi?id=270
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
12 matches
Mail list logo
