Messages in this thread | | | Subject | Re: Overruns are killing my recordings. | From | Lee Revell <> | Date | Fri, 28 Oct 2005 14:43:25 -0400 |
| |
On Fri, 2005-10-28 at 07:52 -0700, Mark Knecht wrote: > On 10/27/05, Lee Revell <rlrevell@joe-job.com> wrote: > > On Thu, 2005-10-27 at 17:00 -0700, Avuton Olrich wrote: > > > aggh. Sorry for all the noise, > > > > > > I have all my drives on a linear raid and I had hdparm set to put my > > > IDE drives to sleep after a while, I didn't put it together because it > > > was happening in the middle of recording. > > > > Hey, I think it's a testament to the progress that has been made in the > > past year and a half that people now consider audio dropouts in a "known > > good" app like ecasound to be a kernel bug. For the longest time the > > answer was "linux isn't an RTOS, deal with it". > > > > Lee > > Lee, et. all, > Could this possibly be part of what is causing my xrun problems? I > had a huge rash of xruns yesterday. I seem to run into issues after > longer times of inactivity. I hadn't considered this possibility > before.
I really doubt it. It's more likely that the xruns are caused by a bug in the new ktimers system. I am seeing "xruns" here too with -rt1, but the latency tracer does not report anything over ~120 usecs. Previous to all the ktimers/HRT stuff going in, I was xrun free for months.
The reason I think it's a ktimers bug is because sometimes JACK reports an xrun of negative length which I'd NEVER seen before.
I suspect this might all be fixed in the latest -rt patch but I have not had time to build it.
Lee
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |