That’s a bummer, but based on everything I’ve read, it makes sense. Novation should have probably mentioned that in their revised manual… or even in the Cubase documentation. Knowing that motorized faders are expected with the HUI protocol would have saved me time chasing this wild goose.
I’ll play around a bit with the layer switching approach you mention. I had originally mapped the transport to use CC rather than MMC, and had custom fader mappings. It was working fine, but another member convinced me I should be using HUI (citing page 31 of the manual for the Impulse). So far the only benefit I’ve found to going this route is that the transport controls aren’t being recorded with the track (since HUI isn’t sending CC commands).
Probably going to ditch the HUI thing and go back to trying to filter out or tinker with putting the transport commands I assign on another channel to prevent them from being recorded.
And oh… the lack of relative encoder support pains me. (I had an email exchange with Novation about that - and they were basically like “sorry… doesn’t work”, even in HUI mode) The frustrating thing is that in “Ableton” mode, the relative encoders work just fine. Rascals. 