Keygroup bugs and lack of undo

I was working on a keygroup with four layers of samples and started to get close to the finish line when I was going to replace one of the layers by going to the Browser screen. I'm not sure exactly what happened but i pressed Load on a sample and suddenly the entire keygroup had been replaced with that one sample.

I panicked and press Unfo, and after a few presses, some of the original layering came back, but not how I had set it up. All the work to find loop points on the samples were gone and it was all reset to play once samples rather than loops.

Is this a known bug? I guess I'll have to remember to save much more often.

BTW, this is why I'd never ever use the autosave feature because if this happened and it then autosaved, it could overwrite hours of hard work without any way of getting back.

So in the browser you pressed a pad that represented a keygroup (e.g. pad A4 = keygroup 4) and then selected a sample and pressed LOAD? If so, this feature is designed to effectively wipe the selected pad/keygroup and assign the loaded sample to layer 1 of that pad/keygroup. It's not possible to target a specific layer this way (from memory, I don't think you can target a specific keygroup layer in the browser, this only works for DRUM programs, by 'shift' dragging in the sample assign screen).

Either way it sounds like you experienced a bug, as even if 'ALL' keygroups was selected in program edit, this should be ignored in the browser screen so the selected (green) keygroup is the only one to receive the loaded sample.

In my experience undo is unpredictable, I now rarely use it unless I absolutely have nothing to left to lose, and instead tend to save my work after every major action.

I would also point out the loop points are another buggy area when it comes to saving. Basically the MPC only re-saves samples (as part of a complete project save) if it detects there has been a change to that sample, but currently if you change a loop point (or even just change the loop type) and then hit 'save', the MPC doesn't always re-save the sample. The current workaround is to either manually re-save that one sample (from SAMPLE EDIT go to MAIN > program row pencil > SAVE CURRENT SAMPLE), or alternatively re-save the entire project under a different name.

Personally I prefer to build keygroup programs directly in the MPC Software, it's much quicker and has more useful features for that kind of work, especially when combined with the hardware for controlling some parameter changes. The hardware UI is great for actual music making workflows, not so great for more technical, fiddly stuff. Unfortunately bugs you discover in the hardware UI are usually also present in the MPC Software.

MPC-Tutor wrote:So in the browser you pressed a pad that represented a keygroup (e.g. pad A4 = keygroup 4) and then selected a sample and pressed LOAD? If so, this feature is designed to effectively wipe the selected pad/keygroup and assign the loaded sample to layer 1 of that pad/keygroup. It's not possible to target a specific layer this way (from memory, I don't think you can target a specific keygroup layer in the browser, this only works for DRUM programs, by 'shift' dragging in the sample assign screen).

Either way it sounds like you experienced a bug, as even if 'ALL' keygroups was selected in program edit, this should be ignored in the browser screen so the selected (green) keygroup is the only one to receive the loaded sample.

In my experience undo is unpredictable, I now rarely use it unless I absolutely have nothing to left to lose, and instead tend to save my work after every major action.

I would also point out the loop points are another buggy area when it comes to saving. Basically the MPC only re-saves samples (as part of a complete project save) if it detects there has been a change to that sample, but currently if you change a loop point (or even just change the loop type) and then hit 'save', the MPC doesn't always re-save the sample. The current workaround is to either manually re-save that one sample (from SAMPLE EDIT go to MAIN > program row pencil > SAVE CURRENT SAMPLE), or alternatively re-save the entire project under a different name.

Personally I prefer to build keygroup programs directly in the MPC Software, it's much quicker and has more useful features for that kind of work, especially when combined with the hardware for controlling some parameter changes. The hardware UI is great for actual music making workflows, not so great for more technical, fiddly stuff. Unfortunately bugs you discover in the hardware UI are usually also present in the MPC Software.

Thanks, very helpful! You could be right, I wasn't trying to assign a layer that way, but maybe I accidentally pressed a pad while browsing. Indeed, the Undo seems erratic at times. I do tend to save quite often but I got carried away in the creative process.