That changed a few updates ago. You can load a sample to one drum pad, leave the drum rack and come back and it’ll remember the folder you’re working out of and then you can load another sample to another pad. You don’t have to navigate your way back to the folder you were working in from the top level of the browser anymore. That was annoying.
However, I may not be understanding your question though.
Ok, question because I’m finally going to attempt to use controller mode: the Push manual specifies to use the supplied cable, is there a reason I couldn’t just use a different, longer cable? It simply doesn’t reach my USB-C port (I use a desktop computer and can’t really move it).
With some USB-C cables, mine won’t power on without also using the power adapter, but with the standalone that shouldn’t matter, as it can power itself in controller mode too.
You can edit - delete instruments, FX, add new ones- one that is already in the library, save it and then change the name.
Or, the best alternative, is to create a “clean” one with one instrument in ableton and then use it as a starting point to all the racks you want to create in SA.
Elegant? No , but it does allow to create chains of midi FX, instruments, audio FX and use them in subsequent projects. No Macro or midi mapping in SA, yet
You can also “create” program changes in standalone. Im sure somebody else uses a similar strategy.
“just” create in Ableton a empty midi channel on your template with 128 clips, and add the corresponding Program Change number to that clip. And then you just choose the one you want to use and put it in the channel of your external instrument. It works, but clumsy AF
Nope. But as I said, if somebody wants to save wants to make a rack in standalone it’s possible, with some setup in Ableton. That might be valuable for some . But I agree that macros and also midi mapping are very important, when it comes to Instrument Racks
Someone asked about using the ERM Multiclock with Push Standalone on Reddit, and I just so happen to have been experimenting with this technique using my Innerclock Sync-Gen Pro II yesterday, so I’m posting here as well to see if anyone has any tips/experiences using this type of clocking:
Still testing, but it seems to work steadily, albeit with some latency (~9ms late on recorded drum machine audio) with the method I describe below. Based on some Googling, it seems that the latency may be caused by Push itself not properly compensating for latency, but I am not sure.
How I set this up:
I am using a sample of the Innerclock VST pulse in Simpler One-Shot mode to trigger the Innerclock. A Midi clip with 24 hits per quarter note needs to be created in order to trigger the clock device. You can find examples of the pulse and midi clip on the ERM website.
On the track with the Simpler, I have an External Audio Effect device set to send out the audio to the Innerclock via ADAT on channels 15/16. This method works via sending to outputs 3/4 on the Push as well in my testing, but I wanted to use that output for headphones which is why I switched to ADAT to send out the pulse.
Also, an external instrument is set up to monitor the drum machine being triggered (Analog Rytm MK1), and I have an audio track with monitoring set of OFF set up to record this external instrument track. Recording to this track is how I tested the latency.
As of now, you still need to set up the external audio effect on the computer btw, then bring it over to the Push.
Overall, this solution provides a seemingly much steadier clock than the standard midi sync method via the Push’s midi outputs, but I would REALLY like to get rid of the 9ms of latency I am getting.
Yep, that solution would get the recorded audio better in-sync, but ultimately that functionality seems to be intended to solve issues with lags between midi-triggering of external synths FROM Ableton and the sound generation on the external synths themselves. This seems (to me) to be an issue with the Delay Compensation itself on the Push (since this problem does not exist using the same Innerclock method from my computer/soundcard). Also, the Rytm doesn’t have this same problem when I am triggering notes on it from Push.
So setting the hardware latency to be 9ms on the external instrument would actually further compound the disconnect between playing live on the Rytm and playing live on the Push.