View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009142 | ardour | bugs | public | 2022-12-04 13:46 | 2023-01-18 13:31 |
| Reporter | noedig | Assigned To | paul | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Platform | Ubuntu | OS | Linux | OS Version | (any) |
| Product Version | 7.1 | ||||
| Summary | 0009142: MIDI automation drawing is offset after tempo change | ||||
| Description | When drawing in a region's automation lane for a MIDI parameter, when there has been a tempo change prior to that region, the drawing input is offset, i.e. when clicking to add a new automation node, the new node does not appear at the click position. | ||||
| Steps To Reproduce | 1. Create a midi track with two midi regions. 2. In-between the regions, create a tempo change marker, so the first region is in 120bpm and the second region is in e.g. 180 bpm. 3. Enable a midi parameter automation lane for the track, e.g. Bender or CC. 4. In draw mode, drawing in the first region's automation area works fine. Drawing in the second region's automation area (after the tempo change) does not work correctly. When clicking to add nodes, they are offset i.e. do not appear where clicked. | ||||
| Additional Information | Forum post with gif screenshots: https://discourse.ardour.org/t/midi-bender-automation-drawing-glitches/107986 | ||||
| Tags | automation, draw, Midi, tempo change | ||||
|
|
|
|
|
Could you please try a nightly build, because I believe this is already fixed. |
|
|
Ardour 7.1.211 Nightly - can confirm the same bug |
|
|
Confirmed here too, bug is still in nightly v7.1-211 2022-12-04 |
|
|
fixed in commit 1728b691 |
|
|
Drawing nodes in the second region (after the tempo change) works now (nightly Ardour-7.1.239-dbg-w64). However, there is still this odd behaviour (see attached gif): when moving an existing node, and then inserting a new one, the former node position jumps. |
|
|
I think I still have this same issue on 7.2. (Debian 10) I followed these steps to reproduce the problem: 1) make automation pattern on some MIDI parameter (like bend), 2) move the MIDI region elsewhere (not sure if relevant), 3) make a tempo change in the project before MIDI region, 4) try to add or edit automation point to different location (you'll see effects when it doesn't align with the snap setting and zooming in/out shows it gets messed up) |
|
|
To clarify my previous comment: It seems that editing the the already drawn points is the bigger issue. They still get misplaced after tempo change. Drawing new points somewhat works for me. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-12-04 13:46 | noedig | New Issue | |
| 2022-12-04 13:46 | noedig | Tag Attached: automation | |
| 2022-12-04 13:46 | noedig | Tag Attached: draw | |
| 2022-12-04 13:46 | noedig | Tag Attached: Midi | |
| 2022-12-04 13:46 | noedig | Tag Attached: tempo change | |
| 2022-12-04 13:46 | noedig | File Added: Peek 2022-12-04 15-31 Ardour bender automation 2.gif | |
| 2022-12-04 14:52 | paul | Note Added: 0026979 | |
| 2022-12-04 16:45 | cooltehno_bugs | Note Added: 0026980 | |
| 2022-12-04 16:45 | cooltehno_bugs | File Added: automation_tenpo_change_glitch.gif | |
| 2022-12-04 17:09 | noedig | Note Added: 0026981 | |
| 2022-12-05 21:55 | paul | Assigned To | => paul |
| 2022-12-05 21:55 | paul | Status | new => resolved |
| 2022-12-05 21:55 | paul | Resolution | open => fixed |
| 2022-12-05 21:55 | paul | Note Added: 0026984 | |
| 2022-12-08 12:08 | noedig | Note Added: 0027000 | |
| 2022-12-08 12:08 | noedig | File Added: ardour automation 2022-12-08.gif | |
| 2023-01-18 13:06 | Arello | Note Added: 0027188 | |
| 2023-01-18 13:31 | Arello | Note Added: 0027189 |
