[00:20] <zequence> OvenWerk1: I have one as well, but I don't use it much and don't have it have home
[00:20] <zequence> Will do some testing though
[00:20] <zequence> Nice breaktrough
[00:51] <OvenWerk1> zequence: sounds good. I was begining to think not much was happening ALSA wise. (not just firewire, but in general)
[00:52] <OvenWerk1> I guess as always the mainstream sound is first. (HDA internal)
[02:01] <holstein> OvenWerk1: i know, and mine is out on load to test with right now
[02:01] <holstein> out on loan*
[02:01] <holstein> im going to try and grab it monday
[02:01] <holstein> i have 14.04 installed on my production rig
[02:02] <holstein> i could do some partition to test those alsa drivers.. that would be *great*!
[02:20] <OvenWerk1> The only thing that puzzles me about alsa/jack and lowlatency is that cpu speed changes cause problems.
[02:21] <holstein> OvenWerk1: yeah, i disable that..
[02:21] <OvenWerk1> There must be a counter in use that counts cpu cycles
[02:21] <OvenWerk1> Me too, I get sub ms latency with it off.
[02:22] <OvenWerk1> Shouldn't have to though... that is really a bug of sorts... but I don't know where the bug is.
[02:22] <holstein> OvenWerk1: how much worse with it on?
[02:23] <OvenWerk1> with it on I get spurious xruns up into 10ms
[02:23] <holstein> thats about what i have found
[02:24] <OvenWerk1> I suspect it is one of the kernel timing services.
[02:25] <OvenWerk1> It is actually worse on my new 4 core system than it was on the old P4 single core.
[02:26] <OvenWerk1> But with the cpu set to solid speed the new i5 is really stable
[02:28] <holstein> yeah, driver support is really where its at
[02:28] <holstein> i have a nice lexicon omega, but, i cant get it below 40ms
[02:28] <OvenWerk1> USB?
[02:29] <holstein> yup
[02:29] <holstein> whic is fine for what i use it for
[02:29] <holstein> i keep the firewire rig packed up ready to travell
[02:29] <OvenWerk1> YaI thought I had looked at one
[02:29] <holstein> i leave the lexicon plugged in all the time
[02:34] <OvenWerk1> Anything is better than internal... no matter how high a sample rate it boasts :P
[02:34] <holstein> well, at least it has the connectors i want
[02:35] <holstein> i bet i get lower latency with the internal though ;)
[02:35] <OvenWerk1> That is another problem with internal audio
[02:35] <holstein> but. yeah. i like the lexicon OK
[02:35] <OvenWerk1> internal HDA get 64frames only with 3 periods is the best I can do with any I have played with.
[02:36] <OvenWerk1> 128 frames is more stable.
[02:37] <OvenWerk1> USB has to be the only USB device on a USB bus and that bus has to have it's own irq. On my netbook There was only one USB plug that was stable at 64/2
[17:10] <OvenWerk1> I have a question with regards to CPU speed. In audio the user needs to be able to set the cpu speed. I am thinking about how best to do this.
[17:11] <holstein> OvenWerk1: i'll test with you, if you like
[17:12] <holstein> OvenWerk1: i installed cpufrequtils ? i think it was.. and i have 2 shortcuts on my desktop to run in terminal.. i put in my password, and get what i need
[17:12] <OvenWerk1> My thought is there needs to be an easy control that can set speed rather than just ondemand/performance
[17:12] <holstein> its not elegant, but, its what ive been doing, and it works for me
[17:13] <holstein> OvenWerk1: what about, JACK related? some tickbox that allows JACK to set it when running?
[17:13] <holstein> thats probably not cool.. 
[17:13] <holstein> OvenWerk1: but, yeah.. it would be nice if the user could set it
[17:13] <OvenWerk1> There may be some systems (lap tops?) where performance brings the temp too high.
[17:14] <OvenWerk1> So being able to set a speed that is steady but not to hot would be nice.
[17:15] <OvenWerk1> My thought is a dropdown from systray that has some options for speed.
[17:15] <holstein> OvenWerk1: i like that
[17:16] <OvenWerk1> The idea of using a password all the time to me is anoying, it should be possible to make it so that is not needed without compromising security
[17:17] <holstein> OvenWerk1: right?! i always thought that too
[17:17] <holstein> may be similar to the audio group thing we override
[17:17] <OvenWerk1> My original thought was to use run levels because I also wanted to be able to shut cron off for low latency work. but I have not noticed any problems with it on my new hardware
[17:18] <holstein> interesting..
[17:19] <OvenWerk1> So I think I will make a program in /usr/sbin that needs SU to work but run it with polkit and passwording turned off.
[17:19] <OvenWerk1> The GUI will be user space.
[17:19] <OvenWerk1> (in pyqt4)
[17:20] <OvenWerk1> I already have something like that that changes jack's latency on the fly and enables or not the pulse -> jack bridge
[17:22] <OvenWerk1> The idea is that jackdbus starts when the session does and acts as the backend for pulse for the desktop.
[17:24] <OvenWerk1> At low latency pulse streams to it's dummy output and basically idles.
[17:26] <OvenWerk1> I have two modes with the jack bridge on, desktop and phone use. The second one is low latency with pulse for use with things like skype which is a major use for people doing radio stuff
[17:27] <OvenWerk1> I set up three non-pulse options for live (lowest latency), recording and mixdown. My plan is to have a config screen that the user can set the latency for each mode with.
[17:29] <holstein> nice.. i like that
[17:29] <OvenWerk1> I don't know if there is an easy way to find out what the user's audio IF limits are or not.
[17:30] <OvenWerk1> I have 4 devices and all have different limits :)
[21:37] <OvenWerk1> holstein: Why do people think lowlatency = performance?
[23:38] <holstein> OvenWerk1: i know, right?!
[23:39] <holstein> OvenWerk1: that guy wasnt ever interested in audio performance, though.. which is fine, but i was treating it like that
[23:39] <holstein> if he had said "im running a server" i would have always insisted on a server kernel..