Maybe just create an init patch, and use ableton presets instead?
After losing all my configs to the recent update, Im starting to think the hack is too much trouble to maintain versus actually making music
![Very Happy :D](./images/smilies/icon_biggrin.gif)
Good idea, except - every time I change presets I get another 3 - 9 .cfg files.peterswimm wrote:You could always map one preset, and then copy them into the new config for each updated instance.
Maybe just create an init patch, and use ableton presets instead?
After losing all my configs to the recent update, Im starting to think the hack is too much trouble to maintain versus actually making music.
Amen.cskracer wrote: Live should include a tool that does the following:
1. Allows the user to select a VST.
2. Reads all of the controls that the VST exposes - including those past the 128 limit currently in live.
3. Allows the user to select which controls they'd like to have mapped for that synth and in what order from the list of VST controls.
4. Allows the user to setup named banks like Ubermap can.
5. Allows the user to rename what each of the controls is called when displayed on Push.
6. Once that configuration has been completed, have Live automatically scan through all of the presets in the VST and create an instrument rack for each preset using the control mapping specified by the user.
I don't think they are as people complain about them too, but chances are that they might be better at this. Worth checking out, though getting one means you have to lug it around with you. A Push is very portable and versatile.cskracer wrote: I'm at the point where I'm considering purchasing one of NI's S series keyboards as it appears as though their automapping features are much more user friendly.
Yup. I haven't tried Ubermap since Tom got a Push 2 (I'm on the original). Spent a lot of time setting it up a few years back. It's great that Tom created this project and it has been a godsend and likely is for a lot of people that are motivated to get into this. Not all are unfortunately.cskracer wrote:
Anyway back to saving my instrument racks with the controls setup via PrEditor....
So true.cskracer wrote:It's a massive disappointment to me that we have to try and use third party tools to do what should be built into Live. It's 2016 for god's sake not 1980.
Live should include a tool that does the following:
1. Allows the user to select a VST.
2. Reads all of the controls that the VST exposes - including those past the 128 limit currently in live.
3. Allows the user to select which controls they'd like to have mapped for that synth and in what order from the list of VST controls.
4. Allows the user to setup named banks like Ubermap can.
5. Allows the user to rename what each of the controls is called when displayed on Push.
6. Once that configuration has been completed, have Live automatically scan through all of the presets in the VST and create an instrument rack for each preset using the control mapping specified by the user.
Nice initiative!cskracer wrote:I've put up a suggestion on centrecode for those of you on the beta forum. I've asked for them to provide auto instrument racking as that's the part that takes the time.
If you're keen please upvote it so we get some traction.
https://ableton.centercode.com/project/ ... 4faf86c4d1
cskracer wrote:Automatic Instrument Racking of 3rd Party VSTs