Can't select Midi note after update?

[explodingPSYCH]

Just updated (10/9/18) and now I can't select midi notes. I'm using left click default action as "select" in the "Midi Note" mouse modifier.

I also have it set up to deselect all other notes in when I click on the piano roll (so I don't accidentally leave other notes selected).

What gives? It was working before the update.

[toadhjo]

I seem to be having the same issue intermittently with Reaper 5.96 on Windows 10.

For example, everything will be working fine, but then I'll split an item and suddenly I can't select notes properly. My cursor gets stuck as the "pencil".

The following gif shows Reaper's behavior before and after splitting an item.



Edit: Reverting to 5.95 has resolved the issue.

[explodingPSYCH]

Originally Posted by toadhjo

I seem to be having the same issue intermittently with Reaper 5.96 on Windows 10.

For example, everything will be working fine, but then I'll split an item and suddenly I can't select notes properly. My cursor gets stuck as the "pencil".

The following gif shows Reaper's behavior before and after splitting an item.



Edit: Reverting to 5.95 has resolved the issue.

Yeah, same. My cursor would get stuck in paint mode (as I think that is the mode I have it in by default), but otherwise same behavior you are showing in your gif.

I've reverted back for now and will skip this update unless anyone has an idea of how to fix this behavior in the new update?

[samizdat]

Same here, this bug is really annoying, i was forced to roll back to version 5.95 too. I thought I was crazy at first or that I accidentally hit an unknown key...
The only way to have all the cursors back in 5.96 was to create a new midi item and rewrite all the notes / events from scratch, can't start from a split item (using S) from a previous pattern.
Please fix this, i confirm it has been introduced with the new version.

[daxliniere]

Reporting in to say I'm experiencing this, too.

[Justin]

Edit: ah, ok -- it's when the item is looped and the first iteration has the notes invisible, then those notes aren't hit tested on later iterations. Fixing!

[daxliniere]

Ah, just emailed you. Glad you got it.

Can you tell why a MIDI item becomes blank when Loop source is disabled? (emailed project)

[Justin]

Originally Posted by daxliniere

Ah, just emailed you. Glad you got it.

Can you tell why a MIDI item becomes blank when Loop source is disabled? (emailed project)

The start offset is probably very high (so that the first loop is tiny)... open item properties and have a look, then resize the left edge slightly to get it to zero out...

[daxliniere]

Originally Posted by Justin

The start offset is probably very high (so that the first loop is tiny)... open item properties and have a look, then resize the left edge slightly to get it to zero out...

Could you add a protection against this behaviour?

[Justin]

Originally Posted by daxliniere

Could you add a protection against this behaviour?

Yeah, I think we'll (in a future version) make it so that if the amount of the source visible would be very small, it will move it to the next loop iteration when unlooping.

[daxliniere]

Awesome, thank you.

[toadhjo]

The latest updating is working great for me, too! Thank you for solving the issue quickly