johnnytravels wrote:The fact alone that you have to load keygroups into a project and they will clutter everything even if you’re not assigning them to tracks will make you hate using keygroups so fast that it’s probably not worth the hassle to convert anything to MPC format (unless of course these are your signature sounds that you know in and out and won’t have to project-manage if you load them).
If you create an instance of Fabric and don't assign that plugin program to a track, it's sat there in your project taking up memory. So in either situation you have to conduct the same project management workflow of deleting unused programs. The only difference is that deleted plugins effectively 'auto-purge'.
And if you are loading many keygroups into ram just to preview them the quick workflow is to load one, try it out and if you don't like it just hit UNDO to simultaneously 'un-load' it and effectively auto purge the samples (i.e. you undo takes you back to the exact state your MPC was in before loading that program).
I just don't get the hate some people suddenly have for keygroups. They have no 'per instance' restriction, can consist of any sound you wish, can be made by you to your own exact requirements and when made properly take up far less memory than most of Akai's plugins. Having to occasionally perform some quick RAM management seems like a very minor, run of the mill thing to do in a sampler and shouldn't be seen as a tortuous ordeal.
What next, a campaign against sample based drum kits and chops? The MPC is a sampler not just a plugin host, although I'm sure Akai absolutely love it when people come to the conclusion the only sounds you can now use in your MPC are the ones found inside their plugins (available exclusively from Akai's store).
If people are worried about ram clutter, just use external MIDI synths (the MPC is, and always has been, a powerful MIDI sequencer), although given some of the MIDI bugs ATM I wonder how long it will be before MIDI support is too gimped to be useful.
