MIDI 'Chase Events' Is Foiled by Muted MIDI Clips w/ CC Curves

Cubase
,
1

When locating the project cursor on a muted MIDI clip, ‘Chase Events’ doesn’t ignore the clip, but reads (and misinterprets) MIDI CC curves. For example, when placing the project cursor on a muted MIDI clip with MIDI Volume commands (MIDI CC #7), the channel will fall silent, regardless of the latest MIDI Volume event, muted or unmuted, but only if the CC data is represented in the Key Editor by a ‘CC Curve.’

To reproduce this problem, follow these steps:

  1. Launch a new project in Cubase 11
  2. Create a MIDI track for a hardware MIDI instrument
  3. Create an audio track for the same hardware MIDI instrument
  4. Using a hardware MIDI controller, verify that MIDI pass-thru is enabled and that sound is produced from the instrument by use of the hardware MIDI controller
  5. Create two consecutive, empty, one-bar MIDI clips
  6. Using the Key Editor, draw a single MIDI Volume event (MIDI CC #7) of 127 (max) in the first MIDI clip
  7. Using the Key Editor, draw a single MIDI Volume event (MIDI CC #7) of 0 (min/off) in the second MIDI clip
  8. Move the project cursor between the two MIDI clips
  9. Using the hardware MIDI controller, note that the hardware synthesizer’s volume is at 100%
  10. Move the project cursor after the second MIDI clip
  11. Using the hardware MIDI controller, note that the hardware synthesizer’s volume is 0% (off)
  12. If volume remains at 100% verify that ‘Chase Events’ is enabled for CC events in Preferences, and try again
  13. In the Project window, mute (Shift + M) the second MIDI clip
  14. Using the hardware MIDI controller, note that the hardware synthesizer’s volume returns to 100%
  15. Move the project cursor over the muted MIDI clip but after the MIDI Volume = 0 event
  16. Using the hardware MIDI controller, note that the hardware synthesizer’s volume remains at 100%
  17. Using the key editor, modify the MIDI Volume = 0 event, creating a CC Curve, such that MIDI volume ramps smoothly from 100% to 0%
  18. Using the hardware MIDI controller, note that the hardware synthesizer’s volume is now 0% (when, in fact, it should remain at 100%)
  19. Move the project cursor to the middle of the MIDI Volume CC curve you created
  20. Using the hardware MIDI controller, note that the hardware synthesizer’s volume remains at 0%
  21. Using the Key Editor, replace the CC curve with stepped values, first deleting the CC curve’s nodes entirely and then drawing a series of MIDI Volume events by hand, using the Draw or Line tools
  22. Using the hardware MIDI controller, note that the hardware synthesizer’s volume returns to 100%

My system:

Windows 10 Pro Version 10.0.19041 Build 19041
Cubase 11 Pro Version 11.0.10 Build 321 - Built on Jan 13 2021
Intel Core i7-4930K CPU @ 3.40 GHz 3300 MHz, 6 cores, 12 logical…

2

Hi,

Based on your test, I have tried something different. I have Muted the MIDI Part. Then I open the muted MIDI Part in the Key Editor and I started to add some MIDI events (MIDI Notes, MIDI CCs). On the MIDI Monitor, I can see, the MIDI data are sent out, even though the MIDI Part has been muted.

Isn’t this actually the source of the issue, you describe?

3

Hi Martin,

I’m not sure if we’re describing the exact same thing or not, but it sounds like we’re in the same ballpark. I’ve repeated the test using the MIDI Monitor instead and verified its accuracy.

Your description of the problem matches mine except for a couple details I will clarify:

  1. While there are no CC Curves in the muted MIDI clip, everything behaves as you’d expect - no MIDI data appears in the MIDI Monitor whatsoever - playing, stopping, or manually moving the project cursor. Likewise, drawing MIDI data by hand (no CC Curve) produces no MIDI data in the MIDI Monitor.
  2. Once a CC Curve is drawn, MIDI data appears in the MIDI Monitor - but only when the curve is drawn or edited, or when the project cursor stops or is manually moved.
  3. When Return to Start Position on Stop is enabled and the project cursor is located at 0.1.1.0, no MIDI data is produced in the MIDI Monitor, whether playback is stopped before, during, or after the CC Curve.
  4. When Return to Start Position on Stop is enabled and the project cursor is located anywhere other than 0.1.1.0, MIDI data is produced in the MIDI Monitor, either when playback is stopped before, during, or after the CC Curve.
  5. When Return to Start Position on Stop is disabled and the project cursor is located anywhere (including 0.1.1.0), MIDI data is produced in the MIDI Monitor, whether playback is stopped before, during, or after the CC Curve.
  6. As described above, editing the CC Curve produces a steady stream of MIDI data in the MIDI Monitor.
  7. It appears that all of the unexpected/undesireable MIDI events have a Value1 that matches the controller number of the CC Curve, and a Value2 of 0 (zero), regardless of the shape of the CC Curve. In other words, if the CC Curve has no zero values, the unexpected data is nonetheless always zero.
  8. On a separate note, clicking on a MIDI note in the Key Editor sends the MIDI Note On/Off data to the respective hardware synths without producing any MIDI data in the MIDI Monitor. I like this behavior but would’ve expected the MIDI Monitor to display the events too.

I hope this is helpful.

Thank you for looking into it!

4

Hi,

Reported to Steinberg. Thank you.

1 Like