ardour/livetrax
13
0
Fork 0
Code

Modify Strip Silence so that it can't create regions with -ve lengths

Browse Source 
AFAICT this could happen if a region's end time (on the timeline) was earlier than the end time in the actual recording. This could cause a situation where the last block of detected silence would have an end time greater than the end tome for the region being processed. Strip Silence would create its new regions - but the last one it created would usually come out with a negative duration.
This commit is contained in:
John Emmas 2015-09-18 10:44:07 +01:00
parent b548b6213d
commit c12e8cc47c
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
libs/ardour/strip_silence.cc
View File

@ -100,7 +100,7 @@ StripSilence::run (boost::shared_ptr<Region> r, Progress* progress)
frameoffset_t const end_of_region = r->start() + r->length();
if (last_silence->second != end_of_region - 1) {
if (last_silence->second < end_of_region - 1) {
audible.push_back (std::make_pair (last_silence->second, end_of_region - 1));
}