I wish the C2D ... (SW update?)

[elseif]

• sent keyboard velocity messages with the Keyboard Trig Mode set to High
• placed the reverberation module after the rotary simulation module in the effects chain
• stored the synth bass pluck setting with a preset

[Quai34]

Yes, why not, if it comes as well with the same update for the C2..Like they did with the last C2D update...

[jazzspire]

I third the motion.

It would be interesting to hear from a product manager as to whether it's possible to write firmware to place the reverberation module after the rotary simulation module in the effects chain.

I'm also interested in keyboard velocity messages feature as well.

[elseif]

• sent keyboard velocity messages with the Keyboard Trig Mode set to High

I just realized this is probably not possible. In order to determine a key's velocity, the time must be measured between the state change of its top and bottom switches. The MIDI message cannot be sent until the velocity is determined (after the bottom switch is closed).

I play LH bass. I split the lower manual and use the MIDI out of the half below the split to drive a ROMpler containing bass samples. Velocity messages are needed to get sample tonal variation. The rest of the keys are used for the B3 function.

I change this wish thusly: When the great (lower) manual is split into two sections, allow the Keyboard Trig Mode of the keys below the split to be set separately from the rest of the C2D's keys (upper manual and lower manual above the split).

[sweelinck]

I just realized this is probably not possible. In order to determine a key's velocity, the time must be measured between the state change of its top and bottom switches. The MIDI message cannot be sent until the velocity is determined (after the bottom switch is closed).

Yes. It is not just for midi but in general you would have to be able to predict the future to have the key velocity at the point in time when the high trigger point is reached. The key may accelerate to a higher velocity after that, for instance.

[elseif]

I just realized this is probably not possible. In order to determine a key's velocity, the time must be measured between the state change of its top and bottom switches. The MIDI message cannot be sent until the velocity is determined (after the bottom switch is closed).

Yes. It is not just for midi but in general you would have to be able to predict the future to have the key velocity at the point in time when the high trigger point is reached. The key may accelerate to a higher velocity after that, for instance.

Non-causal key triggering - that's a feature.