Content-Type: text/plain; charset=ISO-8859-1
There is no difference between jack_iodelay and *older* versions of Fons'
original jack_delay, other than the formatting of the output.
He has noted in the past that we should upgrade the code in jack's utility
folder to use his newer version.
On Sun, Sep 29, 2013 at 3:57 AM, Patrick Shirkey wrote:
Content-Type: text/html; charset=ISO-8859-1
There is no difference between jack_iodelay and *olde=
r* versions of Fons' original jack_delay, other than the formatting of =
the output. He has noted in the past that we should upgrade t=
he code in jack's utility folder to use his newer version.
Sep 29, 2013 at 3:57 AM, Patrick Shirkey <pshirkey@boosthardware=
On Sat, September 28, 2013 6:53 am, Fons Adriaensen wrote:
The PA Devs are aware of my results and have been very helpful so far=
are getting into a murky area where the code has not been worked on
recently so it takes time to refresh on the specifics.
With the differing results from jack_iodelay and jack_delay that has
unfortunately thrown a spanner in the works. Now I have to *prove* that
the new results are completely reliable. That's not an attack on your
work, just that now I have a new variation that needs to be fully
explained to make sure there is no doubt, otherwise it's likely that
fingers will point in other directions.
Some additional empirical data and test results from other people will be
I have compiled the test procedure into a basic document now:
To recap some of the "results" so far are :
- The combination of JACK + PA is stable on my machine for several days in<=
a row even at 64 frames/period and using hda_intel onboard device
- PA Stream Buffer can give consistent 10ms latency
- I am now seeing latency between 16ms to 75ms with the new version of
- There appears to be a bug in the official jack_iodelay which is part of
the jack utility app suite.
Boost Hardware Ltd
Linux-audio-dev mailing list