[00:51] <OvenWerks> wonko: autojack ia all mine, controls started off as a utility that fixed real time and memory lock permisions.
[00:53] <OvenWerks> I added the almost everything that is visible any more. The code still uses a some things from before and so there is some difference in coding style in there. :)
[00:55] <wonko> I have some concerns with the code and wanted to know who's fault it was. 😂
[00:55] <OvenWerks> The elif lsplit[0] == "PULSE": is legeacy for sure. I allows autojack to read both the old pulse=true/false and the newer number in and out. This will (of course) have to be retained and translated to a list of names
[00:55] <OvenWerks> Mine.
[00:56] <OvenWerks> I am not perfect for sure and this is probably my first use of python... let along python with a GUI
[00:57] <OvenWerks> You will note that the config file is moving, both controls and autojack will still read from the old location if it exists, but controls will write to the new location.
[00:58] <wonko> I'll be gentle then. 😁
[00:58] <wonko> I saw that, yeah
[00:58] <wonko> Can you help me understand how launchpad works? Can I fork the repo and do PRs?
[00:59] <OvenWerks> You can fork yes... to a personal branch. I don't know how the PR part works though.
[01:00] <wonko> Do you know how? I could figure it out in that web interface.
[01:00] <wonko> Couldn't
[01:01] <OvenWerks> but to do that you basically clone tp your disk and upload to to your persoanl page.
[01:01] <wonko> Oh, ghetto forking. Got it. 😁
[01:02] <OvenWerks> Up till a year or so ago it was all bzr
[01:02] <OvenWerks> Ya not like github
[01:02] <wonko> I'll make the changes we were talking about. Let's save any code cleanup until after because I know you're changing a bunch right now as well.
[01:05] <OvenWerks> basically what I would do is pulse=true/false makes pulse_in and out = ["pulse_in"] and ["pulse_out"]
[01:06] <OvenWerks> then read in pulse_in= and pulse_out= and test for ints
[01:07] <OvenWerks> if they are ints... create default names for that number. otherwise read it as a list of strings.
[01:07] <OvenWerks> wonko: does that make any sense?
[01:08] <OvenWerks> that way, it doesn't matter which version of config file the user has, it will work with the newest functionallity being the way that is chosen
[01:10] <wonko> Yep, I will maintain absolute backward compatibility in reading but will write my new format
[01:12] <OvenWerks> The GUI has had the audio setup split into three sections. Therefore the pulse bridge has it's own section.
[01:15] <wonko> I'll let you know when I'm done and who knows maybe you can update the GUI before the release (although you wouldn't need to)
[01:16] <OvenWerks> wonko: we have around 4 months before release.
[01:16] <wonko> oh shit, we'll get a ton done before that. :)
[01:16] <OvenWerks> we need to have it done by about feb
[01:17] <wonko> What I'm looking at should take a couple hours. :)
[01:18] <OvenWerks> it is too late for 19.10 but it can go to auto builds anytime.
[01:18] <OvenWerks> Soon as 19.10 is released and the seeds are up dated to 20.04 we can look at release.
[01:19] <OvenWerks> generally we like to release as soon as we can so people can test.
[01:20] <wonko> definitely
[01:21] <wonko> I keep trying to write less python and somehow I keep ending up writing python. :)
[01:21]  * OvenWerks would prefer C++
[01:21] <OvenWerks> (and fltk)
[01:23] <wonko> I would probably choose Go these days but I wouldn't be against C++
[01:23] <wonko> But I haven't written any C++ in about a billion years. :)
[01:24] <OvenWerks> there seems to be a lot of python understanding in ubuntu and so if I vanish, a python utility is easy for someone else to take over.
[01:24] <wonko> yeah, that's why I always end up writing it as well
[01:24] <wonko> especially in the sysadmin world there is a lot of understanding of it
[01:24] <wonko> But I really burnt myself out a couple jobs ago
[01:24] <wonko> 60K lines of python is awful, never do that. :)
[01:25] <OvenWerks> :P
[01:25] <wonko> That's what actually pushed me over the edge to trying Go finally.
[01:25] <wonko> I just wasn't interested in ever doing anything big in python ever again after that.
[01:26] <OvenWerks> Go I have not looked at... I started in the late 70s with basic (the kind with no gosub) and pdp8 machine lang.
[01:27] <OvenWerks> from there I have learned a few more scripting languages (the one that came with OS/2 for example) and then k&r C
[01:27] <OvenWerks> C++ was great coming from that as it shows all my mistakes in compile :)
[01:28] <OvenWerks> but I also learned bash, perl, etc.
[01:29] <OvenWerks> My first GUI was GEM (Atari Mega) but then tcl/tk (look at installer)
[01:29] <OvenWerks> And of course Ardour is Gtk2-ish
[01:29] <wonko> I'm a tad younger than you. Messed with basic in the late 80s, picked up C in the early 90s
[01:30] <wonko> I did own a PDP8 though. :)
[01:31] <OvenWerks> The School I went to (SAIT, Calgary AB, Canada) had a bunch of pdp8s that had been given to them. paper tape input, 32k core memory
[01:33] <wonko> I never got the 8 running, it was missing some stuff that I never got before it got lost in a fire
[01:34] <OvenWerks> my training was not in computers (as you already noted) but in broadcast electronics
[01:34] <wonko> I've also owned several PDP-11s and VAXes. I'm a bit of a nerd. :)
[01:34] <wonko> I failed out of college the first semester. I'm self taught in everything I do. :-D
[01:34] <OvenWerks> Vaxs I have worked with
[01:35] <wonko> There are three of the literally sitting in my garage right now (that I'm trying to find a home for)
[01:35] <OvenWerks> We used them for machine control at least till 2006 when I transfered to Vancouver Island
[01:36] <OvenWerks> (I worked in Vancouver before)
[01:36] <wonko> It wasn't compelling to get rid of them. They were solid machines and they ran forever and control software rarely gained much bloat.
[01:36] <OvenWerks> wonko: they have better real time code than the winNT we used alongside
[01:36] <wonko> I had a PDP-11/70 that I got from a newspaper publisher that used them for layout until the late 90s
[01:37] <OvenWerks> TEX?
[01:37] <wonko> I'm assuming so but I don't know for sure.
[01:38] <OvenWerks> I do know the DEC mice were really robust
[01:38] <wonko> You could bludgeon someone to death with one and go back to work with it like nothing happened.
[01:38] <OvenWerks> We had the hockey puck style which were easy to use right or left handed without switching sw
[01:38] <wonko> yeah, those were nice
[01:39] <wonko> I don't have any of those, I got rid of them with most everything else
[01:39] <wonko> I just couldn't keep hauling that shit around with me
[01:39] <OvenWerks> I don't know if they were really PS/2 or not.
[01:39] <OvenWerks> :)
[01:39] <wonko> they weren't
[01:40]  * OvenWerks just bought a few ps/2 mice
[01:40] <OvenWerks> I want my mouse and keyboard as far away from my USB as I can. USB has better things to do.
[01:41] <wonko> ps/2 ports are surpisingly still around on modern motherboard which honestly surprises me
[01:41] <wonko> so much that I used the word surprise twice in that sentence. :)
[01:42] <OvenWerks> my keyboardis old enough it needs an adaptor to work with ps/2... it even has an xt/at switch on the bottom.
[01:43] <OvenWerks> the USB kb is still a ps/2 key board with USB in between. The PC side still has a ps/2 controller inside last I heard.
[01:43] <wonko> I don't think I believe that. :)
[01:44] <wonko> maybe some of the older ones were ps/2 keyboard with build in usb bridges
[01:44] <wonko> but on the host side it's usb all the way
[01:44] <wonko> anyway, time to put the kid to bed, later!
[01:45] <OvenWerks> o/
[17:38] <wonko> OvenWerks: Is master possibly busted or does this maybe not like being run inside of PyCharm?
[17:40] <wonko> https://gist.github.com/cdc8dcb66ef8843cf37a521ef1d07ddb
[17:40] <wonko> just over and over and over with that
[18:01] <wonko> OvenWerks: Ok, I'm going to say it doesn't like being run from within PyCharm. If I launch it from a terminal it behaves.
[19:14] <studiobot> mtngid was added by: mtngid
[19:14] <studiobot> mtngid was removed by: mtngid
[22:31] <OvenWerks> wonko: we are requested to move this to #ubuntustudio-devel. but yes it needs to have access to dbus... the same dbus that jackdbus and pulseaudio are running on.
[23:57] <wonko> Mic mounted: https://imgur.com/a/BDG8vAH
[23:58] <wonko> [19:55] <0000wonkoIt's too far away for normal use (should be 12-18") but I can pull it forward to the correct position without it obstructing the view of the screens which makes me happy.