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