> Whether a specific input is routed to a specific output is made visible > when you click on the black square below a name like In 1 where it > probably says A1 1+2 on your setup if you're running default conditions. > You'll get a list of outputs. Any output with a check mark has some > amount of this inputs signal routed to that output. hmmm - this makes me think to go check if things aren't routed to multiple places > OK, so now I need to ask what you mean by 'channels'. There are three > 'channel 1's ' in hdspmixer - In 1, Out 1 and A1 1. Are you seeing this > audio on Out 1 when Ardour plays audio? Do you see Out 1 audio making it > to A1 1? ahh - to clarify (if I can!) - when I'm referring to channel/track 1 on ardour, that's in ardour, of course, and then when I say it shows up at channel 1 on the board, that's on my digital mixer - not on hdspmixer - during the tests where hdspmixer was running, I wasn't looking at it, partly because I'm a dolt, partly because it didn't matter to me for some reason, and partly because I believe in my make, the part that was broken was metering, so I'm not sure I would've been able to see the signal (this is something that I just remembered upon waking up this morning) of course, I also did a bunch of testing with hdspmixer not running > This sounds like you're possibly not running hdspmixer 1.3. In an xterm > type 'which hdspmixer'. IF you get /usr/bin/hdspmixer, I think you have > the wrong one. IF you get usr/local/bin/hdspmixer then you are probably > OK. huh. duh. I didn't think of that. I assumed I had no copy of hdspmixer before I downloaded your 1.3 tarball. perhaps 1.3 never did install, and I had 1.1, and that's what I'm running. thanks :) (remember I had unclean making going on when I was compiling and installing) > Provide an lspci output so we can see that you've got the right > firmware. firmware rev 65 - I'll go get an lspci later to confirm > Provide the output of 'cat /proc/asound/card0/hdsp '. If you see 2 > status and two control registers then you have at least partially the > new driver. (I think) If you don't, then something is definitely a bit > off. *nod* > It does actually. I mostly think that if you are doing things right with > the tools them you are still running the wrong software somewhere. > Probably your hdsp.o file isn't the right one is my guess, but we'll > just have to find out. *nod* ok this is good info - thanks :) I'll be back atcha with a report in a while...
