|
|
Screenshot from 2020-10-27 07-44-07.png (9,799 bytes) |
|
|
Is it possible to edit the issue? I forgot to inform my OS version, which is 20.04. |
|
|
I did a few tests and noticed the bug happens when you try to change the velocity of a MIDI note through the mouse (clicking the note and scrolling with the mouse tracker) . If you edit the velocity in the "Edit" window, right-clicking the MIDI note, nothing happens. Since I did this in Ardour 5 without any problems I guess the bug is related to the new features added in 6.3, regarding MIDI notes. For example, in the new version the velocity of a note is shown as a little bar inside the note and changes width dinamically, as we roll with the mouse. |
|
|
The underlying issue is that the GUI queues up events for others to process. But you produce events faster than others (backend, ctrl surfaces etc) can process them. Do you perhaps have any Ctrl surfaces enabled (Preferences > Control Surfaces > ...) Then again repeat MIDI edits might also be able to trigger this, if re-reading the MIDI files takes too long. |
|
|
Hi, thanks for answering. "Do you perhaps have any Ctrl surfaces enabled (Preferences > Control Surfaces > ...)" No, i wasn't even aware of that option. |
|
|
It can be reproduced without MIDI too. Import a long single file recording, for example a voice over recording, more than 30-40 minutes. Attempt to strip silence reproduces this error. Also attempting to normalise a lot many regions results in the same error. 2021-04-22_00-23.png (131,349 bytes) |
|
|
No longer facing this Issue with version versions 6.7 and 6.8 |
|
|
Good to know. Likely fixed in the 6.6 -> 6.7 dev cycle along with similar issues: https://tracker.ardour.org/view.php?id=8626 and https://tracker.ardour.org/view.php?id=8576 |
|
|
Issue has been closed automatically, by Trigger Close Plugin. Feel free to re-open with additional information if you think the issue is not resolved. |
- Anonymous
