ardour/livetrax
13
0
Fork 0
Code

Do not move automation when inserting regions

Browse Source 
RegionInsertDrag or Consolidate Range or any other operation
calling Playlist::add_region() previously triggered RangesMoved()
which resulted in DiskReader::move_processor_automation()

NB. insert + ripple still moves automation correctly.
This commit is contained in:
Robin Gareus 2021-04-29 23:25:50 +02:00
parent 7a89d56009
commit 58557e88c9
Signed by: rgareus
GPG Key ID: A090BCE02CF57F04
2 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
libs/ardour/playlist.cc
View File

@ -800,6 +800,12 @@ Playlist::add_region_internal (boost::shared_ptr<Region> region, samplepos_t pos
region->PropertyChanged.connect_same_thread (region_state_changed_connections, boost::bind (&Playlist::region_changed_proxy, this, _1, boost::weak_ptr<Region> (region)));
region->DropReferences.connect_same_thread (region_drop_references_connections, boost::bind (&Playlist::region_going_away, this, boost::weak_ptr<Region> (region)));
/* do not handle property changes of newly added regions.
* Otherwise this would triggger Playlist::notify_region_moved()
* -> RangesMoved() and move automation.
*/
region->clear_changes ();
return true;
}

1
libs/pbd/stateful.cc
View File

@ -192,6 +192,7 @@ Stateful::clear_changes ()
for (OwnedPropertyList::iterator i = _properties->begin(); i != _properties->end(); ++i) {
i->second->clear_changes ();
}
_pending_changed.clear ();
}
PropertyList *