[10:26] <zequence> OvenWerks: Did you boot it yet?
[15:07] <OvenWerks> It boots fine, but I have had trouble with install. I am not sure if it is the image or my USB HW.
[15:07] <OvenWerks> zequence: My first attempt included formatting the partition which failed... or finished but did not continue.
[15:08] <OvenWerks> I am reinstalling now, but pre-formatted on my normal boot. This seems to be working fine so far.
[15:09] <OvenWerks> however, The USB stick is plugged into a different socket.
[15:13] <OvenWerks> Install finished...
[15:15] <zequence> OvenWerks: I've been having some issues with disk partitioning
[15:15] <zequence> On wily though
[15:15] <zequence> Had to use gparted to partition manually, and then run ubiquity
[15:16] <zequence> Yes, it got stuck on when it was creating the EXT4 file system
[15:41] <OvenWerks> Installed and booted ok.
[19:33] <OvenWerks> hmm, the secret to starting jackdbus at session start is to unload the pulse jack bridge first, start jackdbus and then reload the bridge.
[19:36] <OvenWerks> I was using delays and a pulseaudio -k. which worked for me, but my wife who had "restart applications from the last session" had trouble with skype working right.
[19:37] <OvenWerks> I like the new qjackctl, it is much easier to use.
[19:39] <OvenWerks> the "port maximum" defaults to 256. That is probably a mistake as Jackd(bus) defaults to 2048. Qjackctl only allows it to be as high as 1024.
[19:41] <OvenWerks> There is no reason on a desktop to be less than 2048. (where qjackctl is used) though it could be useful to go less in an embedded setup... where jackd would be started from the command line or script anyway.
[19:42] <zequence> OvenWerks: Interesting about the pulse jack bridge. We should try get something together on that this cycle
[19:42] <zequence> Though, at this point, I'm not entirely sure there will be another release :)
[19:42] <zequence> OvenWerks: What's your thoughts on that? Do you have plans on being project lead?
[19:55] <OvenWerks> I am thinking about it yes. I will see how this one seems to be going in a week.
[19:58] <zequence> Vote is in January, so there may be more than one candidate. I'm sure you, like me, are not worried too much who is lead, as long as it's a reasonable fit.
[19:58] <zequence> I mean, before January, more people might show interest.
[19:59] <zequence> But, it's good to know you are at least thinking about it.
[19:59] <OvenWerks> zequence: I am not sure about committing to the next LTS, but I may be willing to do a release and see where life has taken me. I have just retired and am recovering from the physical abuse of the job. It is hard to know what I will be doing in a year.
[20:01] <OvenWerks> I can load more than one module-jack-sink (or source)
[20:02] <zequence> OvenWerks: Ok. Well, the LTS will need to have some eyes on it for the following three years, though mostly on paper most probably as it has been except for a few bug fixes we've done.
[20:03] <OvenWerks> If I do things inteligently enough, I should be able to by default start jackdbus with the default AI, add any other AIs via zita-ajbridge and then bridge those to pulse as well.
[20:03] <zequence> That would be ideal
[20:04] <OvenWerks> a config file would allow setting what is default.
[20:05] <OvenWerks> a config should even be able to set a USB AI that is not plugged in at start up to take over default if/when it is plugged in.
[20:05] <zequence> Yes, but I could add controls for that. I haven't yet started really working on it. Have lots of unfinished code for controlling jack and pulse.
[20:05] <zequence> I mean, gui controls.
[20:05] <OvenWerks> controls should generally make the config file.
[20:06] <zequence> Yeah
[20:06] <OvenWerks> It would also do on the fly changes
[20:06] <zequence> Right
[20:06] <zequence> What kind of code would you be using for this? bash?
[20:07] <OvenWerks> changing buffer size can be done on the fly for jack but not zita-ajbridge, those would have to be stopped restarted.
[20:07] <OvenWerks> The session start script is in bash
[20:07] <zequence> I've been using python, and there are a couple of alternatives for config libraries, with ready to use classes and functions
[20:07] <zequence> Ok
[20:07] <OvenWerks> The GUI can be in whatever.
[20:08] <zequence> If you like, just work out the functionality, and I could translate that, if needed, to python, and add the config functionality as well
[20:08] <zequence> I would do the config stuff in python either way
[20:08] <OvenWerks> Basically the config file just needs Defaultai=hw;USB kinds of things
[20:09] <OvenWerks> my script starts with:
[20:09] <zequence> Well, sure.
[20:09] <OvenWerks> DELAY=1
[20:09] <OvenWerks> DRIVER=alsa
[20:09] <OvenWerks> DEV=hw:0
[20:09] <OvenWerks> RATE=48000
[20:09] <OvenWerks> FRAME=512
[20:09] <OvenWerks> PERIOD=2
[20:10] <OvenWerks> so far.
[20:11] <zequence> I've been working on a tool I'm calling apt-search for a few days again. It can search for source and binary packages from any active Debian or Ubuntu release
[20:11] <OvenWerks> After that I will put something that checks if ~/.config/whatever/autojack.cfg is there and include it so it can over write the defaults.
[20:11] <zequence> So, want to finish that. But, perhaps I can start working on -controls next week. Also need to finish the project lead vote stuff.
[20:11] <zequence> ..and do whatever work on the wiki to fix things up a bit.
[20:14] <OvenWerks> That is my problem with doing lead stuff. I am not really well enough rounded. I can see the tech stuff, but not the social/PR side. (I mean much more than social media by social)
[20:15] <zequence> I've done my best to kind of put things in place so that the next lead won't have to deal too much with organizational stuff
[20:15] <zequence> I still need to simplify a lot of stuff, I feel
[20:15] <zequence> With such a small team, it's too much
[20:15] <OvenWerks> Its not easy for sure.
[20:16] <zequence> I would like there to be more people involved, and then it makes sense to have a bit of organization
[20:16] <OvenWerks> :)
[20:16] <zequence> But, if it's like as is now, could be a lot of that work is for nothing, and you could just wing it
[20:17] <zequence> I mean, the important stuff is just to get the ISO tested and published, and make sure our metas are healthy. 
[20:17] <zequence> But, we could do a lot, lot more
[20:18] <zequence> We, as in if there was more of we
[20:25] <OvenWerks> :)  yes. I am going to try to be a bit more active this round... 
[20:27] <OvenWerks> I have just about done all I can with Ardour dev work... But what got me into it is I am building a MIDI/OSC/OCA control surface.
[20:27] <OvenWerks> I will be spending more time on that as I get parts.
[20:28] <OvenWerks> I have been using FLTK in c++ so far, but I think I will move to AVTK as that becomes more stable.
[20:37] <DalekSec> :3
[20:59] <zequence> Cool
[22:07] <zequence> OvenWerks: One thing that I really want to get done for controls though is a diagnostic report tool
[22:07] <zequence> Click a button, and get help anywhere from a paste
[22:08] <zequence> Also, get help from the diagnostic itself
[22:10] <OvenWerks> Ardour has a tool that tells what audio devices are available, who has them locked and some things like that.
[22:10] <OvenWerks> I just found an interesting thing. PA keeps running even after logout
[22:11] <OvenWerks> So PA tends to be in a wierd state right after login
[22:12] <OvenWerks> Things that work right after a boot do not work after logout/login, but do work after logout/login as guest/logout/login as user.
[22:48] <zequence> I know there has been attempts of making it user session only for Desktop systems, but it is also able to do system wide stuff