[00:00] <zequence> hmm, we don't have a new default background yet, though
[14:17] <zequence> OvenWerks: Did you manage to set up a good autostart routine for jack?
[14:45] <zequence> I think some devices don't support changing samplerate on the fly, btw. But, that could be overcome by only allowing that for certain devices
[14:52] <zequence> I'm working on -controls this week. Starting with system diagnosis
[14:52] <zequence> Then, I'll add whatever there is time for
[15:48] <OvenWerks> zequence: Any auto start script I can come up with requires some user inputs. Running zita-ajbridge on anything and everything is not really a good idea. we end up with more CPU being used than is really needed and of course many new MB have extra audio interfaces the user is unaware of.
[15:51] <OvenWerks> I do have a script that will go through all the audio devices and connect them all to jack. (and create lines from pulse to them too) But I think there is a better way.
[15:52] <zequence> OvenWerks: I will set up gui options and settings for that. Just wanted to see what you have and see if can incorporate that
[15:52] <OvenWerks> I think it is better to find out from the user what they want to use as their default device, what they want to record from and if they want a USB device to automatically become master.
[15:53] <zequence> One of the plans has been to have a setup wizard on first login. Would make it easy to set your system up for what you need
[15:54] <zequence> There should be a function for checking if the chosen devices exist first, though. Especially USB and Firewire devices may not be connected during boot
[15:55] <OvenWerks> zequence: if you can write a file .config/autojackrc that has some lines like DEV=<default> USB=yes or no EXTRA=<extra device to connect via zita-ajbridge>
[15:55] <zequence> Yes, I will try to work that out
[16:01] <zequence> OvenWerks: So, do you have the autostart script somewhere?
[16:15] <zequence> I'm splitting up -controls into different scripts. The system configurations will be done with a separate command line script residing at /usr/sbin/ubuntustudio-sysconfig. THe gui will call the script when it needs to
[16:16] <zequence> The gui will now be launched as normal user
[16:16] <zequence> The gui may also be run as a command line application only.
[16:18] <zequence> In the future it would be cool if the application could be used also on touch devices
[16:23] <OvenWerks> zequence: I need to reduce it :) so it only deals with devices in the config file.
[16:25] <OvenWerks> DEV= is already handled. I will do EXTRA= and do something with USB= too. I think I will connect at least the main HDA (internal) if found just to be safe.
[16:26] <OvenWerks> The main thing with HDA will be the output.
[16:26] <zequence> OvenWerks: Let me know when you have that done. I'm not sure how much I will be doing this week. Really depends on how much I can get done
[16:26] <zequence> I would like to add autostart options at some point though
[16:27] <OvenWerks> zequence: OK, I haven't really done anything for a week. I won't be doing anything in Ardour probably till after next point release. I only have my own control Surface SW going right now.
[16:29] <OvenWerks> zequence: I also started working on a patch bay for jack. The main difference is that instead of just listing jack clients, it will also list ALSA devices that could be connected. (this is where I went after figuring out auto everything is not so good.)
[16:30] <OvenWerks> in the end this should also be able to connect network AIs such as AVB AES67 streams.
[16:31] <OvenWerks> but to begin I just want it to get to bridging ALSA/PA stuff.
[16:32] <zequence> That would be cool
[16:33] <OvenWerks> zequence: So I will setup autojack to check that DEV and EXTRA exist and make a package.
[16:34] <zequence> OvenWerks: A package?
[16:34] <OvenWerks> ya, that would probably be the easiest thing for you to pull from.
[16:34] <zequence> Why not just supply the script? It's just one file, right?
[16:34] <OvenWerks> A package shows all the files in the directory structure.
[16:35] <zequence> Well, anyway you like.
[16:35] <OvenWerks> no, there is a desktop file to go in /etc/xdg/autostart as well.
[16:35] <zequence> Yeah, I figured
[16:36] <zequence> If we incorporate that to -controls, the autostart will be running a more generic -controls script that does multiple things, checking from configs
[16:36] <zequence> First doing a system diagnostic. Then, starting stuff up
[16:37] <zequence> I would probably translate your stuff to python too
[16:37] <zequence> I'm just mostly interested in the logic at this point, you know?
[16:38] <OvenWerks> I can do a tarball then.
[16:38] <zequence> sure
[16:38] <OvenWerks> it is a bash script so nothing complex.
[16:42] <OvenWerks> something on my system has a memory leak. I never use swap, but this morning swap was half full. The only two new things I had running were guitarix and gxtuner... unless it was a badly behaved webpage. Ardour was not running... mostly just terminals, file managers and firefox.
[16:46] <zequence> did you check the processes?
[16:46] <zequence> You should be able to spot which one is using an abnormal amount of memory
[16:53] <OvenWerks> I have restarted guitarix to check that. The system was too slow to deal with so I just got rid of extra stuff.
[16:54] <OvenWerks> guitarix was running for three or four days, so it may be a while.
[16:56] <OvenWerks> FF was at 4.5 G, but has gone down to 2.6 by getting rid of gmail and google calendar and a few android app pages. I still have most of the tabs there (~30) so that may have been part of the problem.
[16:57] <zequence> :)
[16:58] <OvenWerks> (RAM is 8G)
[16:59] <OvenWerks> Swap is 2.9G as I haven't changed it from when I had the P4 with 2.5G
[17:08] <OvenWerks> on a different topic, AVB looks to be an up and coming thing. There are now three companies with AoIP audio IFs that support it: MOTU (who have also finally started doing USB2.0 compliant AI), focusrite (as part of their RedNet line) and Presonus with their digital rackmount line. Later OSx supports AVB at the ethernet port and there is enough stuff in openAVB to at least make a link in Linux as well (with the right NIC... Intel i210 is 
[17:11] <OvenWerks> While aes67 should be easier to implement on linux (there is aes67 on windows but not AVB) there are few lower cost AIs that use it anyway. With AVB finally being finished, it may over shadow aes67 at least for a LAN.
[17:13] <zequence> Didn't know about that. Seems interesting
[17:14] <OvenWerks> I think it should be possible to come up with a jackd backend for AVB that will deal with at least one AVB AI even with no special NIC. A second AI would have to pass through the first I think to make that work though. At least one stream would have to be alive all the time for sync pruposes.
[17:16] <OvenWerks> The i210 is not costly though, I picked up two at $49 CAD each.
[19:32] <OvenWerks> zequence: the other parameters I use in auto jack are:
[19:33] <OvenWerks> DRIVER=alsa
[19:33] <OvenWerks> DEV=default
[19:33] <OvenWerks> RATE=48000
[19:33] <OvenWerks> FRAME=512
[19:33] <OvenWerks> # zita-ajbridge seems to run better with a lower frame rate.
[19:33] <OvenWerks> ZFRAME=256
[19:33] <OvenWerks> PERIOD=2
[19:34] <OvenWerks> zequence: Any of these can be overridden from .configure/autojackrc which is read in right after these.
[19:36] <OvenWerks> DEV=default is the same as hw:0 but gets replaced with hw:name of hw:0
[19:39] <OvenWerks> zequence: I am thinking I should change EXTRA= to EXTRA_C and EXTRA_P so that just capture or just play will work.
[20:09] <knome> people, how do you see the ubuntu studio future?
[21:02] <sakrecoer> knome: hopefully bright :) if you are asking in the broad sense
[21:03] <sakrecoer> knome: how about you?
[21:06] <sakrecoer> i'd like to see the desktop agnosticism happen. i think it would open up for acwider audience
[21:07] <sakrecoer> *broader audience
[21:08] <sakrecoer> *wider was probably the word i wanted
[21:09] <sakrecoer> i'm adaptable, but desktop choice seem to be a decisive factor for many users
[21:14] <sakrecoer> i wish that school systems world wide will adopt GNU/linux, logicaly in that thought i wish ubuntustudio would become the choice for artschoops
[21:14] <sakrecoer> *artschools
[21:18] <sakrecoer> its a not so distant reality in southamerica and africa i guess
[22:24] <sakrecoer> hopefully the future of the graphics packages will look a bit like this: http://41.media.tumblr.com/6033c0e668e76ec87a8aa7cfe80c8c30/tumblr_np4y8cOkaC1rj6lpxo1_r1_1280.png :)
[22:25] <sakrecoer> or like this: https://mir-s3-cdn-cf.behance.net/project_modules/max_1200/4adadf32534447.5689c1d2ed089.png
[23:47] <knome> i
[23:47] <knome> egh
[23:47] <knome> i'm thinking more about the actual decisions and how studio will exist
[23:48] <knome> i talked the other day with astraljava about this too and we circled around the idea of not releasing an ISO at all
[23:48] <knome> just some metapackages for the workflows
[23:49] <knome> i think the audio workflow is the best example how this could bring more than just "a selection of apps" to the table, with the JACK stuff and controls
[23:50] <knome> this way you could forget all the DE stuff, and even wallpapers and that kind of branding
[23:50] <knome> well, not forget branding completely, but not have to worry about maintaining a dozen of things that you have to do now
[23:51] <knome> it might help the motivation for other people to join contributing, since everything is kind of straight-to-the-point and actually changing something
[23:52] <knome> instead of losing some of the work to infrastructure and bureaucracy
[23:52] <knome> with a team as small as the studio team, the time used for those is relatively substantial
[23:57] <sakrecoer> knome: it is an interesting idea. i can see how it would be beneficial. i also think having an iso is a good "selling point". the prospect of having everything in place after install is attractive...