View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001105||ardour||bugs||public||2005-09-29 19:31||2009-07-04 22:32|
|Summary||0001105: Transport conflict when Ardour is not the master|
|Description||If Ardour is both synced to Jack and the option is set to "stop transport at end of session" it will give the transport hell once it moves past the end of the session.|
Ardour needs to disreguard this option when it is not the transport master.
|Tags||No tags attached.|
Ack! Disreguard the report. I must have been on something. I had mistakenly left ardour as the jack time master.
However, I came upon a related bug that I don't think is due to my incompetence. It Ardour is both synced to jack and the jack time master, the loop mode play back acts odd. When looping back it gets stuck and stutters. It's as if changing the transport time screws with the sync of the playback and it is fighting itself trying to change the transport time.
Ok in 2.8 it seems that when locked to an external TC ardour still tries to respect its stop transport on session end option. This can result in it going back to where palyback stated and looping, or stopping outright.
Really what should happen is when locked to an external timecode, thatoption should not be enabled at all, and Ardour should continue so long as the transport continues, unless it is the TC master.
Given this I am updating this bug to apply to 2.8.
|2005-09-29 19:31||FishB8||New Issue|
|2005-09-30 19:45||FishB8||Note Added: 0002350|
|2009-07-04 22:32||seablade||Note Added: 0006264|
|2009-07-04 22:32||seablade||Severity||minor => tweak|
|2009-07-04 22:32||seablade||Status||new => confirmed|
|2009-07-04 22:32||seablade||Product Version||0.99 => 2.8|
|2009-07-04 22:32||seablade||Description Updated|
|2009-07-04 22:32||seablade||Additional Information Updated|
|2009-07-05 01:55||seablade||Relationship added||related to 0002017|