The way the octatrack works is that if you send it CC61, it sends out all its other current CC values.
Paulink, are you getting your octatrack to update your faderfox this way? I have a PC4. While it will keep up if a CC changes linearly on my OT, the PC4 seems not to accept jumps in values.
I was programming the midihub to transform the program change sent by the OT on pattern change into a CC61 back to the OT. Thought I could link a new part to the new pattern and totally reconfigure the faderfox with all the new CC values of the new part. The OT cooperated and sent the new CCs whenever the pattern changed, but unless they were only off by one from the old faderfox value, it wouldn’t update them.
Maybe I should turn smoothing off at the faderfox but that is its own tradeoff.