[02:26] <smartboyhw> zequence: Speaking about voting, there's a different voting system called CIVS.
[02:29] <smartboyhw> Which the Kubuntu Members will use to vote on the Kubuntu Council members.
[02:31] <smartboyhw> Technically speaking LP votes are better in doing Project Lead cotes 
[02:32] <smartboyhw> s/cotes/votes/
[02:32] <kubotu> smartboyhw meant: "Technically speaking LP votes are better in doing Project Lead votes"
[02:50] <len-dt> smartboyhw, I think the idea is that we need to grow the team large enough that a vote/poll is even needed in the first place.
[02:59] <smartboyhw> len-dt: That's a +1. But in Xubuntu' case, their users LP team vote on their Project Lead 
[02:59] <smartboyhw> We DO have that.
[03:01] <smartboyhw> However the problem will be that whether some people will get votes more equal then the others 
[03:03] <smartboyhw> I think, though, as zequence is still active he will still be the best choice for Project Lead 
[03:05]  * smartboyhw is thinking to do a thank you section for the 13.04 final announcement.
[03:06] <smartboyhw> Off, back in 3-4 hours
[07:09] <smartboyhw> Hello!
[07:17] <smartboyhw> zequence: Do add me as friend on Ubuntu Forums:P
[16:52] <len-dt> zequence, holstein,  phasex is buggy. Sent a message to the developer. The preferences do not save. The only way to set preferences in phasex that will still be there next time it is started is to manually edit the file
[16:53] <len-dt> The file to edit is ~/.phasex/phasex.cfg... should someone ask for help with this.
[16:55] <len-dt> I think the developer has copied over the patch save dialog where the the config save dialog should be and just not changed the values to reflect it's proper use. It seems odd that you would be able to save/load the patch in two places but not be able to save the config :)
[21:15] <len-dt> Wow!, that was fast. Qjackctl 0.3.10 was released April 1 2013 and when I look at the one running in precise it says 0.3.10 build April 5 2013.
[21:26] <zequence> len-dt: That is fast. backport?
[21:27] <zequence> len-dt: Or, are you using some PPA
[21:28] <zequence> len-dt: Doesn't look like it's been released from doing a package search
[21:28] <zequence> I'm just about to boot into precise to test kernels. Will check
[21:31] <zequence> len-dt: I guess you have kxstudio ppa. 
[21:31] <len-dt> I may.
[21:31] <len-dt> Forgot about that. I haven't booted this drive for a bit.
[21:31] <zequence> ls /etc/apt/sources.list.d/
[21:32] <len-dt> kxstudio-team-ppa-precise.list       opera.list
[21:32] <len-dt> kxstudio-team-ppa-precise.list.save  shnatsel-zram-precise.list
[21:32] <zequence> len-dt: I doubt anyone is updating any of the pro audio packages on stable releases. Not even PA gets updated very often (last updated autumn last year)
[21:34] <zequence> PA had an update in November for precise
[21:34] <len-dt> Does jack (not qjackctl) have any way of changing the name of it's ports?
[21:34] <zequence> No idea
[21:34] <len-dt> Ah, I would love to rename ports 5 to 10 on my card.
[21:34] <falktx> I updated qjackctl for kxstudio, yes :)
[21:35] <len-dt> April 5 no doubt :)
[21:35] <falktx> len-dt: port-aliases kinda allow that, but qjackctl doesnt do that
[21:35] <len-dt> qjackctl allows it, but they don't show up in other programs.
[21:35] <falktx> yep, it doesn't use port-aliases
[21:36] <len-dt> I want it to show in Jack to other programs.
[21:36] <falktx> I support aliases in my catia app
[21:36] <len-dt> I have a delta 66 and ports 5 to 8 are not used. and 9-10 are spdif.
[21:36] <falktx> but I think it's better to enable "hardware aliases" instead
[21:37] <len-dt> How do I do that?
[21:37] <falktx> I have it enabled for kxstudio's jack2. use cadence to configure jack and enable it
[21:37] <falktx> sadly qjackctl doesn't read or set jackdbus settings either
[21:39] <len-dt> Well it does a few like rate and -p etc., but not all
[21:39] <len-dt> It does allow the use of net as a back end but does not allow changing the settings.
[21:40] <falktx> no, qjackctl doesn't read jackdbus settings
[21:40] <falktx> as in, the one official jackdbus config in ~/.config/jack/
[21:41] <len-dt> Hmm, OK, I guess it uses dbus to set things but then reads whatever from jack directly.
[21:41] <zequence> qjackctl has its own settings, and also, edits ~/.jackdrc
[21:42] <zequence> .config/rncbc.org/QjackCtl.conf
[21:42] <len-dt> Ya, When jack has settings changed through dbus it saves them too.
[21:42] <falktx> yes, but the problem is that it doesn't read them
[21:43] <falktx> so the settings are not shared with other jack config tools
[21:44] <len-dt> Ya.
[22:22] <len-dt> Hmm, I can tell jack the number of ports I want to use, but not which ports I want to keep if they are non-contiguous.
[22:23] <len-dt> For example 6 ports 1-4 + 9-10
[22:23] <falktx> jack doesn't do that afaik
[22:23] <len-dt> It seems that way.
[22:31] <len-dt> Still 1.9.8 version of jack. Supports CELT but not opus.
[22:41] <len-dt> Nope it says 1.9.9.5 , I thought 1.9.9 came with opus support, release notes say "- Add opus support to NetJack2."
[23:25] <len-dt> zequence, I know it has been sometime since we looked at midi jitter.
[23:26] <len-dt> The Jackd faq has this to say about it: "There is no canonical answer to that. The kernel clock freq (dev.rtc.max-user-freq, dev.hpet.max-user-freq) is irrelevant for JACK, JACK-midi and JACK's MIDI-backends including a2jmidid. However, applications that directly use ALSA-MIDI or ALSA-sequencer may be affected by this. There are many related factors. It depends which timer is used by the soundcard's driver (snd_timer, snd_hrtimer) and how the appl
[23:26] <len-dt> ications schedules ALSA-MIDI data processing."
[23:55] <len-dt> zequence, it would seem we should try to set things up to default to using jack midi if they support it.