View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003329 | ardour | bugs | public | 2010-07-18 15:00 | 2020-04-19 20:14 |
| Reporter | danboid | Assigned To | cth103 | ||
| Priority | normal | Severity | major | Reproducibility | random |
| Status | closed | Resolution | fixed | ||
| Target Version | 3.0-beta1 | ||||
| Summary | 0003329: Extending MIDI automation control points to 127 and zooming causes control point chaos | ||||
| Description | Create a MIDI track and add a MIDI automation track. Draw at least one inverse V shaped curve in the automation track then try dragging the peak to 127- it says 127 but when you release the control point and mouse over it often is only at 126 although sometimes you can drag it to 127 and have it work. Now zoom in and out - this often causes control points set to 127 to either disappear or get relocated to to the start of the track or just relocate randomly, often followed by a crash. Present under 7437 | ||||
| Tags | No tags attached. | ||||
|
|
In fact, the middle point need not be set to 127 to get messed- all thats required is for you to adjust the control points then zoom in and out a couple of times and you should see the data get corrupted. |
|
|
I did get this to happen once, but it's hard to reproduce. |
|
|
I can easily reproduce this under 7448 lucid 64 but I don't think its anything special about 127 although I do still have trouble dragging control points to that value with the mouse- it easier for me to CTRL-RMB and type it in if I really want 127. Try it like this: Draw a MIDI auto peak Zoom In/out - Curve OK CTRL-RMB top control point of peak - set to 127 Zoom In/out - Curve not OK |
|
|
Should be fixed in SVN. The use of the control point dialogue to adjust the point position was the key step in reproducing this that I was missing. |
|
|
The real bad part of this issue (the control point chaos) seems to be fixed under 7450 but it still seems almost impossible to drag any control points to 127. Even if I expand a MIDI auto track to filling as much of the editor window as poss and drag a control point 'beyond' the top of the track, 99% of the time it comes out as 126. However, that is no major issue thanks to CTRL+RMB click but that isn't exactly obvious and so newbs will end up wondering how to get a max value if unfixed. |
|
|
126 limit bug fixed in SVN. |
|
|
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. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2010-07-18 15:00 | danboid | New Issue | |
| 2010-07-18 15:39 | danboid | Note Added: 0008469 | |
| 2010-07-18 22:06 | cth103 | cost | => 0.00 |
| 2010-07-18 22:06 | cth103 | Target Version | => 3.0-beta1 |
| 2010-07-19 01:42 | cth103 | Note Added: 0008476 | |
| 2010-07-20 11:20 | danboid | Note Added: 0008503 | |
| 2010-07-20 16:54 | cth103 | Note Added: 0008507 | |
| 2010-07-20 16:54 | cth103 | Status | new => feedback |
| 2010-07-20 18:32 | danboid | Note Added: 0008509 | |
| 2010-10-02 00:28 | cth103 | Note Added: 0009203 | |
| 2010-10-02 00:28 | cth103 | Status | feedback => resolved |
| 2010-10-02 00:28 | cth103 | Resolution | open => fixed |
| 2010-10-02 00:28 | cth103 | Assigned To | => cth103 |
| 2020-04-19 20:14 | system | Note Added: 0022165 | |
| 2020-04-19 20:14 | system | Status | resolved => closed |
