For questions, answers and opinions
It was somewhat of a exaggeration... But you're also right that the issue is more important then the devs seems to notice...
To be consistent, it should remain as P3 according to the guidelines (because fewer users are affected) . It has less weight than if it was something affecting Windows, or something affecting general usability.grammo wrote:I think it's a P2. The group users who want to use Audacity with Jack are larger then you think... all people on Linux who are working with audio/ music on Gnu/linux should work with Jack... At least if they are taking it serious... And a so also the devs of Audacity should takes this (more) serious IMHO.
I don't know how to do that.Gale Andrews wrote:when people have to shut down sound servers before using Audacity, it's said that setting the conflicting application to use the ALSA default device (as well as Audacity) may let Audacity share the device via dmix. Can JACK be configured like that to solve the ("have to shut JACK first") problem?
Again, please post an message on the linux audio user mailiglist AND on the linux developer mailinglist. Don't be shy, I think they will help you. There are enough people who knows everything about jack, event the developers of jack themselves are on that liststevethefiddle wrote:I don't know how to do that.Gale Andrews wrote:when people have to shut down sound servers before using Audacity, it's said that setting the conflicting application to use the ALSA default device (as well as Audacity) may let Audacity share the device via dmix. Can JACK be configured like that to solve the ("have to shut JACK first") problem?