Very encouraging first test. I noticed that the Faderport WAI is already following the Sonar selected bus, which was the whole reason for this venture
. Details below:
1) Mapping of button functions looks to be correct so far, except for the lights. See #3 below.
2) All transport buttons are working properly.
3) Lights are working but mis-assigned. Rundown as follows:
Mute->lights up channel select R
Solo->lights up Output (channel/bus button)
Arm->lights up fader 'Off' button
Output->lights up solo button
Fader 'Off' ->lights up Arm button
Shift->lights up transport stop button
Rewind->lights up transport FastFwd
FastFwd->lights up transport Rewind
Stop->lights up shift (default state on load)
Play->lights up 'Punch' button
'Loop' button light is triggered by the first touch of the volume fader and remains lit until Sonar is closed and restarted
4) Pan is working perfectly. There is no LED ring on the surface for the encoder.
5) Fader behavior:
-motor moves all the way to the top of its path (6.0) on any track with a volume of more than '-INF' and all the way to the bottom of its path on a track with '-INF' volumne
-after one track's volume is adjusted from the surface, the fader motor seems to stop responding altogether and will not work again until Sonar is closed and restarted
-The fader does work to adjust track volume, but only when the current track's volume is 'met' by the physical fader. I'm guessing this would be resolved when the motor responds properly to the current track volume position.