At least then it would bring some sanity when trying to attach mixxx outputs to another jack application, at the moment it is very confusing to know what Mixxx:out_1 through to Mixxx:out_? does.
Also I've come across something just now by trying to attach mixxx to another jack application, I have only master and headphones outputs enabled in mixxx settings. When I have Master set as system and channels 1-2 and Headphones on system channels 3-4 I only have 4 output ports showing in qjackctl. When I enable Headphones as system channels 5-6 I get 6 output ports in qjackctl. How come there are an extra 2 ports? This is very confusing. Not sure if this should be filed as a separate bug.
May I suggest at least having an informative client name, something along the lines of:
Mixxx:Master_left s_left s_right
Mixxx:Master_right
Mixxx:Headphone
Mixxx:Headphone
Mixxx:Deck1_left
Mixxx:Deck1_right
Mixxx:Deck2_left
Mixxx:Deck2_right
At least then it would bring some sanity when trying to attach mixxx outputs to another jack application, at the moment it is very confusing to know what Mixxx:out_1 through to Mixxx:out_? does.
Also I've come across something just now by trying to attach mixxx to another jack application, I have only master and headphones outputs enabled in mixxx settings. When I have Master set as system and channels 1-2 and Headphones on system channels 3-4 I only have 4 output ports showing in qjackctl. When I enable Headphones as system channels 5-6 I get 6 output ports in qjackctl. How come there are an extra 2 ports? This is very confusing. Not sure if this should be filed as a separate bug.