A Bestiary of MIDI Bugs

[sockmonkey72]

Originally Posted by Petey-B

A Real Head Scratcher
In the MIDI Editor I have a script that moves selected notes by an interval; it works most of the time, but in one situation goes horribly awry.
This is the MIDI editor before running the script. The index of the selected note is 9, and overlaps the previous note.



This is the script:

-- Move the selected note back by an eigth
local _,_,_,s,e = reaper.MIDI_GetNote(take,9)
reaper.MIDI_SetNote(take,9,nil,nil,s-480,e-480,nil,nil,nil,true)
reaper.MIDI_Sort(take)

This is the result:



Notes:
This works correctly IF:

• the notes aren't overlapped
• the note is not selected
• the notes are not the same pitch
• the note is moved by the arrow keys rather than the script

If I use MIDI_GetNote to check the lengths after, they don't reflect the longer note. It does however appear correctly in the event list.
I haven't come up with a workaround for this, it always seems to happen when the notes fall on the same starting point.

I wasn't sure if this belonged in Bug Reports or Developer's Forum, but I found this thread and it seemed appropriate...

This is a long-standing bug in the high-level API. You can use my drop-in replacement, MIDIUtils (here), which solves it.

[Petey-B]

Originally Posted by sockmonkey72

This is a long-standing bug in the high-level API. You can use my drop-in replacement, MIDIUtils (here), which solves it.

First off, thank you for all that work, I found your MIDI Utils repository and got the Lua code.
Unfortunately my scripts are ultimately linked to a TouchOSC control surface, rather than a native GUI that uses a defer loop.
As a result I have to keep my scripts short and autonomous; faders and encoders call them repeatedly (require is not an option).
You can find some examples of these in the thread TouchOSC Widgets for Reaper.
So my plan is to extricate the code needed to make my TouchOSC Note Mover work properly, and merge it into my own (hopefully learning a few things in the process). I've grown quite fond of Lua, it's first class functions and total disregard for data typing reminds me of my days of working in assembler

[vanceism7]

Has anyone else seen this glitch? I've been refraining from upgrading my reaper version because it makes playback very annoying.



If I start my track from an area where a midi cc vertex isn't present (like in the screenshot), the cc value is completely ignored until it hits the next vertex, then it starts following along again. I recently upgraded to v7.02 and now v7.03 but looks like this hasn't been fixed yet still.

I wasn't sure if it had been reported yet or not, I couldn't find anything searching the forums and the net so I figured I'd ask

[Denys]

It's not technically a bug but when scrolling between MIDI notes using the left and right keys (assigned to "Select previous/next note" in my configuration), shouldn't the view follow the cursor when it gets out of the window?

[JacobTrial]

Please check the video, there is some "ghost" midi being added at the end of an event and i cannot see it to delete it... it only happens at a certain zoom-out level. Focus on the midi velocity lane where my mouse cursor is.

https://drive.google.com/open?id=1co...0&usp=drive_fs

[Holzwurm]

My bug report didn't get any response. If anybody could be so kind and test it, it would be much appreciated.

MIDI Editor bug: Using the event properties dialog on notes destroys selected cc events and turns them into notes

With "CC selection follows note selection" set to ON,
-select some notes with cc events "below" them
-open Event Properties.
-select "Notes" from dropdown
-edit velocity field
>selected CCs are converted to notes with velocity values that equal the former CC values modified with the edit value. The note number of the notes getting created by the bug is the CC number of the CC events getting deleted by the bug. E.g cc 4 events become E-1 notes.

If anybody could either confirm this or tell me what I got wrong, that would be awesome.

.gif of the bug, more material in the original thread:

[sockmonkey72]

Originally Posted by Holzwurm

My bug report didn't get any response. If anybody could be so kind and test it, it would be much appreciated.

MIDI Editor bug: Using the event properties dialog on notes destroys selected cc events and turns them into notes

With "CC selection follows note selection" set to ON,
-select some notes with cc events "below" them
-open Event Properties.
-select "Notes" from dropdown
-edit velocity field
>selected CCs are converted to notes with velocity values that equal the former CC values modified with the edit value. The note number of the notes getting created by the bug is the CC number of the CC events getting deleted by the bug. E.g cc 4 events become E-1 notes.

If anybody could either confirm this or tell me what I got wrong, that would be awesome.

.gif of the bug, more material in the original thread:

I didn't test this, but based on your description, it's expected behavior. Event Properties applies to all selected events, and you are changing the event type of all selected events to Notes. Note-on events have 2 bytes of data { notenum, velocity }. CC events also have 2 bytes of data { ccnum, value }, so it's just doing the best translation of the events it can.

[Holzwurm]

Thank you so much, I misunderstood and assumed the event type field was a filter instead of the new event type. Now it all makes sense, vielen Dank!

[JRTaylorMusic]

Requesting that this issue be added under Mouse modifiers and editing actions.
where

MIDI note >> left click >> Cmd >> Toggle note selection
stops working if
MIDI note >> left drag >> Cmd >> Edit note velocity