MIDI Chase Events is broken (maybe?)

Cubase
1

I ran into some oddities with the output of a MIDI track the other day which prompted me to investigate further.
It appears that even when MIDI Chase Events is disabled for all event types, MIDI data is still being sent in some cases when navigating a project.

Below is a screen recording showcasing what I’m talking about. The recording was made using Cubase Pro 12.0.70 on Windows 10 Pro 22H2. Before starting Cubase I removed the Preferences folder (%AppData%\Steinberg\Cubase 12_64). I created a new Blank project with a single MIDI Track. The Input and Output Routing of the track was set to Not Connected.

MIDI Chase
Right click and open image in a new tab to increase resolution and readability

The screen recording above is using the MIDI insert plugin “MIDI Monitor” but I also tested with a 3rd party application and saw the exact same result.

This behavior raises a few question for me. Why does Cubase send MIDI CC data when locating before and after the MIDI Part bounds when Chase Events is disabled? Why does Cubase send a CC value of 0—in some cases by itself and in others preceding the entered value in the Part?

Even when Chase Events is enabled, some of cases where Cubase sends MIDI CC data appears illogical to me. For example, placing the Project Cursor before (to the left of) the first MIDI Part in the project.

2

I tested a bit with Cubase 14 and found plenty more inexplicable weirdness when clicking along the timeline while transport is stopped.

So yes, something seems not right.

However, I don’t currently have the enthusiasm to spend more time on testing/documenting this behaviour, since it’s not really within my regular workflow. I always have “chase on” and there’s lots of MIDI routing permutations that show up differently in the MIDI monitor (and other MIDI insert FX).

3

Thank you for taking your time and giving this a looksee.

Yes, it seems something is not quite right, even with chase turned off.

1 Like