Interestingly enough I am not starting jack with qjackctl. I'm loading it at boot time with 'jack_control start' It's almost the very last thing that happens during boot.. After that i'm loading 'pulseaudio --start' with some modules that hook into the jack server. The idea being, when you load the X11 environment, pulse and jack are ready to be manage by your awesome app (qjackctl)... But i can't for the life of me figure out why qjackctl thinks it's starting jack when i've triple checked that it is not or should not be loading jack. Not using 'qjackctl -s' nor did i check off start jack in the config panel.
Interestingly enough I am not starting jack with qjackctl. I'm loading it at boot time with 'jack_control start' It's almost the very last thing that happens during boot.. After that i'm loading 'pulseaudio --start' with some modules that hook into the jack server. The idea being, when you load the X11 environment, pulse and jack are ready to be manage by your awesome app (qjackctl)... But i can't for the life of me figure out why qjackctl thinks it's starting jack when i've triple checked that it is not or should not be loading jack. Not using 'qjackctl -s' nor did i check off start jack in the config panel.
thanks!