I am still learning my way around the SL MKIII - so there may be stuff I don’t completely have correct in this mini-writeup, but it feels like it’s not a bad idea, since there is a little misunderstanding in this thread.
- the keyboard does indeed have aftertouch. It’s ‘channel’ aftertouch, but has a decent feel in my opinion. The pads support polyphonic aftertouch.
- the step sequencer is a lot more capable than most folks understand. Each song (session in SL MKIII speak) supports 8 parts. Each part can have 8 sequences.. So each saved song/session - can have 64 patterns. I am still working my way through this . . but suspect, once I get comfortable moving around - it will be easier. There are plenty of vids showing different folk moving around with the sequencer - in it’s different modes.
- setting up MIDI CC mapping for gear, is done through a SL MKIII “template”. It would be nice if there was an automap feature (it’s possible there is- and I’ve missed it). It would be even nicer - if it was possible to put the controller into ‘learn’ mode, and map that way. There isn’t. So - setting up hardware mapping is manual. That said - here are a couple of important things about that. 1) The SL MKIII comes with a bunch of pre-configured mappings. For me - that meant, I didn’t have to map an OB-6, Peak, or BigSky reverb. I DID have to map a JD-XA and FA-06, and some soft synths. It took me, about a 1/2 hour to get my JD-XA mapped. 2) Each of the templates can contain a custom configuration for 16 encoders, 16 buttons, 8 faders, 16 pressure sensitive pads, the mod wheel and three hardware pedals. That’s ~ 60 mappable controls per hardware or software instrument. Personally - I don’t map every possible control to a controller-synth - so I haven’t come close to hitting the ceiling with this as a limitation. Neither for mapping for a live rig (I’ve been using an Axiom Pro and an Arturia ‘The Laboratory’ for a few years. For me - for live play - there are typically about 10 things (aside from transport control) that I want to use live. For the home studio.. I definitely want to map more… but even for the OB-6.. (my synth I want the most mapped control of)… that amounts to about 30 things I want mapped. Still not close to the ~60. So I doubt I’ll ever see the limitation. Maybe others though - have more elaborate needs. On the OB... I have already been used to reaching for it's controls, when there is an odd setting I need to set. If I find I am using it a bunch -- I'll map it. Again though - for me that is about 30 things. Way less than 60.
- Routing of my gear, has been dead easy. I am still working my way through the capabilities, and have only created a handful of templates - but it is fricken great. This is what I wanted the controller for. Since gear is pre-mapped to ‘templates’ - setting up ‘sessions’ or songs - is quick and easy. I created a template session, that has my synths (hardware and software) pre-connected/routed. They are already mapped via the templates, so it’s not necessary to prepare a session this way - but it is nice to have the DIN/Channel pre-defined. To setup a song/sequence - I copy a template. save as a new song - then dink around with setting up layers, splits, and patch selection. You can store 64 of these on the device - and can offload groups - if you run out. On top of these settings - you define the sequences. You can map sessions to the controller - and it's an instant cutover, so it's possible to utilize multiple sessions for a single song.
Again - I am still working my way through the manual, and learning stuff. There are a couple of fantastic tutorials out there, which went through the setup stuff I needed. I am now trying to figure out how to use my iConnectMIDI4+ for more than just a way of integrating iOS (iPad) synths. ( the SL MKIII does all the mapping I was getting in the iCM4+, a LOT easier, and more conveniently) so there is huge overlap. iConnectivity is really going to have to step up their game. Anyway - hopefully this wasn’t too inaccurate. Your mileage may vary, yadda yadda .. . .