MIDI CC Control of Step Velocity?

I'm not an MPC user (yet) so please forgive me if I'm not using the right terminology... I was wondering if it is possible to assign MIDI CCs to control sequencer steps on any of the current MPCs? To be more specific, I'd like to be able to control the velocity for each step (16 steps) from the faders (16 faders) on a pair of Behringer BCF2000s so that each fader corresponds to the velocity of a step in the MPC. Does anyone know if this is possible?

morbank wrote:I'm not an MPC user (yet) so please forgive me if I'm not using the right terminology... I was wondering if it is possible to assign MIDI CCs to control sequencer steps on any of the current MPCs? To be more specific, I'd like to be able to control the velocity for each step (16 steps) from the faders (16 faders) on a pair of Behringer BCF2000s so that each fader corresponds to the velocity of a step in the MPC. Does anyone know if this is possible?

not sure about controlling externally but in step sequencer the MPC Qlink control the velocity for each step. When you press the Qlink button it scroll by 4 step so you can adjust the 16 step of your bar.

Hmm, maybe it’s possible to control the QLink knobs via MIDI then?

morbank wrote:I'm not an MPC user (yet) so please forgive me if I'm not using the right terminology... I was wondering if it is possible to assign MIDI CCs to control sequencer steps on any of the current MPCs? To be more specific, I'd like to be able to control the velocity for each step (16 steps) from the faders (16 faders) on a pair of Behringer BCF2000s so that each fader corresponds to the velocity of a step in the MPC. Does anyone know if this is possible?

the MIDI standard shows that Velocity is part of the Note ON/OFF information:
https://www.midi.org/specifications-old ... di-message

OEMs of Synth are usually listing detailed MIDI signals and the appropriate parameters of their machines.
AKAI is ignoring this. To me this is a "Band in the Box" behaviour - users are NOT interested how to tweak sounds... bad behaviour for a company who calls themselves "Professionals".....

EDIT: Interesting off-topic detail: an improvement of the MIDI standard is under discussion - called MIDI 2.0 (https://www.midi.org/articles-old/detai ... y-exchange), as the MIDI standard we are currently using is still 1.0 (since 1984). Part of it is "Jitter Timestamps" which should work with MIDI 1.0 and 2.0, as it is a new protocol and not an extension to an existing protocol.

morbank wrote:Hmm, maybe it’s possible to control the QLink knobs via MIDI then?

Unfortunately, and contrary to the MPC software, we can't currently MIDI remote the 16 Q-links on the MPC hardware.

the MPC is not a step sequencer
-despite all/most sequencers on the market today are step sequencers
so, you better assign the MIDI cc to vol (nr 7) - which has the same effect
because of the improved resolution (contrary to 16/32/64 steps of a steppin seq) of the MPC you can add fine nuances of that MiDI cc (nr 7 or whatever)

there's a stepsequencer inside the MPC (on each & every track!) which let you input/control notes and controller data in a steppin' way
with the X you can control (whatever control, be that vel, or note, or CC ) 16 steps of your step sequence at once

tiger001 wrote:there's a stepsequencer inside the MPC (on each & every track!) which let you input/control notes and controller data in a steppin' way
with the X you can control (whatever control, be that vel, or note, or CC ) 16 steps of your step sequence at once

Tiger, are you able to point me to where this is covered in the manual?

p 155 and on in the latest user guide 2.7.2