CTAG Beast I/O and Jack Port Mappings

I've observed unexpected Jack Port to CTAG I/O mappings as I've learned more about how the CTAG Beast is set up.

I'm using Henrix' v0.1.2 Debian SD card image

After booting, I load the ALSA drivers sudo ./load-ctag-beast-16ch-drivers.sh

I start Jack using jackd -P75 -dalsa -dhw:0 -p1024 -n2 -s -r48000 -i8 -o16 &

By temporarily connecting Jack inputs to outputs, I observe the following mappings...

CTAG Top... Board In 1&2 / Beast In 1&2 = JACK In 5&6
CTAG Top... Board In 3&4 / Beast In 3&4 = JACK In 7&8
CTAG Bottom Board In 1&2 / Beast In 5&6 = JACK In 1&2
CTAG Bottom Board In 3&4 / Beast In 7&8 = JACK In 3&4

CTAG Top... Board Out 1&2 / Beast Out 01&02 = JACK Out 01&02
CTAG Top... Board Out 3&4 / Beast Out 03&04 = JACK Out 03&04
CTAG Top... Board Out 5&6 / Beast Out 05&06 = JACK Out 05&06
CTAG Top... Board Out 7&8 / Beast Out 07&08 = JACK Out 07&08
CTAG Bottom Board Out 1&2 / Beast Out 09&10 = JACK Out 09&10
CTAG Bottom Board Out 3&4 / Beast Out 11&12 = JACK Out 11&12
CTAG Bottom Board Out 5&6 / Beast Out 13&14 = JACK Out 13&14
CTAG Bottom Board Out 7&8 / Beast Out 15&16 = JACK Out 15&16

So the Jack outputs are physically mapped how I would expect, but the inputs are reversed (top & bottom boards swapped).

This caught me out at first because I was expecting Jack's inputs 1&2 to be on the top board along with it's outputs and so wasn't getting any sound with my stereo in & stereo out loopback tests.

Hope this helps save someone else the time!