Same! When I get that urge to sell this thing I re-watch Loopop's video on it and I remember that I only know and use like 20% of what this thing is capable of.
@@chiefbucknell thanks my friend! A lot of what I talked about here came from our conversations 🤣. KeyStep will probably be a forever device for me I think.
I was always curious what the user scripts do and how to activate them. This was a good example of that. I hate the controller mapping that you get with the regular scripts, they are so limiting and do things that keep you away from intuitive work.
Same! I never messed with scripts because I thought it would be too complicated or cause issues in the daw. Super simple and it just works. It’s got me wanting to go buy cheap midi controllers to make them do specific things. Nice way to not spend a lot of money on the latest greatest.
Thanks! I picked ip a Keystep 37 open box special... as a cheap way to get a slightly better portable controller. It's both an amazing and frustrating little device. Frustrating in it's lack of DAW integration support from Arturia. After getting more into Ableton's capabilities I'm finding the limits are not as harmful as my first impressions left me thinking. The 37's limitations actually forcef me to better utilize both the software and equipment!
I really wish there was a way to use the transport controls on the keystep to control Ableton. I love that the key step has a sequencer and arp, but I'd be glad if I had an option to bypass that and use those controls for transport. I imagine you could go into the remote script and modify, but that feels like extra work!
For some reason I only got the first knob to work with this instant mapping. I can still assign MIDI mapping manually for the remaining 3 knobs though, no idea what’s causing this..
Which version of Ableton are you using? I think one of the other things I read is that when you make that folder the name has to match exactly how it is identified in Ableton. Not sure if that will fix it though!
![The Wall Song ร้องข้ามกำแพง | EP.213 | กรีน อัษฎาพร | 3 ต.ค. 67 [1/5]](http://i.ytimg.com/vi/3KrlLbCsadI/mqdefault.jpg)
![[Live] : ONE FIGHT NIGHT 25 วันนี้!! "อเล็กซิส vs รีเกียน"](http://i.ytimg.com/vi/suVr9a6BM2g/mqdefault.jpg)
Great tips for the Keystep 37. A device I almost sold because I was focused on the keys vs what is under the hood.
Same! When I get that urge to sell this thing I re-watch Loopop's video on it and I remember that I only know and use like 20% of what this thing is capable of.
Reminds me how a video from Mylar Melodies about the OG KeyStep’s sequencer convinced me to pick up one of those. Great video!
@@chiefbucknell thanks my friend! A lot of what I talked about here came from our conversations 🤣. KeyStep will probably be a forever device for me I think.
I was always curious what the user scripts do and how to activate them. This was a good example of that. I hate the controller mapping that you get with the regular scripts, they are so limiting and do things that keep you away from intuitive work.
Same! I never messed with scripts because I thought it would be too complicated or cause issues in the daw. Super simple and it just works. It’s got me wanting to go buy cheap midi controllers to make them do specific things. Nice way to not spend a lot of money on the latest greatest.
Thanks!
I picked ip a Keystep 37 open box special... as a cheap way to get a slightly better portable controller.
It's both an amazing and frustrating little device.
Frustrating in it's lack of DAW integration support from Arturia.
After getting more into Ableton's capabilities I'm finding the limits are not as harmful as my first impressions left me thinking. The 37's limitations actually forcef me to better utilize both the software and equipment!
I really wish there was a way to use the transport controls on the keystep to control Ableton. I love that the key step has a sequencer and arp, but I'd be glad if I had an option to bypass that and use those controls for transport. I imagine you could go into the remote script and modify, but that feels like extra work!
For some reason I only got the first knob to work with this instant mapping. I can still assign MIDI mapping manually for the remaining 3 knobs though, no idea what’s causing this..
Which version of Ableton are you using? I think one of the other things I read is that when you make that folder the name has to match exactly how it is identified in Ableton. Not sure if that will fix it though!