[15:27] Eickmeyer: thank you for uploading controls... [15:28] OvenWerks: Quite welcome. :) [15:29] Eickmeyer: if I can find a simple fix to the db problem that will come soon. [15:29] Sounds great. :) [15:29] but I think it is going to be messy [15:30] Big changes are always messy. [15:31] * OvenWerks thinks he needs to create a controls or autojack lib [15:31] I think there is some code that controls and autojack need to be able to share [15:33] Oh, probably. By the way, is there a way to start and stop jack from the command line? I'm thinking about writing a plasma widget that can do the basic start/restart and stop items right from the systray. [15:33] Eickmeyer: you do not mean start and stop jack but tell autojack to do that? [15:33] Yeah. [15:34] Wouldn't be DE-agnostic, but it would be a start. [15:34] * OvenWerks gives a sigh of releif [15:34] haha [15:34] there are two dbus commands [15:35] hmmm and a rewrite of the config file to change JACK to true or false [15:36] That's easy. [15:36] Yeah but I should change it so the config rewrite is not needed [15:37] maybe not, the config rewrite is what makes the current state say over reboot [15:37] I was just about to say... [15:37] I don't really want autojack doing that rewrite [15:39] Yeah. If there was a way of passing a command line to studio-controls itself to not launch a GUI but to do the dbus command, that would be amazing. [15:39] (and, of course, do the conf rewrite) [15:39] There are really two ways to do this, have the systray applet send the signal controls normally would to autojack or have it send a signal to controls... [15:40] I think a signal to controls would be best, because then we're not having to reinvent the wheel. [15:40] except controls may not be running [15:40] Right. Hence, a command-line parameter. [15:41] really the thing to do would be like qjackctl where it keeps running but becomes the systray applet [15:42] but that is not quick simple ;) [15:43] Do you want this to be a part of controls or separate? [15:43] I was thinking separate. Something that just passes a command and sits in the plasma tray, therefore not taking up any additional resources. [15:44] Literally a plasma applet written in qml that basically acts as a plugin for Plasma. [15:44] See plasma-optimus. It's an applet I forked for Plasma to switch between NVIDIA and Intel graphics. [15:45] It simply sits there and runs a script, when called, but is not using additional resources because it runs as part of the plasma process. [15:50] will that be written in pythom3? [15:51] (changing the db is a python3 thing) anyway I am writing it to be cl [15:51] It would be written in qml. [15:52] Plasma does everything with qml. [15:52] * OvenWerks is not at all familiar with that [15:52] Well, that's where I come it. [15:52] *in [15:52] The only thing I'd need is a way to pass a command to studio-controls to do its thing. Not even an API, just a command-line parameter. [15:53] It can use bash in the backend to do that. [15:54] I am writing a quick py3 utility right now. Controls sets up the GUI before it does anything else [15:55] It would take more changes to controls to do the same [15:58] I see. [16:52] Eickmeyer: Can I assume autojack has already been run? (That will at least create a config file of some sort) [16:52] OvenWerks: Yes. [16:53] Eickmeyer: if this utility is run with no config file, it will error out (error 1) [16:53] Ah, good to know. Probably won't affect the applet. [16:54] I can catch the error though, and pop a dialog. [16:54] Eickmeyer: I think that starting jack if studio_controls has never been run is probably not a good thing [16:54] Agreed. [16:54] It will try to pick the best internal audio device it can find [17:42] Eickmeyer: it would be possible to have autojack not create a config file on first run but fix an already created config so that controls would have to be run just to create a config [17:42] Eickmeyer: but I thing that would be considered a new feature not a bugfix [17:42] That's correct, we'd have to backport not upload. [17:43] Unless it fixes something that's a little broken. [17:45] Having a systray applet is already a new feature... [17:45] Yeah, that would have to be a backport. [17:47] Eickmeyer: right now, autojack will not start jack untill controls runs anyway, so not broken. But if a systray applet goes around that and creates a problem, then this would be a fix to make the systray applet work. [17:47] Oh, pwedwxr. [17:47] *perfect [17:47] fingers on wrong keys. hehe [19:01] And stack overflow goes paywall (sigh) No access without an account so we can sell your info. [19:12] Yikes. I hope askubuntu isn't affectdd. [19:13] *whew* it's not. [19:34] Eickmeyer: http://www.ovenwerks.net/paste/controls-cl [19:34] down load and make it executable if needed [19:35] can be called with either start or stop as the only parmeter [19:35] OvenWerks: That look slike it should work for sure. I can't test it right now, but I'll try to after I'm done with work. [19:38] Works here anyway [19:41] Sweet! [19:45] When running Dolphin remotely (via latte-dock) it pops up dialogs on the local machine instead of the remote machine :P [19:46] I think this is because all dolphine windows are the same process and so dialogs pop up on the display where it was first started [22:18] Eickmeyer: the script I gave you can be translated to run native in qml [22:20] OvenWerks: Won't be necessary as qml just draws the frontend, defines the icon, and executes something when a button is pushed. [22:20] ok [22:20] So, I'd just have it execute that script with an argument depending on what is pressed.