MPC 3 loads a default kit on boot-up. How can I prevent that

Manu B wrote:Tout à fait, et c'est tellement plus logique

I guess it depends on your mindset. I know I'm a old head after using an MPC for 20+ years, but there are times where the new workflow isn't so seamless.

For example, you lay down a track but you want to see how these MIDI notes sound with different sounds/programs. I laid it with a piano, but maybe it sounds better with strings or a lead, or whatever. I would just go down to PGM and cycle through my sounds to experiment with it.

I can technically still experiment with different sounds, except this time I need to go back into the browser each time and load a new PGM. Not huge but it is more time and more friction. Like I said, technically speaking it works but that workflow adds more friction into the process.

I don't know if somebody has a workaround for that. I know Akai is doing their best to appeal to everybody and give everything to everyone, but the fundamental shift of having the sound "database" to the tracks sometimes adds friction.

maybe not helpful, and you probably already know this, but you can send midi from one track to another. more friction though.

Yea still not as seamless, but I appreciate the tip.