I have been through the most of the posts here and yet have seen nothing about relative continuous control (I could have missed it). Am I the only one trying to get relative CC from the Softstep ? (Ableton users, Live 9 does support relative CC mapping!)
So here are my findings : I figured out 2 different ways to achieve relative CC using only 1 PAD, but in each case, I get a weird irregular flow of midi data stream from the softstep, as if the midi output speed of the softstep was irregular after a while. Let me explain :
1- Relative CC via HOSTED Mode - using Signed Bit relative mode
This trick is kinda working but it is ugly programming of the softstep.... but still, it works...
Modline 1/ Source : TOP/ Gain : 2/ Offset : 0/ Table : Lin/ Min : 1/ Max : 3/ Destination : whatever CC you want on whatever channel.
Modline 2/ Source : BOTTOM/ Gain : 2/ Offset : 64/ Table : Lin/ Min : 65/ Max : 67/ Destination : same CC than modline 1
Why is it ugly ? Because when we step on the Top of the Pad both modlines send data : modline 1 sends a "+2" message and modline 2 sends a "-1" message, which will results in an increase of the DAW parameter but a lot of unuseful data is send.
Also I think that if we are in hosted mode, relative CC might not be so relevant because of the fact that the softstep keeps the last parameter of the pad in its memory. A Y increment would do the trick then, but I have not tried it, because I am a STANDALONE mode user !
2 - Relative CC via STANDALONE Mode - Using Signed Bit Relative Mode
In standalone, there is no Top and Bottom source mode. So this turns out to be a geek solution : Bome's Midi Translator is involved, it takes 4 translators to get one pad doing a relative CC. If some of you are interested, I can give you the code as a reply. But since this post is getting quite long, I skip to the third part which is :
3 - Softstep irregular output speed ?
I noticed this since using a relative CC, I had to step several seconds on a pad to get to the value I desired. But in both cases, after a 1-2 seconds press, the CC value seems to get stuck (as if no more data was sent by the softstep) and if I keep pressing it gets back to normal after another 1-2 seconds. It results in a not smooth modification of the CC value. When the CC value gets stuck, if I stop pressing and repress the pad, then it works agian fluently for the next 1-2 seconds.
Did anyone noticed this "bug" ?