=== micahg_ is now known as micahg [19:32] I read the "[ubuntu-studio-devel] First Call for Contributors for the 14.10 cycle of development" email - what type of work would you have for software engineers (Python)? [20:54] aleb: We have some of our own application development, and python would work well for that. [20:55] zequence: meant to post to your list - but here will do - if you need any help with QA type things - just shout [20:55] elfy: Thanks. We would definitely need some work on our testing routines [20:55] I'll be less busy this cycle I hope - many things are already set up and running [20:56] zequence: yep - package testing is not so easy for me to help with as I don't use many of your packages, though basic tests are easy enough to get started - depends if there is any value in doing that [20:59] elfy: I'm sure you have a lot of experience that would come to use for us, especially in how to structure it, using the tools available, and so on. But sure, the focus is a bit different. The most advanced topic is testing audio. [20:59] Since most of us do only audio, not much work is done testing graphics and video [20:59] Surely, also advanced topics, to the people who know that stuff well [21:00] then I would guess the best thing would be too find some people to write the advanced things [21:01] I would guess that most of the 'normal' stuff you seed you can forget as much is tested elsewhere [21:02] given that you don't appear to have a huge number of people about - I'd be looking at the long plan - get everything up before 16.04 [21:02] it DID take us a whole cycle to get our stuff ready - and we had quite a lot of people writing them [21:03] a list of apps you want to test would be a good start :) [21:07] elfy: Planning long term for 16.04 is very much in line with how I think. [21:07] then I am sure I will be able to help you then :) [21:10] zequence: if you can get me some sort of list - with some sort of importance of your apps - then I can start looking at it, assuming you want to of course [21:11] but I'm away now - wicked headache most of the day [21:11] zequence: been sick all week... so it iskind of hard to have an interest in anything :) [21:12] I have (for my own use) been working on an audio mode systray app. [21:13] I don't know if Studio would want to use it or not. [21:14] The system side part may be useful if Studio would prefer to use a more generic controls tool. [21:16] I am using python with pyqt for the gui. But system side will probably be sh scripts... just because I can copy some things that are already there. [21:16] OvenWerk1: Ubuntu Studio controls, as I've been working at, is a systray app [21:16] OvenWerk1: Sure you are not reproducing the same work? [21:16] Probably not quite. [21:17] But that is why I asked if it was even useful for Studio. [21:17] OvenWerk1: Would be great to see what you are planning on doing, and what you have done [21:17] It is useful for what I want on my machine :) [21:17] Well, that is probably not what everyone needs - but some of it might be [21:18] I have set my system up so that jackdbus starts at session start. [21:19] That is one thing I'm working at as well [21:20] Ay app sets latency of jack as well as pa-jack bridge on off. I am working on also controlling if CPU governor is ondemand or performance depending on latency. [21:20] autostarting jack - also, controlling jack through dbus [21:21] Right now I have 5 modes, but I am finding my new machine doesn't really need all of them. [21:22] OvenWerk1: Would be nice to see the code you've done. My first job for ubuntustudio-controls will be to SRU the existing one in trusty, to make it do something useful, but that will only administer rt privilege. Later, I'll start summing up my previous work - perhaps also see if falktx (who already has made quite extensive work on a systray app) would like to work with us on that [21:23] falktx systray app supports all DEs [21:23] I have a desktop mode... high latency, pulse on. I have a low latency phone mode with pulse still on. Then three different latencys for pulse off, recording live and mixdown. [21:23] That was why I went with QT for the gui. [21:24] Both GTK and QT supports all DEs. I was more referring to the systray part [21:24] indicator and systray are separate. Also, Gnome has it's own thing, but can support systray and indicator apps with plugins [21:24] That was the part I meant too. The gtk2/3 systray stuff has been in the air for a while. [21:27] Anyway, I have found that my recording mode and live mode don't seem to need different settings. [21:28] You seem to have worked out a logic for things, and are still figuring that out. You would probably benefit from feedback, unless of course, you are only working on that for yourself [21:28] So I am thinking of doing just four modes. One thing I would really like to be able to do is find the min/max latency for a sound card. [21:29] Feed back would be fine. [21:29] The simpler, the better. One mode would be best of all. [21:30] Tuning cpu governor is of course a nice thing to do [21:30] I tried doing userspace with different speeds. Basically I don't need it. [21:31] I can run in performance at 100% cpu on all cores without getting too hot. [21:31] I seem to have a good 10C head space [21:32] OvenWerk1: Did you see the mail about suspend? [21:32] We should see about that, and SRU it [21:32] In fact performance seems to generate less heat than ondemand when pushed. [21:33] Getting a bit late. Will be back tomorrow. Need to address some mails, and finalize the structure for planning, so we can go forward with defining out specs for this release [21:33] OK, I will go pick up my boy. [23:00] zequence, so if I volunteer, what would you ask me to do, could you give me an example?