MIDI program change is certainly the fastest, but you cannot see where and what you're navigating.rod_zero wrote:I didn't like loading racked presets from Push it is slow, as it has to load the plug in again.
To me the best solution ofr this is using the MIDI program change functionality in plug ins, this is done placing a M4L device before the VST which can send MIDI program change messages. Works quite well and is much more faster.
I'm browsing through my own presets now on Push via racks, and as long as you're browsing within the same VST, the changeover from one to the next is literally instant. For me at least. I've got them all neatly placed in my own folders as well (Arps; Arps - experimental; Plucked; SEQ - melody; etc) , so I can see exactly where I'm going, and get there quickly, all from Push. I also like that you can just hit the amber button below the relevant area on the screen to load the next preset/rack
My PC is a 6+ year-old geriatric piece of crap, slowly failing in most dept - HD is extremely sluggish, first-gen i7, half-broken dual-GPU, and warts. Windows 7.
EDIT: btw, if anyone wants my take on a Push Hive and Bazille configurationmapping, I'd be happy to share. Both need tweaking perhaps, but I find the Hive one very enjoyable to use.
One thing to consider before anyone starts saving racks for Push if you also want a sensible parameter layout for each - configure your ideal parameter layout as the template first, otherwise you'll have to save all those racks again if you make any changes. There is perhaps a quicker way of implementing any changes to all racks after the fact, but I'm not aware of how.
