I just got a remote sl25 as my microkontrol simply didn't have enough scenes, or flexibility in assignment.
I love the sl, but I encountered an issue there that I had encountered with the Microkontrol as well.
When mapping a button (toggle or momentary) to a rotary, (I use this either for muting or punching sends or macros usually) I find that if I leave the range on the button set to min=0 max=127, it won't affect the parameter in the interface. However, if I set it to min=1 max=126, it works fine. Not a deal breaker, but a little weird. Anyone else see this?
The other issue I found (and this is only on the sl) is that when I have buttons set up like this, every third time the button cycles, it doesn't do anything. For momentary controls, presses 1 and 2 cause the parameter to cycle, but press 3 doesn't. Press 4 and 5 work, but not 6, etc. On parameters that are set to toggle, it's the same where press down/up #1 works as well as #2, but not #3.
The second issue is actually the one that reallly bothers me, as 33% of the time, when I go for one of these parameters, nothing happens. =FRUSTRATION.
Another question, has anyone here successfully set up the sl so that it shows up as a remote control surface twice? That is, where you modify the original automap template to send and recieve on the #1 ports and save it to another slot? I think this would be cool, as you could lock the surface into to plugins or racks, and toggle back and forth. I think it should work...
Lastly, does anyone know how to disable Ableton's behavior of automatically dumping sysex to the SL on bootup? I have modified the standard automap template so that I can have 8 layers with the same automapping, but discreet controls for static assignments (don't ask why... long story revolves around GURU patters), but without the MEM Protect setting enabled, every time I load ableton, whichever template is active is overwritten...
Thanks!
---EDIT---
I did the double control surface thing I was talking about, and it works! The only downside is that the SL gets kind of confused about which labels are supposed to be displayed in the interface, so they basically become useless, but the values for the controls that are automapped update as one would expect as you toggle back and forth between automap templates.