View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004401 | ardour | bugs | public | 2011-10-28 00:26 | 2020-04-19 20:15 |
| Reporter | nettings | Assigned To | cth103 | ||
| Priority | high | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Platform | Linux x86_64 | OS | openSUSE | OS Version | 11.4 |
| Target Version | 3.0-beta2 | ||||
| Summary | 0004401: custom metering points are forgotten when the metering is switched around | ||||
| Description | custom metering points are not retained and will end up at their default location (post everything) when the metering has been switched. | ||||
| Steps To Reproduce | select custom metering in a mixer strip, move the metering point away from its default location, for example just above the fader. then toggle the metering button around until you are at "custom" again. the metering point is at the default position again and the user selection has been forgotten. | ||||
| Additional Information | i'd suggest to keep the metering "plugin" permanently visible in the mixer strip (reflecting the currently selected metering position), and to do away with the metering button at the bottom. the metering "plugin" could then offer a menu like any other plugin, where the selections in|out|pre|post|custom are available. the screen space for the now unused metering button could be used to make track comments more visible again. | ||||
| Tags | No tags attached. | ||||
|
|
currently, the pseudo-plugin has a checkbox, like all other plugins. when unchecked, the meter freezes (hopefully conserving cpu). it would be nice (and more consistent) if the non-custom metering modes could be switched off too. that would be possible with the above suggestion. |
|
|
I'm not convinced about the always-visible meter thing, but we should fix the memory of custom metering points. |
|
|
Custom metering points should be saved in SVN 10641. If you feel strongly about the permanent meter visibility, would you mind filing a feature request? Thanks! |
|
|
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 |
|---|---|---|---|
| 2011-10-28 00:26 | nettings | New Issue | |
| 2011-10-28 00:26 | nettings | cost | => 0.00 |
| 2011-10-28 00:28 | nettings | Relationship added | related to 0004400 |
| 2011-10-28 00:29 | nettings | Relationship added | related to 0004398 |
| 2011-10-28 00:38 | cth103 | Target Version | => 3.0-beta1 |
| 2011-10-28 00:43 | nettings | Note Added: 0011815 | |
| 2011-11-14 16:57 | cth103 | Note Added: 0012011 | |
| 2011-11-14 16:57 | cth103 | Status | new => confirmed |
| 2011-11-14 16:57 | cth103 | Target Version | 3.0-beta1 => 3.0-beta2 |
| 2011-11-16 00:58 | cth103 | Note Added: 0012078 | |
| 2011-11-16 00:58 | cth103 | Status | confirmed => resolved |
| 2011-11-16 00:58 | cth103 | Resolution | open => fixed |
| 2011-11-16 00:58 | cth103 | Assigned To | => cth103 |
| 2020-04-19 20:15 | system | Note Added: 0022792 | |
| 2020-04-19 20:15 | system | Status | resolved => closed |
