allanger/ardour
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Activity

do not transition "back" to Rolling by calling start_transport() if a locate was for loop-end

Browse Source 
We never stopped the transport, so there's no reason to start it again. Doing so causes alignment problems
because all tracks have their ::run() ranges reinitialized
This commit is contained in:
Paul Davis
2019-11-06 23:54:34 -07:00
parent 625b8297ea
commit f04ee50375
1 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
libs/ardour/transport_fsm.cc
View File

@@ -421,6 +421,7 @@ TransportFSM::locate_for_loop (Event const & l)
assert (l.type == Locate);
DEBUG_TRACE (DEBUG::TFSMEvents, string_compose ("locate_for_loop, wl = %1\n", l.with_loop));
current_roll_after_locate_status = l.with_roll;
_last_locate = l;
api->locate (l.target, l.with_roll, l.with_flush, l.with_loop, l.force);
}
@@ -484,9 +485,11 @@ TransportFSM::should_roll_after_locate () const
void
TransportFSM::roll_after_locate () const
{
DEBUG_TRACE (DEBUG::TFSMEvents, "rolling after locate\n");
DEBUG_TRACE (DEBUG::TFSMEvents, string_compose ("rolling after locate, was for_loop ? %1\n", _last_locate.with_loop));
current_roll_after_locate_status = boost::none;
api->start_transport ();
if (!_last_locate.with_loop) {
api->start_transport ();
}
}
void