[LAU] Linux audio app design: The nature of xruns

lanas lanas at securenet.net
Mon Dec 28 15:24:02 EST 2009


Le Lundi, 28 Décembre 2009 20:17:21 +0100,
Guido Scholz <guido.scholz at bayernline.de> a écrit :

> as far as I understood your experiment, you compared these two setups
> to conclude "QARecord is to blame":

Not really.  And I forgot to mention jackmix which looks like another
quick hack.

This is because it was not much of an experiment to start with but
rather an observation derived from finding a way to record the song
without so many xruns.

As such, the observation was quite clear: kernel real-time
capabilities, although they might play a role somewhere, had nothing
to do in producing xruns since switching applications resolved the
problem.  From that observation then a question arose: there must be a
bad way and a good way of writing a Linux audio/jack application: what
is it ?

> For mathematical reasons I would like to get your result from this
> alternative setup (also giving better access to a root cause):
> 
>   3) noise -> jackmix -> Ardour -> wav-file

Indeed.  That's the possibility I haven't explored since I think the
result of the observation was to see that there's a bad and good way of
writing such applications.  Now, that the bad way lies with jackmix
and/or Qarecord is a second point that has more to do with technical
performance in the context of writing such an audio/jack application.
Which is not the case at the moment.  I'm currently working on a project
that has nothing to do with such matters but I consider for a next
project to make a Linux jack application that would ease my music
making as I find there are some things that could make it easier to
make music.

> Some other interesting information would be, what program versions
> (jackmix, QARecord) are you using?

Hmmm.. I'd disagree with this insofar as debugging these apps is
certainly not the matter.

Tschüß.




More information about the Linux-audio-user mailing list