qjackctl just lists and identifies all system audio pcm devices exactly as the ALSA system software stack enumerates them.
it's a fact that sound devices are listed in the order their respective drivers are eventually loaded at boot time or detected whenever they're plugged in (this is the case of the removable USB devices).
unfortunately this order of events isn't always deterministic as you may already noticed.
the solution is to force fixed slot indexes for each kernel device module--you tell that on the /etc/modprobe.conf or /etc/modprobe.d entries while on kernel system configuration settings or whatever it gets called on your distro of choice (mine is openSUSE and it's all done under YaST Hardware Settings / Sound devices)
whether the MPK gets listed as a PCM device is beyond me. however. i do have a MPK25 here and it's listed there too. i just mark it once with some higher slot index on the modprobe.conf settings and gone with it :)
qjackctl just lists and identifies all system audio pcm devices exactly as the ALSA system software stack enumerates them.
it's a fact that sound devices are listed in the order their respective drivers are eventually loaded at boot time or detected whenever they're plugged in (this is the case of the removable USB devices).
unfortunately this order of events isn't always deterministic as you may already noticed.
the solution is to force fixed slot indexes for each kernel device module--you tell that on the /etc/modprobe.conf or /etc/modprobe.d entries while on kernel system configuration settings or whatever it gets called on your distro of choice (mine is openSUSE and it's all done under YaST Hardware Settings / Sound devices)
you may also go and read this topic on ALSA wiki. it gives you all the necessary insight ;)
whether the MPK gets listed as a PCM device is beyond me. however. i do have a MPK25 here and it's listed there too. i just mark it once with some higher slot index on the modprobe.conf settings and gone with it :)
cheers