Trigger delay not taken into account on midi in

[yrn1]

When ‘live playing’ a track with midi (track setup - input/record setup - midi channel 1 = track 1 record), and this track has trigger delay configured, this trigger delay is not used when playing the keyboard. Notes that are recorded and then played back do have the trigger delay applied.

[XORadmin]

When ‘live playing’ a track with midi (track setup - input/record setup - midi channel 1 = track 1 record), and this track has trigger delay configured, this trigger delay is not used when playing the keyboard. Notes that are recorded and then played back do have the trigger delay applied.

Trigger delay applies only on the trigger column, not from other sources or FX.

[yrn1]

Ok. But it’s very disturbing (at least in my case, where MI Rings really needs some trigger delay) to play on the keyboard (while recording) while hearing ‘wrong’ velocity, because rings is still using the previous’ note value. Isn’t the point of trigger delay to compensate for modules that behave like that?

[XORadmin]

Ok. But it’s very disturbing (at least in my case, where MI Rings really needs some trigger delay) to play on the keyboard (while recording) while hearing ‘wrong’ velocity, because rings is still using the previous’ note value. Isn’t the point of trigger delay to compensate for modules that behave like that?

It is exactly for this, but has only been implemented for the trigger column. 
I will move this topic to the feature requests.

[yrn1]

Great thanks!

[yrn1]

This wasn't yet implemented in 1.26, right? There is the choice for 'Column' or 'All' for trigger delay, but it still does not delay triggers coming from midi input.