View Issue Details

IDProjectCategoryView StatusLast Update
0006845ardourbugspublic2016-04-10 19:04
Reportermhartzel Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
PlatformLinuxOSGentooOS VersionGentoo
Product Version4.7 
Summary0006845: Moving the first automation volume point on a track, also moves the next
DescriptionThe first volume automation point on a track sometimes gets "tied" to the next automation point. With this I mean that if you record volume automation in the middle of a audio track by moving a fader and then move to the beginning of the track and move the first automation point up or down (that Ardour creates automatically), then the next automation point (that you recorded yourself) moves also. The first and the next point gets tied together so that they always maintain their relative volume difference. This makes it impossible to change the starting volume level of the track since it also affects the next automation point.
Steps To ReproduceArdour 4.7

- Create a new session and one audio track to it.
- Show fader (volume) automation on the track.
- Move the play head to 10 seconds on the timeline
- Change the track volume automation mode to touch.
- Move the automation volume fader to -30 dB.
- Start playback and move the volume automation fader. This records automation for the movement.
- Stop playback
- Use either Grab or Draw mouse tool and move the automation volume point at the beginning of the track up or down. This point and the next moves together.
- Now move the first automation point you recorded yourself. Moving it moves also the automation point at the beginning of the track.

Result: Moving the automation point at the beginning of the track moves also the next point that the user created. You can not change the volume level at the beginning of the track without it changing the volume of the next automation point.

Expected result: Moving the volume automation point at beginning of the track does not affect the volume level of the next automation point and these points can be moved independently of each other.
TagsNo tags attached.

Activities

mhartzel

2016-04-10 19:04

reporter   ~0018145

I tested this thing a little more and realized that this is caused by two automation points being selected at the same time. Pressing the ESC - key clears selection and then the automation points move independently of each other as one expects.

I think this case is on the edge of "user error" and Ardour unexpected behaviour and such a minor thing that it probably is best that this bug report is closed :)

Issue History

Date Modified Username Field Change
2016-03-28 17:53 mhartzel New Issue
2016-04-10 19:04 mhartzel Note Added: 0018145
2016-04-10 19:04 mhartzel Status new => closed
2016-04-10 19:04 mhartzel Resolution open => no change required