From: Stefan Richter <stefanr@s5...> - 2010-12-20 23:37:43
step 1 towards a FFADO that has a hint of usability: If jackd's
firewire driver fails to start up, jackd's log should contain at least
a rough indication what failed. Without a trailing -v3 or -v6 or any
other non-default parameter on the jackd command line.
For example, I remember how jackd refused to start with my Saffire Pro
24 when I got it. The reason was that the Pro 24 was sold with an
ancient firmware that FFADO no longer supported (or never did) and had
to be upgraded. Of course I only learned that after I remembered to
add the verbosity parameter.
Such a straightforward failure condition should cause a clear error
message in jackd's log, without having to add non-default parameters
to the driver first.
Whenever a user brings up this tired "firewire ERR: Could not start
streaming threads: -1" message (and nothing more) on IRC or ffado-user,
somebody needs to tell him the same old thing again and again and
again: Please retry with -vSomething appended to the command line.
This wastes the user's time and the time of anybody who is inclined to
trouble-shoot the issue with the user. Sure, most of the time some more
questions will have to be asked, but why start from null?
-=====-==-=- ==-- =-=-=