View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005759 | ardour | bugs | public | 2013-11-06 16:28 | 2015-10-30 15:47 |
| Reporter | don3 | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | sometimes |
| Status | new | Resolution | open | ||
| Product Version | 3.0 | ||||
| Summary | 0005759: Dragging a horizontal fader automation line does not always show the same value as the endpoints | ||||
| Description | Dragging a horizontal fader automation line (between 2 points of equal value) does not always show the same value as the endpoints'. Steps to reproduce: - Set two adjacent fader automation points at the same level, creating a horizontal line between them. Hover over the points to confirm their values. - Drag (with left button) the line with the mouse to some other level, noting the pop-up value displayed just before releasing the mouse button. (It isn't even necessary to move the line -- just holding down the left button to see the current value pop up is usually enough.) - Hover over each of the end-points again and observe their values. I would expect the endpoint values to match the last dislayed pop-up value. For me, the value of the endpoints is very often (I'd say > 70% of the time) different, usually by 0.1 - 0.4 dB. The same issue can be seen with region gain automation. I've seen this with all A3 versions I've used so far, including 3.5.14, on Fedora 14 (32-bit) under KDE and Fedora 19 (64-but) under LXDE. | ||||
| Tags | No tags attached. | ||||
|
|
Issue still present with 4.4.0, and nightly 4.4.154. Fixing this could solve/improve a work-flow issue mentioned in notes for bug 0006647. Specifically: When I try to drag a line (after switching to Internal Edit or Grab mode; it doesn't work in Draw mode), the value displayed does not (usually?) match either endpoint, and when I release the mouse button, the values of the endpoints don't match the value displayed during the drag Further, dragging points and lines "feels" (to me) more different than it should -- eg: - Hovering over a line displays a "+" cursor but no value (of course, not all lines are horizontal, so some special handling might be in order there), while dragging a line does show a value. - Dragging lines doesn't seem to have any affinity for 0 dB. |
|
|
This is interesting. If the two endpoints have different values, then the readout should be the value at the grabbed position. I'll investigate this more. |
|
|
This should be fixed in current git (36dd7f8d9d60). Please test. Thanks. |
|
|
With light testing, this issue looks fixed in nightly 4.4.163. (I see there's one more commit in Git after this which could affect line dragging; perhaps I should have waited for the next nightly.) Automation editing/dragging behavior seems much improved with recent changes. :-) Thank you!! There are still some things that (IMO) could be looked at to improve the experience a little more even, at least for my work flow. I can open a new bug report to propose some of those. A couple are mentioned in notes above: - what to display when hovering over a line - what to display while dragging a non-horizontal line - "affinity" for 0 dB when dragging lines |
