Bug in Delta MIDI Computer player device?

[gribbly]

I think I found a bug in Delta MIDI Computer. Here's a video:

In the video:

• Reason drum kits is being played a by a constant note (F#1) in the sequencer

• Delta is intercepting F#1 and transposing it based on the state of CV1

• CV1 is being driven by a Thor Mod Wheel (visualized in Compare CV Scope)

• The basic idea is that as CV1 changes, you hear different toms

Here's the bug:

• If you quantize to the grid, Delta "misses" the first note in the loop - it plays a F#1 even when CV1 should be modifying it to a higher note

• If I move the first note to be a few ticks late, it works correctly

• But if the first note is hard quantized to the grid, the "If" node seems to miss the state of the CV?

Anyone else encountered this?

EDIT: Reason 12.7d3 standalone, Windows 11, no VSTs

[FLVZ]

I think I found a bug in Delta MIDI Computer. Here's a video:

In the video:

• Reason drum kits is being played a by a constant note (F#1) in the sequencer

• Delta is intercepting F#1 and transposing it based on the state of CV1

• CV1 is being driven by a Thor Mod Wheel (visualized in Compare CV Scope)

• The basic idea is that as CV1 changes, you hear different toms

Here's the bug:

• If you quantize to the grid, Delta "misses" the first note in the loop - it plays a F#1 even when CV1 should be modifying it to a higher note

• If I move the first note to be a few ticks late, it works correctly

• But if the first note is hard quantized to the grid, the "If" node seems to miss the state of the CV?

Anyone else encountered this?

EDIT: Reason 12.7d3 standalone, Windows 11, no VSTs

Yeah noticed this since upgrading also. The first midi note can't start bang-on-the-grid has to be moved forward slightly or it doesn't play, which can be kinda annoying!