Hi All,
Bristol itself does not fall back to ALSA, but the compilation did not
include the Jack code (will upload a fix today). Without the Jack code in
the executable (try 'ldd $BRISTOL/bin/bristol' and look for libjack) then
there is per se no support and we drop through to the audio device, this is
correct operation for the compiled binary and the fix is for me to be a
little wiser in compilation. I will add a flag to the effect of printing an
error message when Jack is selected and the libraries were not included in
the compilation. This first release only looked for Jack headers and
libraries in the default location, /usr/local/ and if they could not be
found there then tough. The fix is just for me to look a little bit further
than the end of my nose :-)
Bristol does start jackd if it is not active, however since this us a
function of the jack library then unless it is compiled with the application
this will obviously not work either.
Nick
From: Lee Revell <rlrevell@xxxxxxxxxxx>
To: A list for linux audio users <linux-audio-user@xxxxxxxxxxxxxxxxxx>
CC: nickycopeland@xxxxxxxxxxx
Subject: Re: ANN: Bristol 0.9.4
Date: Thu, 20 Apr 2006 13:57:23 -0400
On Thu, 2006-04-20 at 10:16 +0200, Thomas Kuther wrote:
> Hmm just tried 0.9.4-1.src.041906 compiled as you explained above, but
> i
> don't seem to be able to get it to use jack.
> i did:
> $ startBristol -b3 -jack &
> or -audio jack
>
> but it starts using alsa.
> Any hints? :)
>
Nick,
I think this behavior of falling back to ALSA is confusing - most users
would expect Bristol to fail to start if -jack is specified but it can't
find the server.
Lee
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
