RME HDSP 9652

As you can see from the previous section, "numid=5" is responsible for opening up the channels for the convolver PC.

To ensure safety, all channels are closed first and only the required channels are then opened. This can be done with the following script, (courtesy, Hiroshi)

#clear all direct physical connections for safety
for ichannel in $(seq 0 1 25) do amixer -c 0 cset numid=5 $ichannel,$ichannel,0
done
#playback connections
amixer -c 0 cset numid=5 26,0,32768
amixer -c 0 cset numid=5 27,1,32768
amixer -c 0 cset numid=5 28,2,32768
amixer -c 0 cset numid=5 29,3,32768
The above script was commented out in my latest script as it causes some runtime error. I am trying to work out the reason behind....

Initially, I am confused the amixer script with the BruteFIR script. The 4 lines shown above is amixer script. In other words, physical input channels are named as 0,1,2,..., playback channels are 26,27,28,..., physical output channels (which are physically different from the above input channels) are named also as 0,1,2,...

amixer -c 0 cset numid=5 26,0,32768
amixer -c 0 cset numid=5 27,1,32768
amixer -c 0 cset numid=5 28,2,32768
amixer -c 0 cset numid=5 29,3,32768

The above amixer command means software (BruteFIR in our case) outputs to four channels 26,...,29, and they are connected to physical (ADAT) channels 0,...,3 respectively BY the above commands.

However, inside BruteFIR script, channels 26,...,29 are called 26/0,...,3.
So, in BruteFIR, the script should read

#output "llow", "rlow", "lmid", "rmid", "lhigh", "rhigh" { output "llow", "rlow", "lmid", "rmid" {
device: "alsa" { device: "hw:0";}; # ignore_xrun: true; };
sample: "S24_4LE";
channels: 26/0,1,2,3;
delay: 0,3,282,282;
# delay: 0,3,332,332;
dither: true;