I agree with Stefan, but I don't know enough about the process here to make the decision to make a new bug.
Stephen Irons's description is exactly right (at least for my problem). I don't know if it is related to the original bug or not. Probably it should be its own bug since it happens with or without PulseAudio (I don't have PulseAudio installed on my box). Incidently, the problem seems to be known upstream: http://audacityteam.org/forum/viewtopic.php?f=18&t=128 but I don't think anything has been done about it. >From my perspective, jackd should *not* be run by audacity if jack has not been selected as a device. If the user changes from jackd to another device, then jackd should be killed if it was started from audactiy. If it was not started from audacity, it should tell the user to stop the demon before it tries (and fails) to open the device. If audacity starts jackd there should be a way of setting the sample rate in audacity. It also should not let the user pick sample rates that aren't available. So lots of small bugs working together to create the situation where anyone with jackd installed almost certainly won't be able to use audacity (which is ironic given that jackd is the preferred method). -- Audacity does not mesh with PulseAudio https://bugs.launchpad.net/bugs/178895 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
