[09:06] <zequence> sakrecoer_: OvenWerks: (and anyone else who will be working on our package sources): I will be renaming some bzr branches to use the standard naming scheme used for Ubuntu code
[09:07] <zequence> Development branches will all be called "trunk" from now on
[09:07] <zequence> the shorthand (i.e. lp:ubuntustudio-default-settings) will still be the same on all packages
[09:28] <sakrecoer_> ok :)
[09:30] <zequence> sakrecoer_: If you already have a branch locally, uploading to the renamed branch will probably not work using ":parent".
[09:30] <zequence> pushing, I mean
[09:30] <zequence> not uploading :)
[09:32] <zequence> sakrecoer_: btw, if you ever want to fool around with launchpad, just to see how it works, use this https://staging.launchpad.net/
[10:02] <zequence> sakrecoer_: OvenWerks: I updated the part in the wiki dealing with maintaining our packages. Redid the part about the source, to make it more to the point. So far, nothing about making actual changes to the source, and uploading it, but that will come later: https://wiki.ubuntu.com/UbuntuStudio/UbuntuStudioPackageMaintenance
[10:21] <zequence> sakrecoer_: I put an awful amount of time doing these at one point, but I would do it in a different way today https://wiki.ubuntu.com/UbuntuStudio/TeamStructure
[10:23] <zequence> So, feel free to simplify it, if you want. With such a small team, people tend to know what the other one is doing, without having to document it
[10:25] <zequence> Also, the blueprints page doesn't abslutely need to include the actual blueprints. I did that more to get an overview in text in a way you can't get from the launchpad interface https://wiki.ubuntu.com/UbuntuStudio/Blueprints
[15:04] <zequence> Think I'm going to take an easy route as far as development for this cycle goes. Want to a few improvements to -controls, such as a diagnostic tool, and some notification functions to let the user know when something is not right.
[15:05] <zequence> And, when anyone wants to do anything jack based on a Ubuntu flavor, or derivative, they should be told to install -controls
[15:06] <zequence> If they have problems, the diagnostic tool can create a report which they can show others so that it will be easier to identify the problem
[15:06] <zequence> Also, we should at least make videos on basic jack usage
[15:06] <zequence> So, that is what I will commit to this cycle. I'll do some work on -controls before FF, and then do a couple of videos before the release
[15:08] <zequence> No desktop agnostic stuff, no changes to the installer at all. I don't just don't have the time, sorry to say.
[15:09] <knome> zequence, if you are planning to be involved at all with the website refresher, see backlog on this channel :)
[15:10] <zequence> knome: Ok, thanks.
[15:12] <zequence> knome: Great news about the theme. Yeah, I need to see it first, but I for one wouldn't require anything fancy. We do have some people who can do graphics, so in that way we could see about modding it ourselves
[15:12] <knome> please don't mod the main theme - do it under a child theme :)
[15:12] <knome> i can even help with that
[15:12] <zequence> Yes, of course.
[15:12] <knome> and if the things you need are sensible, i'm happy to merge them to the main theme too
[15:13] <zequence> Ok, thanks. We should start by installing it somewhere, and start testing it.
[15:13] <zequence> sakrecoer_: ^
[15:13] <knome> yeah, that would be a good idea, and helpful for me too
[15:14] <zequence> I have a staging site for the old theme already, so I will set that up
[15:14] <knome> great!
[15:15] <zequence> flocculant: Set already accepted that I think. He's a core member now with immense powers.
[15:15] <flocculant> yep - all sorted now
[15:15] <zequence> Oh, I did the mistake of scrolling, and forgot I had scolled
[15:15] <knome> ahah :)
[15:16] <zequence> So, your comment was at the bottom :D
[15:16] <zequence> scrolled*
[15:16] <flocculant> ha ha 
[15:20] <sakrecoer_> zequence: knome: thanks guys! let me know where i can sneakpeak :p
[15:20] <sakrecoer_> my power alone are useless, the real power is the teamwork!
[15:21] <sakrecoer_> read you later guys! happy friday!
[15:21] <zequence> sakrecoer_: If I haven't done it by tomorrow, you may remind me. I'll set up a staging site at my webbhotell, and can give anyone ftp access so they can do stuff if they want
[15:21] <sakrecoer_> awsome!
[15:21] <knome> the latter is true, but the former isn't; single persons can achieve things too (and even more so kickstart good thing)
[15:21] <sakrecoer_> i'll check in to morrow no doubt!
[15:22] <sakrecoer_> knome: :) true, but in this case, since i'm a complete launchpad noob, those powers alone are.. well not so handy :D
[15:22] <cfhowlett> sakrecoer_, hey
[15:22] <sakrecoer_> cfhowlett: hi!
[15:23] <sakrecoer_> i'm on the run, email? :)
[15:23] <sakrecoer_> or just shoot and i read it later :)
[15:23] <sakrecoer_> bye y'all!
[15:23] <zequence> sakrecoer_: I'll put the cops on the wrong trail for ya. Have fun!
[18:36] <flocculant> sakrecoer_ zequence - seems Ross is all sorted now \o/ left the release team
[20:23] <zequence> flocculant: Alright. Thanks :)
[20:23] <flocculant> welcome - glad you've finally got there \o/
[20:24] <flocculant> I'll not wander off - so if anyone needs anything I'm happy to help 
[20:25] <zequence> OvenWerks: You ever notice ardour using a bit more RAM than it aught to?
[20:28] <cub> About the web, wordpress theme, I like the simplicity. Child theme and colours should be easy to work with. As long as there is a design decided in colours, look n feel, so to speak.
[20:29] <cub> Zak emailed the other day, but unsure if and how much he will be able to produce before the 16.04 release
[20:32] <cub> I don't have a test site set up yet, but it seems you are already on it
[21:28] <OvenWerks> zequence: it depends on what you are displaying I think (plugins are another different thing drumgizmo or linuxsampler are huge) Let me try a fresh session
[21:31] <OvenWerks> fresh session with two audio tracks. Gnome system monitor says 148Mbytes
[21:32] <OvenWerks> xfce-taskmanager says 287.
[21:33] <OvenWerks> zequence: ardour version 4.6.161.
[21:36] <OvenWerks> Ardour 4.6.0 with same session - session manager 85Mbyte, Task manager 200Mbyte.
[21:37] <OvenWerks> of note 4.6.0 is the release (optimized version) while 4.6.161 is the debug version.
[21:39] <OvenWerks> zequence: mixbus3 (release) is 90.6/205Mbytes
[21:40] <OvenWerks> zequence: my firefox (three pages of tabs) is sitting aroudn 360-400Mbytes for comparison
[21:44] <OvenWerks> zequence: wow, ardour 3.5.403 uses 323/440 Mbytes for the same session (our package for 14.04). But one of the big changes from 3.* 4.* was a lot of memeory cleanup as I recall.
[21:46]  * OvenWerks obviouly hasn't run ardour3 for some time, it looks quite different.
[21:56] <OvenWerks> 18 tracks (not much content) with eqs, 3 synths,and a few busses with reverbs and the 148MB goes up to 623MB. 
[21:56] <OvenWerks> if that is more than it ought to or not, I can't really say.
[21:57] <OvenWerks> drumgizmo or linux sampler can use over a GB just on their own.
[22:00] <OvenWerks> I suspect the the big memory drinkers in that 623MB above are the two instances of fluid synth in there. Qsynth running standalone is 204MB
[22:01] <OvenWerks> zequence: I think we found before that task manager includes memory that is shared between jackd(bus) and all of it's clients but system monitor doesn't.
[22:20] <sakrecoer_> flocculant \o/ and yes, please stay for coffee. as in "do not wander off" <3 :)
[22:21] <flocculant> ha ha 
[22:22] <flocculant> my work is done :D
[22:22] <flocculant> now I can just wait for MP's for me to comment on :)
[22:22] <sakrecoer_> that is awesome! now you will have the time to explain to me what you did :)
[22:23] <flocculant> I shook the tree till the broken bits fell out - then watered it a bit, all was well 
[22:23] <sakrecoer_> haha
[22:25] <sakrecoer_> gah... MP... Merge... merge... ...push? 
[22:25] <sakrecoer_> xq
[22:25] <flocculant> merge proposal 
[22:25] <flocculant> or mr - request *shrug* 
[22:25] <sakrecoer_> YES!
[22:25] <flocculant> mp I think :)
[22:25]  * sakrecoer_ shake the hand of Mr. Merge Proposal
[22:25] <flocculant> :)
[22:26] <flocculant> I only do testcases ... easy 
[22:26] <sakrecoer_> :) i will do qsynth sunday
[22:27] <flocculant> I will not deal with it on Sunday - got a testing irc session to run for xubuntu 
[22:28] <flocculant> https://lists.ubuntu.com/archives/xubuntu-devel/2016-January/011006.html
[22:29] <flocculant> just in case you want to pop by and see what we're up to - given you now have package tracker stuff
[23:00] <zequence> OvenWerks: When I've ran a session with ardour for a few hours, I find that it has gradually leaked memory. I only use processing plugins. No samples or instruments
[23:01] <zequence> Same session, same plugins, about 4GB difference in RAM usage over time
[23:01] <zequence> Something it not right