[00:43] <ScottL> installling now, first testing install from menu, then i'll try boot live and then install
[01:33] <ScottL> okay, installed direct (i.e. without live boot) and phasex and aeolus both started
[01:33] <ScottL> i don't really do midi/synth stuff so i didn't know what to really do with them </embarrassed grin>
[01:36] <ScottL> booting into live now and then will install
[02:27] <ScottL> len__, both aeolus and phasex worked for me right after installing from live boot as well
[03:35] <len__> ScottL, I think I will invalidate the bugs then. Maybe there has been a lib change from yesterday to today. Both of my boxes work now too.
[03:49] <len> One of the bugs was already invalidated... not enough stack trace to mean anything. They did seem to think wrong lib version might be it though.
[04:01] <len__> Most synths are easy to test ScottL, plug the virt keyboard to midi in and the output to jack... press some keys on the virt keys and hear sound ;-)
[04:05] <len__> aeolus is harder, the manual has to have the midi input assigned to it and sounds selected.
[04:06] <len__> aeolus is able to be played like a 3 manual pipe organ if you have three midi keyboards and a set of pedals.
[19:33] <scott-work> astraljava: yeah, i was confused by the comment on the cinerella bug
[19:33] <scott-work> but quite frankly, it's kinda not an appropriate comment either way
[20:14] <astraljava> scott-work: True, wrong bug totally. :)
[20:57] <Len-live> scott-work, astraljava, The volume indicator in the tray now launches pavucontrol. I think that is the last of the fixes before release? just testing?
[20:59] <Len-live> I would like to do some more work on the menu some time. It would be nice to make it work right for as many apps as possible even if we don't ship them.
[20:59] <scott-work> Len-live: agreed
[21:00] <scott-work> anybody have ideas for UDS blueprints regarding ubuntu studio?
[21:00] <scott-work> i can't at this time, last time we did the lowlatency kernel
[21:01] <Len-live> sorry ... UDS = ?
[21:01] <scott-work> but seeing as i think this cycle will probably be mainly small fixes to things done this cycle and documentation, i don't know what we would need
[21:01] <scott-work> UDS = ubuntu developer summit
[21:01] <scott-work> as project lead i am invited to go, not that i do too much really other than attend, learn, and coordinate some stuff
[21:02] <Len-live> I think controls is the next thing.
[21:02] <scott-work> last time i submitted a blueprint for getting the lowlatency kernel into the repo, which was approved and several of the kernel guys showed up for it and gave it some legitimacy :P
[21:02] <scott-work> Len-live: what type of controls are you thinking about? 
[21:03] <Len-live> What software to load, how to set up jack and other stuff, record mode...
[21:03] <Len-live> workflows on all levels really.
[21:04] <Len-live> I am finding with one of my machines a record mode will be needed if I am to do audio with it. NM seems to give me xruns.
[21:04] <scott-work> i think getting together and brainstorming some larger goals for improving the user interfacing with ubuntu studio could be useful
[21:05] <Len-live> You have a way with words :-)
[21:05] <scott-work> step back and abstract a few things, make a list of possible goals, and see where that suggests we go
[21:05] <knome> scott-work, btw, did you already see http://open.knome.fi/2012/04/16/looking-towards-xubuntu-q/ ?
[21:05] <scott-work> lol, thanks
[21:05] <scott-work> i think i did knome , but i probably should reread it if it is the same
[21:05] <knome> :)
[21:05] <scott-work> oh, maybe not, last time i saw a pdf
[21:06] <knome> no, it's a more verbose onw
[21:06] <knome> *one
[21:06] <scott-work> good :) i look forward to reading it
[21:06] <scott-work> i'm am excited about this coming cycle because it WON'T be an LTS version and we can take a few (more) risks :P
[21:06] <knome> next thing i should paste you is the rewritten strategy document when i get to proof-read it one more time
[21:07] <scott-work> yes, i would like to read it, very much so
[21:07] <scott-work> i feel very strongly that the q-cycle should focus on getting some more foundational things done as a minimum;
[21:07] <scott-work> 1. lowlatency maintenance (priority)
[21:07] <scott-work> 2. user documentation
[21:08] <Len-live> knome how hard would it be to change the xfce display app to include dual monitor placement?
[21:08] <scott-work> 3. testing procedures/documentation
[21:08] <knome> Len-live, i've no idea, i'm not a programmer
[21:09] <Len-live> who would I talk to in xfce?
[21:09] <scott-work> 4. refine existing work flows/develop new ones and update wiki documentation
[21:10] <scott-work> and these are just the big items
[21:10] <knome> Len-live, just ask #xfce-dev
[21:10] <scott-work> i am concerned about other development however, i think this will keep my busy for a majority of the cycle
[21:11] <scott-work> i realize that others will be interested in other things than documentation and such
[21:11] <knome> i hope so
[21:11] <knome> one of the items for xubuntu too is documentation
[21:11] <knome> we partly overlap because of xfce
[21:11] <scott-work> but i do feel that docuementation is a very important step for ubuntu studio at this point (in a rebuilding context)
[21:12] <scott-work> knome: that is true, part of what i wanted to do was to document "normal desktop usage"
[21:12] <scott-work> knome: but the largest part is to docuement the creative processes 
[21:12] <scott-work> or work flows
[21:12] <knome> sure
[21:12] <scott-work> but there are also many smaller dev work, like adding #ubuntustudio channel to irc by default and others
[21:12] <Len-live> scott-work, text or video documentation?
[21:13] <scott-work> Len-live: really both
[21:13] <scott-work> but i think text (in the wiki or our website) is paramount at this time, and quicker to do
[21:13] <Len-live> I kinda sensed that was part of where your blog was headed.
[21:13] <scott-work> yeah :)
[21:13] <scott-work> i already recorded another one and should do another this weekend and then edit some of them
[21:14] <scott-work> but first i really, really, REALLY need to work on the ubuntu studio website
[21:14] <knome> ;]
[21:14] <scott-work> i really doubt we will get it released for 12.04 release (not on the same day)
[21:14] <scott-work> but it should be within weeks i would hope
[21:14] <knome> i think it's a bit unrealistic now too
[21:14] <scott-work> really?  :(
[21:14] <knome> noting that even the IS won't get it up in a day
[21:15] <knome> i mean, releasing parallel with 12.04
[21:15] <knome> two weeks after is probably fine
[21:15] <knome> if you can find time to work on it now
[21:15] <scott-work> yeah, yeah, i'm okay with no ton the same day
[21:15] <scott-work> how responsive do you think they will be? i.e. how soon after we say "all clear...go!" will they have it pushed out and live?
[21:16] <scott-work> oops   s/no ton/not on
[21:16] <knome> i have a ticket pending for four days now to update the xubuntu.org code
[21:17] <knome> i suppose you could get a relatively high priority for the US site
[21:17] <scott-work> i'm hoping they will do it within two weeks
[21:17] <scott-work> two weeks of filing a ticket, that is
[21:17] <knome> yeah, completely
[21:17] <knome> the workload probably eases after release
[21:17] <knome> so we can get back to better times
[21:18] <scott-work> oh good :)
[21:18] <knome> and of course, you can push for high priority on some items now and then
[21:18] <scott-work> i have quite a few ideas as well, Len-live , about user improvements
[21:18] <scott-work> knome: good to know
[21:18] <knome> derivatives are never over ubuntu stuff, but you can get quite high
[21:19] <scott-work> but i think q+1 cycle may be the best time for considerable attention to this
[21:20] <scott-work> however, i don't want you to misunderstand my intentions or intents
[21:25]  * scott-work got interrupted at work by work :P
[21:26] <scott-work> Len-live: i realize that most people aren't into creating documentation and i defintely expect people to want to focus on what they want to do
[21:26] <scott-work> so i expect people to focus on development work
[21:27] <Len-live> As always, it is the way volunteer work is.
[21:27] <Len-live>  Gotta pick kids up at school
[21:27] <scott-work> however, i hope that we can pick and choose what we do and if we are doing brand new stuff that we try to make it fit a larger vision or plan
[21:35] <knome> i'm off :)
[21:35] <knome> see you later
[22:02] <Len-live> Scott-work, I think that will happen if there is a well defined plan overall.
[22:03] <Len-live> Some of it will be " I need this to do what I want" stuff too.
[22:03] <Len-live> That is one of the reasons I want to make the menu work with the stuff we don't ship too.
[22:08] <Len-live> I have heard a few " this is 2012 after all" remarks about using more resource hungry DEs and stuff, but one of my computers is less than a year old and the DE/OS fluff is giving it problems.
[22:10] <Len-live> I get an xrun about every minute (I think from wireless rescan), but if I turn the wireless off, I get an xrun every 5 seconds.
[22:11] <Len-live> This is with nothing happening, just jack and pulse running.
[22:20] <scott-work> Len-live: to be honest i still wouldn't mind a "kill pulse" switch
[22:21] <scott-work> that could be part of a record mode accessed from an icon on the top panel
[22:21] <scott-work> okay, going homes
[22:21] <Len-live> scott-work I would say that is part of the record mode.
[22:21] <Len-live> C ja later
[22:21] <scott-work> agreed
[23:30] <ScottL> something else we probably need to consider is if there are any SRU's we might want to do quickly after release (if that is not frowned upon)
[23:30] <micahg> ScottL: everyone does it :)
[23:30] <micahg> you can start staging them now if you like
[23:30]  * ScottL realizes he still didn't get the clock plugin correct
[23:31] <micahg> if it's a deal breaker on the ISO, we can still respin
[23:31] <ScottL> i was basing it on what xubuntu did but didn't get it proper
[23:31] <micahg> Xubuntu switched to the datetime plugin
[23:31] <ScottL> micahg, it's not a deal break, but not what was intended
[23:32] <ScottL> micahg, yes, i was looking at a few revisions ago, plus i wanted to look at xubuntu and how the new clock works and consider it for us
[23:32] <micahg> that's the problem with C/P in general, unless you know the context, it's easy to take a change that won't help
[23:34] <ScottL> C/P?
[23:34] <micahg> cut and paste
[23:34]  * micahg probably used the wrong abbrv
[23:35] <micahg> should've been C&P :)
[23:35] <ScottL> oh, i didn't cut and paste, i was changing the value but i needed the other part
[23:35] <ScottL> the variable name
[23:35] <ScottL> BUT it does look like the plugin had been updated so that might have changed anyways from what was used previously