i don't to be able to compile alsaplayer. you seem to have hard-coded the paths to glib in the configure file (this is from configure itself):
CFLAGS="$CFLAGS -I$x_includes -L$x_libraries" CPPFLAGS="$CPPFLAGS -I$x_includes -I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/local/jack/include" AS="$CC" mine is in /usr/local, not /usr. i tried --with-glib-prefix and --with-glib-exec-prefix, but neither of them change the CXXFLAGS setting that results in: g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/X11R6/include -I/usr/include/glib-1.2 -I/usr/lib/glib/include .... these paths are not valid on my system. configure appears to use glib-config, checking for glib-config... /usr/local/bin/glib-config checking for GLIB - version >= 1.2.8... yes but glib-config says: % glib-config --cflags -I/usr/local/lib/glib/include -I/usr/local/include compare with the output above. i've hacked the configure script for now. --------------------------------------- >andy@phobos:/usr/local/jack/bin$ ./jackd -d hw:0,0 >creating alsa driver ... hw:0,0|64|48000 >ALSA lib conf.c:3218:(parse_args) Unknown parameter 1 >ALSA lib conf.c:3326:(snd_config_expand) Parse arguments error: No such >file or directory >ALSA lib control.c:570:(snd_ctl_open_noupdate) Invalid CTL hw:0,0 >control open "hw:0,0" (No such file or directory) >cannot load ALSA driver module > >Hmm, no ctl device for hw:0,0 ?? I'll dig into alsa_driver to see >where/why it fails. I wonder if ALSA has been changed to no longer support hw:N,M ? >Okay, is jackd doing clipping? I.e. does it ensure that output stays >between 1.000 and -1.000 ? All hell breaks loose when I connect multiple Nope. How and why could it do that? AFAIK, there are only a few ways to handle mixing: 1) take no action: the sum may or may not clip 2) clip the result 3) implicitly clip in the conversion back to h/w format 4) use compression on the signal 5) scale each input by a constant amount 6) apply independent gain control to each input i don't consider any of these except (1) as something that JACK would do. do you feel different? >clients to the same ports here. Garbled output, and probably some memory >overwrites since jackd usually segfaults after 3 or 4 connects. thats nothing to do with multiple ports, i believe.
