Hey all, quick Q: when I go into Browse mode on my Push 2 (Live 9.7.1), I can only see the Default preset under Aalto, no others are available. This used to work, I gather. Is there something I can do to restore this?
thanks!
- wells
Hi Wells, I've never had the chance to try Push so I'm guessing a bit here.
At one point I moved the location for presets from ~/Library/Plug-Ins/Audio/Presets/Aalto to ~/Music/Madrona Labs/Aalto. It's possible Push / Live are looking for presets in this old location. You could try moving some there to check.
You could also try the VST instead of the AU.
Do you know if Live is trying to load presets in .aupreset format? That's a custom AU thing I moved away from.
I'd like to make it work with Push, it's a cool piece of hardware, so I will look into this.
Ableton Push supports browsing in the same way as Ableton Live generally does... i.e. what you can view in Lives browser is available in Push. (so doesn't need special testing)
basically there are two (actually 3) ways ;)
two described here;
https://help.ableton.com/hc/en-us/articles/209776485-Browsing-plug-in-presets-with-Push
a) AU - save your presets as aupresets... this works for everthing (well thats is an AU :))
b) VST - save as PC banks (ML doesnt support this)
c) put plugin in a instrument rack, and then save the rack.
I use (a) the most, but of course this wont work if your on a PC (only Mac), (c) is ok but a bit cumbersome, but has the advantage that you can assign some macros whilst you are there :)
In some ways I quite like saving these presets separate outside the ML preset system, as it means I have only my presets on the push :)
the main 'pain' is if you use other DAWs (that dont support AUs) then you cannot get to these saved presets...
to get around this I save in both .aupreset and in the ML browser, which of course means there can be 'discrepancies'
its a pain, plug in developers dont like the au/fxp format as they are limiting, and of course means you need to dupe au and fxp formats (and others if you support aax etc), but its not ideal for users either, as DAWs can only use these standards... they know nothing of internal presets. (though bitwig, seem to know something about u-he's preset)
Native instruments are trying to get around this with NKS, and a few developers have jump on board... but Im not sure they are making this technology available to DAWs, or if its just for their controllers.
anyway, its only really a pain, if your using multiple daws, otherwise there is a way to get these things to work :)
Thanks much for the info! I hope this helps you out, Wells.
thanks techno bear!