Well worth the time just to create a default template for a VST that has all your controls mapped ready to go. Once you have a patch for a project you can then map to macro. You can still access all configured controls easily with Push but you just have to "step" into the rack instead of having them right on hand. The easiest thing to do is simply MIDI learn the controls you want and leave them as simply configured controls, not macros. This can cause issues when you save a project or touch a macro.
If you map MIDI controls to the 8 macro knobs then the knobs will not update to a newly loaded patch. So I'm sticking to just racking with no macros - I can assign them when needed. It is a confirmed bug, but I don't think very high on their priority list.
The downside with Zebra, and I don't know if it's JUST Zebra, is that if you macro map parameters, and load one preset after the other (the racks, not in Zebra itself), they can sometimes completely ruin the newly loaded patch. Just annoying to have to dive so deep to access your own stuff, but once you've navigated to this area it's also practically instantaneous to load presets as racks one after the other. You can then browse your racked presets from Push via Places - User Library - Presets - Instruments.
(3) Rack up the presets yourself one by one manually, or do it via a keyboard/mouse input logger, and loop a batch script overnight to save the presets. rd-control as it offers other useful little MIDI features too. Works great, is instantaneous, although you can't see the name of the currently loaded preset on Push. (2) Place the VST's presets in its MIDI program change folder, and use any of the free Max4Live devices to scroll through either presets or banks of presets. I don't have any NI stuff myself, but it does look pretty impressive. vst-bridge has extensive Native Instrument preset browsing/dial setups for Push.
0 kommentar(er)
