cc Q

hello,

has somebody done Quantizing on (midi) CC?

i'm dithering my cc info, but i want them to follow the beat (or not-)

would be great if i could quant. my improper input

some rather unusual behavior : if i hit the TC in step edit, the values in the seq. are not send anymore to the (external) synt - it kinda hangs
TC apply has no effect, but if i return to the seq/close the window - everything is as before - so no change

=>still 'faulty' knob turning from my side

should anybody knows or wants to try, please feedback.

c'mon b-boys (&bgirls)

nobody has tried this before?

confirm or deny please

j

so that i understand: you want to quantize the CC info you are recording into the 4k? and the problem is that you can't get your knob-twiddling timed correctly?

i would be surprised if quantizing continuous control data was a 4k feature but i do not know for sure. in the meantime you could always try slowing the tempo, recording your cc input and then restoring to the original tempo.

you are partly assuming correctly

i'm just twidling my knobs (on the synths) and recording them into the MPC

if i slow down the T, the amount of recorded info will be greater !

I go into step edit (list), select all / one MIDI CC info in the seq and hit the TC button

when you do this with note info, the recorded notes jump onto the TC value(s)

when I do this with CC info, nothing happens - even first CC value is transmitted to synths and then stops - when i return to main everything is as normal - but not Quantised

the goal of this TC is to dither my CC info and/or to be right on the beat (or not)

so there is no way to Quantise MIDI cc info?

have a nice day,

j

The controller info is more like a reference in time, if you were to quantize that it would have some bad aspects on the overall timing and processing of data.

Think of it more like a grid for things to happen instead of things happening.
Unlike a note it a function that has to be acted on and responded to.
Based on the processing power of the MP and the required stability it's trying to achieve throwing controller info around in a quantized manner could give all sorts of lags, lock ups and head aches.

ok, thx for the reply

although i find it rather 'unprofessional' - in the sense that events are events - notes, cc info, Q link controllers...

they should all be treated equal - in terms of PP, event handling and (MIDI) timings

are you really sure those engi's conceived/programmed sort of a priority system to deal with this kind of info?

cheers,

jay