Update, so after a nights configuring I think I know wherein the problem lies. :), I added Jack to the tray and now, when I start it, it gets completely red. I checked this up and supposedly it has to do with xruns(?). I also noticed that it helps changing the frames/period setting, but only to a degree(even at highest it's no good). I see now that this is not strange at all since it's the xruns that are causing it to slow down in the first place... Now all I have to figure out is why the xruns are being sent. Also I noticed something when starting alsamixer, I only have the masterbar. //paco <div class="gmail_quote">On Fri, Mar 6, 2009 at 10:21 PM, Robert Klaar <<a href="mailto:nim.batu@gmail.com">nim.batu@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Hi there again! Been configuring audio now for the most of my friday-evening, everything works fine except it doesn't :(. Pulseaudio works, mediaplayers routing to pulseaudio too, but things like Ardour, Hydrogen, everything Jack-based doesn't. It lags when I try to use any samples and everything that's not working can in one way or another be related to Jack. When I started up a new project in Ardour, a notice came up stating that I had locked my memory or something, I looked up how to unlock this and now the notice is gone but nothing has changed with how it sounds, allthought it seemed reasonable(I'm sitting on a dual core 2.3 ghz with a ram of 3 g so I find it hard to think anything's wrong with the hardware per sey), I also checked with system monitor and it is hardly working it would seem when running jack. Also Jack shows, in the Jack-ctrl window something like 1(249), "249 is increasing", don't know if this is normal or not since I'm new to the whole thing. Anyone care to take a guess?... so that I might go out and get oen or two beers at least this friday evening :)... //paco </blockquote></div>