View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0004400ardourbugspublic2011-10-28 00:172020-04-19 20:15
Reporternettings Assigned Tocth103  
PriorityhighSeverityfeatureReproducibilityalways
Status closedResolutionfixed 
PlatformLinux x86_64OSopenSUSEOS Version11.4
Target Version3.0-beta1 
Summary0004400: custom metering points are not saved
Descriptionafter a session has been loaded, all custom metering points have dropped to the end of the plugin chain, even though they had been moved to immediately post-fader before saving the session.
Steps To Reproduceadd some plugins, put the custom metering point somewhere other than at the very end, preferrably between the fader and some other post-fader plugins.
Additional Informationthis is a usability issue for me because i'm currently working on very large sessions (>60 tracks), where manual restoration of metering points is not really feasible. this is an ambisonic session, where each mono track fans out to a 16ch mastering bus after the custom panner. i need to see the levels _after_ the faders, but i'm only interested in the one mono level, not in the 16 individual components. using "out" or "post" is not an option, because i don't have the processing power or screen real estate for 60x16 mostly useless meters.
TagsNo tags attached.

Relationships

related to 0004398 closedcth103 No way to see at a glance if a track has comments. 
related to 0004401 closedcth103 custom metering points are forgotten when the metering is switched around 

Activities

cth103

2011-10-29 01:19

administrator   ~0011824

Fixed in SVN 10330.

nettings

2011-10-29 20:35

manager   ~0011827

thanks. it works for me, and it's a huge time-saver already.
bug 4401 is still open, though - i wonder whether it could be fixed easily using the same persistence mechanism.

system

2020-04-19 20:15

developer   ~0022791

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.

Issue History

Date Modified Username Field Change
2011-10-28 00:17 nettings New Issue
2011-10-28 00:17 nettings cost => 0.00
2011-10-28 00:27 nettings Relationship added related to 0004398
2011-10-28 00:28 nettings Relationship added related to 0004401
2011-10-28 00:38 cth103 Target Version 3.0 => 3.0-beta1
2011-10-29 01:19 cth103 Note Added: 0011824
2011-10-29 01:19 cth103 Status new => resolved
2011-10-29 01:19 cth103 Resolution open => fixed
2011-10-29 01:19 cth103 Assigned To => cth103
2011-10-29 20:35 nettings Note Added: 0011827
2020-04-19 20:15 system Note Added: 0022791
2020-04-19 20:15 system Status resolved => closed