-----Original Message-----
From: linux-audio-user-bounces(a)lists.linuxaudio.org on behalf of Simon W. Fielding
Sent: Thu 2/5/2009 12:33
To: linux-audio-user(a)lists.linuxaudio.org
Subject: Re: [LAU] Phonic Helix Board 12 FireWireMKIIcompatibility(linux/ffado)
From: Robert Jonsson [mailto:spamatica@gmail.com]
Sent: 04 February 2009 13:07
To: Simon W. Fielding
Cc: linux-audio-user(a)lists.linuxaudio.org
Subject: Re: [LAU] Phonic Helix Board 12 FireWire
MKIIcompatibility(linux/ffado)
That would be a good deed.
Probably Pete has more pressing needs than me, but
still. The things
I'd like to
know of the top of my head are basically:
- if it's relatively stable.
- no artifacts in the sound, clicks etc, recording for a while with
lowish latency
should prove "something"
- What kind of latency to expect, this might be a bit
of work to
determine. Not sure myself how to do it
other than tuning a complete system and bringing the
buffers down to
the lowest that are usable.
OK - I now have a working basic FC10 system - relevant details are :-
Hardware: Toshiba Tecra M3
Kernel: 2.6.26.8-1.rt15.1.fc10.ccrma.i686.rt
Jackd: jackdmp 1.9.1
ffado: 2.0-0.6.rc1.fc10.ccrma (libffado 1.999.40)
Initial cursory testing shows (no recording load, just an idle mixer with nothing
connected) :-
jackd -R -dfirewire -r96000 -p16 -n3 ... jackd won't even start - uses too much CPU
jackd -R -dfirewire -r96000 -p32 -n3 ... jackd won't even start - uses too much CPU
Both of the above seem to sometimes leave the 1394 bus in a strange state. A forced bus
reset using
gscanbus seems to fix it.
jackd -R -dfirewire -r96000 -p64 -n3 ... jackd starts - uses approx 70% CPU with xruns
every 10-20 seconds
jackd -R -dfirewire -r96000 -p128 -n3 ... jackd starts - uses approx 50% CPU - no xruns
jackd -R -dfirewire -r96000 -p256 -n3 ... jackd starts - uses approx 45% CPU - no xruns
jackd -R -dfirewire -r96000 -p512 -n3 ... jackd starts - uses approx 25% CPU - no xruns
This is all I have time for today - I'll try and do more later this week. If I've
missed any useful
details, please ask and I'll try to get them posted.
Cheers,
Simon