View Issue Details
|ID||Category||Date Submitted||Last Update|
|0008217||bugs||2020-06-07 22:01||2020-07-02 18:07|
|Platform||Thinkpad T460s||OS||Ubuntu||OS Version||20.04 LTS|
|Fixed in Version|
|Summary||0008217: MIDI note becoming invisible when trimming region with first note perfectly quatized|
|Description||see attached video|
|Steps To Reproduce||Create MIDI region.|
Put a note on the start of a bar, use quantize to be perfectly sure.
Activate snapping on bars
Try to trim the region to the beginning of above bar
The note vanishes when snapping pulls the region beginning on the bar position
* Trimming with "J" results also in vanishing of MIDI note
* Cutting with "C" Cutting mode results also in vanishing note
* But "Slicing" with "S" keeps the note visible
And: Though the note is invisble, the note is playing on Playback
simplescreenrecorder-2020-06-08_00.39.50.mp4 (789,161 bytes)
this was a good bug report. thanks.
the bug only occurs, as far as i can determine, if the region is created unsnapped. If the region is created snapped to the grid, things work as expected.
the reason for the bug is due to rounding errors. the real fix for this is coming in a major code redesign that will be part of 7.0.
MIDI note times are defined by an offset from the start of the MIDI file. So when a note is quantized but the region start is not snapped to the same grid, that offset is some arbitrary fractional value (e.g. 0.504 beats rather than 0.5 beats) . When the region position is then snapped to the grid and we try to determine if the note is inside the region, we get the wrong answer.
|2020-06-07 22:01||derwok||New Issue|
|2020-06-07 22:01||derwok||Tag Attached: Midi|
|2020-06-07 22:42||derwok||File Added: simplescreenrecorder-2020-06-08_00.39.50.mp4|
|2020-06-07 23:03||x42||Relationship added||related to 0008128|
|2020-06-07 23:04||x42||Relationship added||related to 0007947|
|2020-07-02 18:07||paul||Note Added: 0024563|