Ted Felix

This is really interesting. It shows some error, but I'm not sure how much. I'm not used to working in timecode for this sort of thing. Samples is more precise and simpler to convert to msecs. Is this showing hundredths of a frame? What standard? 29.97fps NTSC? 23.976 HDTV? Something else? Can you redo the screenshot in samples mode along with providing the sample rate?

Just pushed a fix [af8355]. If there is no matrix velocity in the rg file, it goes with 100. If the matrix velocity is 0 (which is bogus and shouldn't be allowed), it changes it to 100. That should cover the issue. Please test latest git.

Fix matrix velocity can end up 0

A note-on event with velocity zero is essentially a note off. We probably shouldn't even allow that drop down to have the number zero in it. It makes no sense given that rg avoids exposing the "note-off" concept to the user. At any rate, I'll take a quick look and see if I can figure this out. I think I have some old example files lying around from this that I can use to test.

EventParameterDialog: Cleanup

Set Event Velocities used to default to 100, which is the default value of a note. Now it defaults to an unlikely value of zero now. Was that an intentional change? Check the "Velocity" value in the toolbar between Grid and Quantize. It's using the value from there.

when editing an event, nothing is selected on closing the popup, so you don't know which one was edited Fixed in [c6ec41]. Please test latest git.

ELE: Fix edit not leaving event selected