[06:49] <abogani> I'm not happy at all about this ^
[06:49] <abogani> Luke have locked kernel so I can't neither change or updated it.
[06:50] <abogani> Good catch guy. You are like any other member of the UKT.
[06:50] <micahg> he's not a member of the UKT :)
[06:50] <abogani> Indeed he seems.
[06:51] <CFHowlett> meeting this sunday are we?
[06:52] <abogani> ScottL: Could you remove me from Maintainer field in lowlatency kernel, please?
[06:52] <micahg> abogani: I'm sure he'd like help, he mentioned that you need to keep the changelog entries when updating
[06:53] <abogani> micahg: But he have dropped his git tree so I can't recent changelog.
[06:53] <abogani> s/recent/get recent
[06:54] <abogani> micahg: Are you part of Canonical staff?
[06:54] <micahg> yes
[06:56] <micahg> abogani: I'm sure there's still a git tree, just ask him to let you know where it is and update the Vcs-Git in the package
[06:59] <abogani> Vcs-Git point to my git tree!
[06:59] <abogani> You can't take a critical look at things made by your colleagues, evidently.
[07:04] <micahg> Vcs-Git: http://kernel.ubuntu.com/git-repos/ubuntu/ubuntu-precise-meta-lowlatency.git
[07:07] <micahg> abogani: just encouraging you not to abandon something you obviously care about due to miscommunication
[07:20] <abogani> They have changed my work (aka commits) without any communication, change authorship of patches which I have written and finally make me work worst for non obviously reason. Sure there is a miscommunication problem here but not made by me.
[07:21] <micahg> abogani: I never accused you of miscommunication
[07:22] <micahg> abogani: we value giving proper attribution to contributors, if this is not happening, it needs to be addressed
[11:47] <scott-work> i am upset about alessio and the lowlatency kernel
[11:49] <scott-work> the reported callousness WRT alessio's work is disturbing
[11:51] <scott-work> as i was committed to getting the lowlatency kernel into the repository, i am also committed to developing, documenting, and making sure we follow a proper maintenance procedure for it
[12:16] <scott-work> my weekly email for the release-team meeting will include a line item about this as well (although the "line" item will actually be several lines)
[13:58] <astraljava> Yeah, I have no detailed info regarding the matter, so I don't have any input on the matter. Just that it's unfortunate.
[13:59] <knome> astraljava, re: release meeting: 16:24  ogasawara: I recall skaet mentioned yesterday that the meeting is canceled for today and she'd call an impromptu meeting on monday if needed
[14:03] <scott-work> kate has stated previously that we most likely would not have meeting directly after a (milestone) release
[14:04] <astraljava> knome: Yeah, I noticed.
[14:04] <astraljava> Fine by me.
[14:22] <astraljava> So, now that it's official, we can plan for the amd64+mac images for the Q release, as I'm gonna have a Mac for a work laptop in the new job that I'm starting a little over two weeks from now.
[14:23] <holstein> you mean, PPC?
[14:24] <astraljava> holstein: No, those are for the powerpc chipsets. The new line of Macs with Intel hardware.
[14:24] <holstein> im over hopping through hoops for that hardware
[14:24] <holstein> i have a few that i got for free, and im just not into them anymore
[14:25] <astraljava> Yeah, I wouldn't get it for myself personally, but as for a workhorse, it's ok.
[14:25] <holstein> hey... if it works, it works
[14:26] <holstein> personally, i plan on buying either used hardware, or machines with linux pre-loaded
[14:28] <holstein> i wonder what all the new bios changes, and whatever is up with the mac is going to add to the work load for projects like *buntu
[14:29] <astraljava> holstein: I don't know, yet, but I intend to find out soon when I have the machine to test with.
[14:30] <holstein> i need to get something running iOS i think.. for testing
[14:30] <holstein> too bad you really cant get away with virtualizing those
[15:29] <scott-work> now that what is official, astraljava ?
[15:29] <astraljava> scott-work: The new job.
[15:30] <scott-work> oh, i didn't realize you had announced it, sorry...but congratualtions again! :)
[15:31] <astraljava> Thankee. :)
[16:17] <scott-work> astraljava: i updated bug #967140 to include the icon image and slideshow background as well
[16:17] <scott-work> (i'm sure you got the email for it)
[16:21] <astraljava> scott-work: Ok. Colin wasn't sure he would be able to do anything about it. It's got links to the cdimage, so it's possible that bug will not progress, in which case we need to find another way to make changes to the distributor logo.
[16:21] <scott-work> do anything about the icon?
[16:26] <astraljava> scott-work: The bug isn't about the icon. But if you agree with him about changing the description, then it can be transformed to other branding issues.
[16:30] <scott-work> i didn't see him say anything about changing the description, astraljava 
[16:31] <scott-work> i changed the description in the bug
[16:31] <scott-work> am i being presumptuous about the bug?
[16:32] <scott-work> did colin say it might be possible to update this before final release?  or was he deferring it until p-cycle?
[16:32] <scott-work> s/p-cycle/q-cycle
[16:58] <astraljava> scott-work: No, I don't think you got the point. My "complaint" was about the dash in the name of our distribution. Colin said he wasn't sure there was anything he could do, as it was so tied to the cdimage thingies, ie. very low-level stuff. Hence I'm afraid it's pointless in adding more stuff in that bug, regardless whether they refer to branding or not.
[17:16] <astraljava> scott-work: Or is it so that the distribution-logo dependent on the cdimage as well? I wouldn't know, but if it was, then the change in the bug description would be totally justified.
[17:21] <astraljava> scott-work: ...and there you have it, Colin commented on the bug.
[17:58] <scott-work> astraljava: aye, i understand now
[17:58] <ttoine> astraljava, scott-work, the beta 2 is available. Should I make a new fresh install ??
[18:19] <astraljava> ttoine: It would be good, for further bugs are still to be found,  I'm sure. :)
[18:20] <knome> astraljava, are you saying you have hidden bugs in the ubuntu studio? oh my... :)
[18:20] <astraljava> knome: Oh bugger off, you <beep>ing <beep> <beep>!
[18:20] <knome> khihihi
[18:21] <ttoine> astraljava, I think I will do a fresh install. at the moment, I did an update. Is there anything to change to be an on the beta 2 from a beta 1 ? just make a dist-upgrade is enough ? Or should I change the repositories ?
[18:21] <astraljava> ttoine: No, just as usual, the packages are updated, nothing else.
[18:21] <knome> ttoine, just do any pending package updates
[18:22] <ttoine> astraljava, I was not sure. so actually the beta 2 is just a kind of daily build ?
[18:22] <astraljava> ttoine: In a way, yes. A snapshot, if you will.
[18:23] <ttoine> astraljava, ok. sometimes, I think I ask idiot question
[18:23] <astraljava> ttoine: Not by any chance. It's not obvious, unless you're following the development closely.
[18:24] <ttoine> astraljava, is there any stuff you want me to check in the beta 2 ??
[18:25] <astraljava> ttoine: Not really, I'm not aware of any known bugs. Just test it to its limits. :)
[18:26] <ttoine> astraljava, sure, I'll do that ;-))))
[18:27] <astraljava> ttoine: Great, thanks! :)
[18:29]  * ttoine is dreaming for a minute to create a company offering Ubuntu Studio workstation and laptops 
[18:31] <astraljava> That'd be sweet, yes. :)
[18:31] <ttoine> the main problem would be to find a good motherboard with no irq problem
[18:32] <knome> risky though, if astraljava has been hiding the bugs
[18:32] <ttoine> knome, ;-)
[18:32] <astraljava> Probably. Take a look at the stuff mentioned on openoctave site.
[18:42] <ttoine> astraljava, I just had a look at the openoctave project. Is there anything about hardware ?
[18:43] <astraljava> ttoine: I'm not sure, but I bet the Wendy's studio setup is free of any conflicts. :)
[18:44] <ttoine> astraljava, Wnedy ?
[18:45] <ttoine> Wendy ?
[18:46] <astraljava> ttoine: http://www.indiegogo.com/OPEN-OCTAVE-STUDIO-You-are-the-music-We-are-the-means
[18:47] <astraljava> ttoine: Scroll down a bit. That's what you get for $10k. :)
[18:53] <ttoine> astraljava, yes, ok. too bad the brand of the mother board isn't named ;-)
[18:53] <astraljava> ttoine: I'm sure they will tell you if you email them. :)
[18:54] <ttoine> astraljava, just speaking of hardware, I am amazed because everybody use Intel cpus... but Amd are cheaper for the same power, need less electricity and heat more, meaning less fan noise.
[18:55] <ttoine> but maybe a full Intel (gpu included) would be the best to produce audio..
[18:55] <astraljava> ttoine: Sure, but they're still a bit behind in processing power. 
[18:55] <ttoine> but which applicaiton really use hyperthreading ??
[18:55] <astraljava> True. I'm not sure either.
[18:56] <ttoine> at the moment, AMD is leading the cpu market for hyper computing centers
[18:56] <astraljava> Ok, I'm not up-to-date on such matters.
[18:57] <ttoine> astraljava, I try to do my best to be up to date but it is very hard
[18:58] <ttoine> the best for performance would certainly be amd cpu with nvidia gpu. but the matter is more about the main chipset (usb, sata, pci, etc...)
[18:59] <ttoine> astraljava, anyway, thanks to the link to Open Octave. It seems to be a great project. Maybe we should consider to have it in Ubuntu Studio, if it is possible
[18:59] <astraljava> ttoine: I agree, and will bring it up when planning for Q dev cycle.
[19:36] <len> astraljava, congrats on the job.
[19:37] <astraljava> Thanks, Len!
[19:37] <len> ttoine scott-work and all, re testing beta 2, I have had problems with the Mar 28 ISO. With qjackctl not starting jackd.
[19:38] <len> I did not test the live session. And it was after the new kernel installed itself before I tested it.
[19:38] <len> It was working fine before, so this is really something to watch.
[19:39] <len> I am DL todays ISO and will check Live and install. I will also try using ardour to start jackd to see if it is just qjackctl
[19:43] <astraljava> len: I'm afraid there is no updates to the images. We will have to debug the qjackctl bug outside of the general development of the distribution.
[19:51] <scott-work> len: did you mark bug #925257 as 'incomplete' ?
[19:57] <ailo> len: You could try starting jack from the command line. Only, qjackctl is probably set to use jackdbus, so there are two optional commands to use when starting jackd.
[19:58] <ailo> len: First, check which audio device you want to start. Either look in qjackctl, or do: cat /proc/asound/cards
[19:58] <ailo> Then start jack like this: jackd -d alsa -d hw:0
[19:58] <ailo> If hw:0 is the card you want to start with
[19:59] <ailo> Actually, I've never started jackdbus from the command line
[19:59] <ailo> Have to see how that works
[20:05] <ailo> jackdbus is cool, but I just hope it's not messing up regular jackd. Have to look more into that
[20:12] <ailo> Seems like you need something to control it. Regular ardour was not aware it was running. Just running jackd for a moment from the command line seems stable, but this is not US. Just regular Ubuntu, with the pa bridge installed
[20:12] <ailo> To start jackdbus you just do: jackdbus auto
[20:12] <ailo> But that doesn't get you anywhere
[20:14] <ailo> len: So, if you just want to start jack, just start it like I said: jackd -d alsa -d hw:(?)
[20:14] <ailo> Also, you could try disabling jackdbus from qjackctl to see if that helps
[20:14] <ailo> That will of course only affect qjackctl
[20:15] <ailo> jackdbus usually stays running for me in the background after a crash, so make sure to kill it if that happens