0000435: automation logic in 0.505.1 - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0000435	ardour	bugs	public	2004-05-09 16:03	2004-05-25 19:06

Reporter	rparker	Assigned To
Priority	urgent	Severity	feature	Reproducibility	always
Status	closed	Resolution	open

Summary	0000435: automation logic in 0.505.1
Description	Ardour/GTK 0.505.1 running with libardour 0.805.1 Test session that was created with 0.500, and has been opened and saved with each upgrade since that version. The session has 26 stereo tracks, thirteen have fade events at the tail. Record automation events at the end of track_1, i.e. fade the tail. Repeat fade events for each song where it's required. Assume track_2 is about five seconds longer than track_1 so you can visually observe what happens between the two tracks and their respective automation events. 1. After recording automation events for the tracks where it's required, return to track_1 play the automation event. When finished, mute track_1. 2. Make track_2 mixerstrip visible in the editor and play the automation event with mute engaged. At this point the automation fade events for track_1 are being applied to track_2. However, you will not see track_1 automation fade events occur on track_2 unless you start and stop the transport: stop transport; fade adjusts to the recorded event start transport; fade returns to 0.0dbfs So, the automation logic for which track events apply to is foobar because if you have 13 tracks with fade events as described above the events for any of those tracks appear to be applied to any other track. Throughout the above the state of Pan for some but not all tracks is positioned at Center. Unmuting a track will cause pan to position hard L. and R. where it's expected. I don't know what happens to Pan in a session that's created with 0.505.1; however, in this session from .501.? Pan for the entire track appears to be dictated by automation events and the correct state is achieved only when the track is not in Mute. So there could be a two fold problem here. Pan is dictated by automation and mute controls whether the automation event will apply. Damned, I hope you can make something out of this report. It's very difficult to describe what's happening because we have several bugs that are very intertwined and things get pretty confusing.
Tags	No tags attached.

Date Modified	Username	Field	Change
2004-05-09 16:03	rparker	New Issue
2004-05-09 16:03	rparker	E-mail	=> rtp405@yahoo.com
2004-05-25 17:11	paul	Note Added: 0000826
2004-05-25 17:11	paul	Status	new => feedback
2004-05-25 19:06	rparker	Status	feedback => closed
2004-05-25 19:06	rparker	Note Added: 0000829