Jack Audio Connection Kit Implementation Does not Follow Normal Behaviour
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mixxx |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
There are some issues with Jack Audio Connection Kit behaviour. It does not follow standard Jack behaviour ...
1. The Mixxx preferences dialog for Jack is not set up in the usual way. Other apps just connect to the Jack server and present their connections there without presenting them in their own GUI. This is the usual Jack behaviour. Jack connections are best handled by software such as QJackCtl. There is no need to show the drop down lists when Jack is selected.
2. The Jack connection names are not correct ...
A. They are numberd from 0 (zero) when other Jack apps have them numbered from 1 (one).
B. They don't have proper names. Hydrogen names all its outputs by instrument name or just "Out_L" and "Out_R" if its not setup per instrument. Ardour has proper names like "auditioner/out 1", "auditioner/out 2". Same for "click" and it gives the names of the various tracks if they have been named by the user. The outputs and inputs should be presented to Jack server with the names as they are given on the left of the drop down boxes in the Mixxx Jack preferences GUI.
Examples of proper Jack behaviour can be found in Hydrogen and Ardour, and other Jack software and their relationship to QJackCtl.
I looked for a "best practices" document that might describe how best to implement Jack in an application. I'll comment here if I find one. However it is the users of Jack that know how it "should" work. This really only becomes apparent after fully familiarising oneself with Jack.
Changed in mixxx: | |
assignee: | Bill Good (bkgood) → nobody |
status: | Confirmed → Won't Fix |
Since we use JACK through PortAudio there are limitations in how we can interact with JACK. We should work with PortAudio to expose more of the JACK API.