View Issue Details

IDProjectCategoryView StatusLast Update
0004195ardourbugspublic2011-10-25 00:18
Reporteroofus Assigned Tocth103  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
PlatformDell D830 core2duo T9300 2.5GHzOSKubuntuOS Version10.10
Target Version3.0-beta1 
Summary0004195: A track that is record armed when a session is loaded doesn't switch the metering back when record is disarmed
DescriptionA track that is record armed when a session is loaded doesn't switch the metering back when record is disarmed.
Steps To ReproduceStart a new session. Add a track. Set its meter point to 'Pre'.
Enable the tracks rec arm button, The metering switches to 'In'.
Release the rec arm the metering switches back to 'Pre'.
Enable the rec arm again, save the session and quite Ardour.
Start Ardour again and re-load the same session.
The track is rec armed as it should be and the meter point is set to 'In', as it should be.
Release the rec arm button on the track and the metering stays at 'In', it should switch back to 'Pre'

The meter point for a rec armed track should be an override for the metering point selected by the user but shouldn't supplant it.
TagsNo tags attached.

Activities

paul

2011-07-18 18:17

administrator   ~0011159

this is interesting. what would it switch it back to, when there's no information on what it was? or is the point that we need to save and restore both metering states?

oofus

2011-07-18 18:29

developer   ~0011160

I don't think that both metering states need to be saved or restored. The metering point is set by the user (pressing the metering button) and when in record the metering point is switched to 'In' regardless. So the logic needs to be : metering position = that set by the user unless in record then it is 'In'. The meter position and record state are already saved in the session.

cth103

2011-10-24 22:54

administrator   ~0011775

Fixed in SVN 10304.

oofus

2011-10-25 00:18

developer   ~0011780

Excellent, thanks for fixing this. Seems to work absolutely fine.

Issue History

Date Modified Username Field Change
2011-07-17 12:53 oofus New Issue
2011-07-17 12:53 oofus cost => 0.00
2011-07-17 13:48 cth103 Priority high => normal
2011-07-17 13:48 cth103 Target Version => 3.0-beta1
2011-07-18 18:17 paul Note Added: 0011159
2011-07-18 18:29 oofus Note Added: 0011160
2011-10-24 21:53 cth103 Status new => confirmed
2011-10-24 22:54 cth103 Note Added: 0011775
2011-10-24 22:54 cth103 Status confirmed => resolved
2011-10-24 22:54 cth103 Resolution open => fixed
2011-10-24 22:54 cth103 Assigned To => cth103
2011-10-25 00:18 oofus Note Added: 0011780
2011-10-25 00:18 oofus Status resolved => closed