TheOtherSupport@KMI wrote:Yes, it can be done.
There's two options - you can do this all in the editor, by using 'dummy' modlines, that only serve to light the LED, and using the 'X Key pressed' to turn off LEDs based on interacting with other keys.
Another option is doing some M4L programming to observe the state of the looper and send LED info from Live.
TheOtherSupport@KMI wrote:There isn't a 'guide' per say, but all of the info should be in the manual: http://files.keithmcmillen.com/downloads/softstep/SoftStep_Manual_v2.01.pdf.
If you run into trouble, let me know. I'd be happy to clear things up for you.
emmett@KMI wrote:In order to program the LEDs, go to the Advanced SoftStep Editor and click on a pad.
Click on LED Settings to see the hidden right side of the window.
On the "play" pad, have a modline set to turn turn both LEDs off with a source of "other key pressed". Also have another modline so that when the "play" pad is pressed it's green LED is set to true. Foot on should be sufficient. (1)
Do the same for the record pad but set the LED to to red instead of green.
Do the same for overdub although when you hit this key it will turn the play LED off. (Sorry about that)
Do the same with stop but use blink true instead of true for turning on the LED.
TheOtherSupport@KMI wrote:Here's an example for the play button. In this scenario button 1 is play, button 2 is record, button 3 is stop, button 4 would be overdub.
I have a foot on source triggering a toggle (this is to make sure when you hit play, it always lights the LED and plays the Looper). If stop or record is triggered (keys 2 and 3) then the play LED will turn off. Overdub (Button 4) doesn't affect play because they can occur simultaneously.
For the "X key pressed" modlines, you can set the output to None, because you aren't sending any MIDI data, just controlling LEDs.
Hopefully this gives you an idea of how to setup the other keys.
Users browsing this forum: No registered users and 1 guest