On Nov 5, 2013, at 1:33 AM, Dan Stowell <danstowell+sc3@xxxxxxxxx> wrote:
Thanks! Do they included dependencies for working versions of jack? I have yet to make a combination of jack + alsa_out make even the slightest chirp. I’ve been independently trying to test jack with ecasound. I can play a .wav file with ecasound like this: ecasound -i test.wav -o alsa But with ecasound -i test.wav -o jack and jackd is running like this: jackd -p 8 -d dummy and alsa_out is running like this: alsa_out -q1 No audio ever comes out. By the way, to build on the pi, I had to make the following change: diff --git a/CMakeLists.txt b/CMakeLists.txt index dd4fc47..57463e2 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -108,8 +108,8 @@ option(FINAL_BUILD "Build as single source file." OFF) option(FFT_GREEN "Use internal 'Green' FFT lib rather than FFTW. (Not recommended.)" OFF) -option(SSE "Compile with support for SSE instructions." ON) -option(SSE2 "Compile with support for SSE2 instructions." ON) +option(SSE "Compile with support for SSE instructions." OFF) +option(SSE2 "Compile with support for SSE2 instructions." OFF) set(AUDIOAPI "default" CACHE STRING "Audio API to use (one of {default,coreaudio,jack,portaudio})") Looks like somebody hard-coded Intel flags, which of course make gcc barf on arm. Perhaps those could be made conditional on the architecture? - Patrick |