Re: [LAU] Test if Linux is ready for audio (realtimeconfigquickscan.pl script)

On Thu, Oct 22, 2009 at 02:32:17PM -0700, Scott wrote:

> >From the horse's mouth:
>
> > It has to do with Python's lack of support for signals in threads.
> >
> > https://bugzilla.gnome.org/show_bug.cgi?id=481569
> > http://dev.laptop.org/ticket/4680
> >
> > The Red Hat people have put a lot of work into fixing this, along with
> > Sugar.
> >
> > Python apps which initialize threads will end up waking every 1/10th
> > of a second, rather than idling properly.

So what ? Many apps wake up at that frequency or higher and don't
cause any problem at all by doing so. Every Jack app will wake up
at period rate, typically more than 100Hz.

The problem discussed in the links above seems to be related
more to PyGTK than Python in general.

Here at the CdS all the audio systems are controlled by multi-
threaded 'master' programs written in Python. The threads are
handling network connections and updating the wireless remote
control apps (running on EEE's) all the time, normally at 25
Hz or close. I've never seen an xrun here.

Hint: don't run NetworkManager.

Ciao,

-- 
FA
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@email-addr-hidden
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user