Velocity

The midi velocity on main screen doesn't seem to work? was wondering if anyone encountered this. Do I have to have PC on seq or off? Can't figure it out.

When recording MIDI info by the way.

i have not tried it with 4.55 yet, but it used to work.

it'll only affect pre-recorded midi data.

Mr modnaR wrote:it'll only affect pre-recorded midi data.

yup. this always confused me at first, and i don't often use track velocity because it doesn't apply to individual pads when struck by themselves. instead, i use the global param edit to turn down the pgm's level with WHOLE.

Mr modnaR wrote:it'll only affect pre-recorded midi data.

Can you explain this alil more please?

grinchmob wrote:

Mr modnaR wrote:it'll only affect pre-recorded midi data.

Can you explain this alil more please?

Yeah, do you mean pre-recorded as in it's a MIDI file or pre-recorded as in it will change the velocity of the MIDI data, but only if it is already recorded into the sequence (i.e. not playing it real-time)?

Cause I've had the same problem where recording a MIDI part, the velocity % setting did absolutely nothing. I had to edit the levels in the sound module (on my PC) to adjust it.

the velocity setting only has an effect on a track that's recorded, not played live. so, if you just hit the pads and adjust velocity on the main screen, nothing happens. but if you record a track, then play it back, it'll affect the note data coming from the mpc's sequencer. this is a non-destructive form of editing too, so you can always take the value back to 100% to get what you originally recorded.

also bear in mind that it acts like 'note on' qlink data, in that it'll only change the velocity of the note as it hits, not halfway through. this works fine for highly detailed drum and melody tracks, not so great for 8-bar loops (you know who you are, you lazy bastards), as you have to wait for the loop trigger note to come round again for the velocity setting to have an effect.

hope this helps.