There seems to be no way to audition a single step on Push. That is strange because, in Elektron devices, it is a major fine-tuning method that could greatly enhance the workflow of Push.
It seems to be almost there, but then not quite. When you hold a step in a drum rack, you have the ability to tweak the “trig locks” of that step. However, there is no button to listen to the selected step.
If you hit play, you will hear your changes, but only when that specific step is played—which can be tedious in a 64-step sequence. Additionally, you will hear the entire set rather than the step in isolation.
A functional pre-listen switch in the user preferences of Push, similar to what you have in Ableton, would be a great addition.
P.S.: When pre-listening to a note in the piano roll in Ableton, the envelopes’ states are ignored! So, there is no true step preview there either…
Just released v1.0.0 of MIDIseq, a 64 step sequencer with proper parameter locks, automation, trig locks (including microtiming and modulated ratchets)
All modulations are implemented using the modulation feature in Ableton Live so you still have full control over the original parameter.
Currently there is bank support for Ableton Push and we’re looking to expand support further.
Yeah the load time is definitely not the fastest unfortunately. This is purely because of the scope of the functionality and the necessary steps to initialise 30,000+ parameters on load within the Ableton ecosystem.
We spent a fair chunk of time optimising runtime performance but the load time was always the same. Long story short, we’re not sure if Ableton / Max4Live is able to handle a large quantity of parameters in a timely manner on load. The only way to cut it back was by stripping out functionality which we didn’t want to do.
It’s definitely something that is on our radar but haven’t found a solution for yet.
yea its a great sequencer (elektron vibes) but it’s definitely a bit heavy on resources.
I think if possible it would be good to have the sequencer open as just 1 single track (rather than 8) - to keep it light on resources. then have a (+) button to add extra tracks as you need.
Yeah it’s a good idea, we explored an avenue with that train of thought. Ultimately there was a workflow trade off as when enabling an inactive channel there were sync issues so we didn’t go with it for v1.0.0.
Once a couple things are checked off we are going to explore re-writing a lot of the code from the ground up with optimization in mind to hopefully enjoy the best of both worlds. But it definitely won’t be a small task considering how long it took us to get to this point. So please bear with us