On 9/19/05, Billy Holmes <[EMAIL PROTECTED]> wrote: > Mark Knecht wrote: > > > everything caught up and worked well. Probably the same here. I expect > > it will be fine one of these days soon. > > take a look in the ck (ck-sources) mailing list: > > http://bhhdoa.org.au/mailman/listinfo/ck > > http://kernel.kolivas.org/ > > It's moderated by the author. They always have some talk about > interactivity which leads to audio talk. There are a few audio guys on > there that should be able to give you some ideas/links. ck tends to > attract audio and video people, because of it's low latency. From what I > can gather, audio people feel ck may not be perfect for audio apps, but > it's a good start.
Thanks. Yes, I've run ck-sources a few times in the past but not had good luck with it. I'm also suspicious that the problem I'm currectly seeing with the gentoo-sources AMD64 kernel is likely to not be solved by this. It seems right now that a simple emerge sync is causing xruns on this system implying to me some underlying problem with either hard drive activity or networking. since the hard drive is SATA and the networking option in the kernel marks the NIC driver as 'Reverse engineered - experimental' I'm not confident of fixing this problem in the immediate short term anyway. My thoughts right now: 1) kernel.org + rt patches 2) ck-sources 3) gentoo-sources-amd64 + rt patches not cleanly applied I may also investigate a different NIC. I have a email friend that runs a studio in Sydney. I helped him move from FC2 to Gentoo. We had xruns using some of the NIC stuff for his motherboard. When we found that was the problem he never had another problem. Thanks for your ideas. cheers, Mark -- [email protected] mailing list
