By nickmz
Sat Jul 09, 2022 2:31 pm
MPC ONE 2.11.2
I bought MPC ONE to try finger-drumming and faced a very annoying issue. For example I load factory kit "Acoustic-Kit-Ac Fat.xpm" into an empty project and start my practice with the pads. Unfortunately sometimes when I play a dense hat or snare 1/8 pattern I clearly hear that some of the notes disappear. Not even they disappear but they abruptly stop the previous hat sound and the whole piece sounds awful. This is extremely annoying and frustrating.
I recorded my playing and found that in this cases MPC detects a very short and quiet note. So I tried to change the sensitivity/threshold pad settings and try to play harder. But it didn't help at all, the issue stops only if I hit the pad extremely hard which makes the playing uncomfortable.
I tried to find some setting or MIDI filter which allows to set minimum value for velocity and/or length of a note, but didn't find anything yet.
Then I thought my pads are just broken, as I bought MPC used on eBay.
But lately I decided to change the program settings for "Acoustic-Kit-Ac Fat.xpm". There are two ways to make muting for the hats or the snares:
- you can specify a "mute group" for a pad
- or you can explicitly set up to 4 "mute targets" pads for a pad
By default "Acoustic-Kit-Ac Fat.xpm" uses the simplest way with a "mute group" and uses "mono" polyphony for hi-hats (A03, A04, A08). For snares there is not mute group but polyphony is "mono" as well.
So I changes the settings:
- set polyphony to "2" instead of "mono" for all pads (for most sounds like kicks, snares, rides you can't hear the difference)
- for hi-hats I set the "mute group" setting to "off" and set the explicit mutual "mute target" for all (A03, A04, A08), to stop one hi-hat sound by another hi-hat sounds (looks like this specific change is not important here)
The issue has gone! Now I can play as softly as I want, nothing cuts off the sound, I don't hear any glitches. Every hit on the pads is detected in a way as I would expect.
So what was that? Does anyone else experience the same? I just have only a week of experience and only with 2.11.2 firmware.
I bought MPC ONE to try finger-drumming and faced a very annoying issue. For example I load factory kit "Acoustic-Kit-Ac Fat.xpm" into an empty project and start my practice with the pads. Unfortunately sometimes when I play a dense hat or snare 1/8 pattern I clearly hear that some of the notes disappear. Not even they disappear but they abruptly stop the previous hat sound and the whole piece sounds awful. This is extremely annoying and frustrating.
I recorded my playing and found that in this cases MPC detects a very short and quiet note. So I tried to change the sensitivity/threshold pad settings and try to play harder. But it didn't help at all, the issue stops only if I hit the pad extremely hard which makes the playing uncomfortable.
I tried to find some setting or MIDI filter which allows to set minimum value for velocity and/or length of a note, but didn't find anything yet.
Then I thought my pads are just broken, as I bought MPC used on eBay.
But lately I decided to change the program settings for "Acoustic-Kit-Ac Fat.xpm". There are two ways to make muting for the hats or the snares:
- you can specify a "mute group" for a pad
- or you can explicitly set up to 4 "mute targets" pads for a pad
By default "Acoustic-Kit-Ac Fat.xpm" uses the simplest way with a "mute group" and uses "mono" polyphony for hi-hats (A03, A04, A08). For snares there is not mute group but polyphony is "mono" as well.
So I changes the settings:
- set polyphony to "2" instead of "mono" for all pads (for most sounds like kicks, snares, rides you can't hear the difference)
- for hi-hats I set the "mute group" setting to "off" and set the explicit mutual "mute target" for all (A03, A04, A08), to stop one hi-hat sound by another hi-hat sounds (looks like this specific change is not important here)
The issue has gone! Now I can play as softly as I want, nothing cuts off the sound, I don't hear any glitches. Every hit on the pads is detected in a way as I would expect.
So what was that? Does anyone else experience the same? I just have only a week of experience and only with 2.11.2 firmware.
Last edited by nickmz on Sat Jul 09, 2022 3:14 pm, edited 2 times in total.




