Gale Andrews wrote:OK, we noticed the "votes" for the "feature requests" about JACK. We have been aware of problems with JACK for a long time, though some of them change subtly with PortAudio updates as Steve says. I do think these issues are closer to bugs than feature requests, and as such, bugs are now best reported by writing to feedback _AT_audacityteam_DOT_org. We add confirmed bugs reported to that address to our Wiki Release Checklist (we no longer track bugs via Bugzilla).
So I have added the JACK issues I know/understand about on the Release Checklist (at the bottom of the "Priority P3" issues). Steve, if you are aware of other reproducible problems with JACK, can you summarise them for me?
As for the feature requests page, please note I removed the feature request about the subject problem with JACK from the "Playback Enhancements" section. This is best handled as a bug, and certainly not best described as a playback enhancement. I''ve left in a more generalised feature request "Full support for application-linking sound servers such as JACK" in the "Recording enhancements" section, as (possibly) the most appropriate place:
http://audacityteam.org/wiki/index.php? ... hancements
I already transferred the votes for the deleted request to this, so if anyone else wants to vote, or suggest specific features of JACK we should be supporting (better), please do it there.
As to fixes for JACK, I don't think there are obvious fixes we know of that we can apply, and our position is that essentially we are asking for suggested patches to point us in the right direction. It probably wants a tripartite Audacity/Portaudio/JACK dialogue with input from other apps. in some cases (for example alsaplayer if their fixes are relevant to us sorting out the subject problem).
studio32 wrote:Please keep voting: http://audacityteam.org/wiki/index.php? ... hancements
Users browsing this forum: No registered users and 0 guests