MIDI CC reset inconsistently sends val 0 even when nothing in item

[fierywater]

Edit: Should have said "no CCs in item", there were notes.

Hi! I'm running into what I believe to be erroneous behavior with MIDI CC reset on stop/loop.

I have a Moog Sub 37 and have done the following:
1) Set up MIDI and audio tracks, MIDI routing to and from the Sub 37 (with Local Control off) and audio input monitoring the Sub 37's output.
2) Added an item playing simple 16th notes.
3) Set the timeline to loop the item.
4) Added ReaControlMIDI to the MIDI track for monitoring purposes.

If I play the track, twiddle knobs, and either let it loop or stop playback, Reaper seems to semi-randomly send val 0 messages to the CCs for knobs that I played. I say semi-randomly because it doesn't appear to do it for all CCs. If there's a rhyme or reason to it, I'm not sure what it is.

For example, I just played the item back while moving the knobs for CC114, CC115, CC116, CC117, and CC118. It didn't reset anything on the first loop. On the second loop, it sent value 0 to CC115 and CC117.

There is no automation, CC or otherwise, in the item. I recorded nothing into it - I only drew a series of notes. I'm not sure what's determining the CCs it's trying to reset and resetting to 0 is obviously wrong, as there's no reference for it to draw that from.

I discovered this with a real song and was wondering why the sounds on my Sub 37 were getting messed up on loop, and figuring it out took a while. I easily reproduced it in a test project (attached), though.

I also tested with my Novation Summit, just to make sure it wasn't some quirk with the Moog. I moved the knobs for CC78, CC79, and CC80, and on the second loop (??) it reset CC79 and CC80 to 0 but left CC78 alone.

Anyways, this makes the Reset MIDI CC/Pitch behavior pretty much unusable, although it luckily doesn't happen if the Reset MIDI/CC Pitch settings are disabled. I can work around it with those checkboxes off and just use ReaControlMIDI for automation, but it seemed like it was worth reporting.

I confirmed this behavior on 6.75 and on the latest pre-release (6.75+dev0211), just to make sure it wasn't fixed with one of the chase behavior notes.

The project file I used to test is attached and my specs are below for the sake of completeness:
Windows 11 22H2
Reaper 6.75, also tested on 6.75+dev0211 (both x64)
AMD Ryzen 9 7900X, 32GB RAM
Focusrite Scarlett 18i20, although I used USB-MIDI for both instruments (doesn't seem to matter regardless)

Cheers!

[Justin]

Ah, it shouldn't be sending resets in this case (input monitoring is excluded from the tracking), the fact that it does is a bug! Trying to narrow it down.

Edit: aha, fixing! It was hard to reproduce because it only occurred here when the CC input monitoring occurs at the exact sample as a note-off from the media.

[fierywater]

Originally Posted by Justin

Ah, it shouldn't be sending resets in this case (input monitoring is excluded from the tracking), the fact that it does is a bug! Trying to narrow it down.

Edit: aha, fixing! It was hard to reproduce because it only occurred here when the CC input monitoring occurs at the exact sample as a note-off from the media.

You rock, thanks!

[Justin]

Today’s dev build (see the pre-release forum) should fix!

[fierywater]

Originally Posted by Justin

Today’s dev build (see the pre-release forum) should fix!

I wasn't able to reproduce it in the pre-release - thanks for the quick fix!

[John Novak]

Nice to see MIDI bugs getting attention and quick fixes! I approve