[19:06] <AppAraat[m]> hi, is there a way to use a dark theme for `qjackctl` ?
[19:43] <OvenWerks> AppAraat[m]: it appears not. You could ask the author though.
[19:44] <AppAraat[m]> hmm, is there otherwise something like `qjackctl` but for the CLI?
[19:44] <OvenWerks> AppAraat[m]: rncbc hangs out on #lad at least
[19:44] <OvenWerks> like qjackctl in what way?
[19:45] <OvenWerks> jack_control will start jack
[19:45] <AppAraat[m]> oh, cool to know. Thanks.
[19:45] <OvenWerks> jack_connect can connect one port to another
[19:46] <OvenWerks> jack_lsp will list existing ports and with the -c option will show connections
[19:47] <OvenWerks> jack-plumbing can use a file to make connetions when certain ports show up.
[19:47] <OvenWerks> basically type jack and then tab a few times to get a list of all jack* commands
[19:48] <OvenWerks> If you have not installed jack-tools, it gives a few more
[19:48] <AppAraat[m]> ah, looks kinda messy but I'll take a look, thanks :)
[19:49] <AppAraat[m]> most of them don't seem to have manpages :(
[19:50] <OvenWerks> standard unix-y lots of tools that do only one thing kind of messy yes
[19:51] <AppAraat[m]> I don't see any reason most of them could be integrated with the use of flags or subcommands, or at least be documented, but that's my first impression.
[19:51] <AppAraat[m]> *could not
[19:56] <OvenWerks> fully agree
[19:57] <OvenWerks> I got more out of jack_control by trying to run it with no parameters than any documentation
[19:58] <OvenWerks> many of them are python scripts BTW
[20:42] <AppAraat[m]> oh hmm, yeah seems like `jack_control` is the big daddy.
[22:15] <studiobot> AlFarsie13 was added by: AlFarsie13
[22:16] <studiobot> AlFarsie13 was removed by: AlFarsie13