fix(alignment-filling-start-end): fix the bug that may generate non-monotonic timecode when filling Nan #793
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Get non-monotonic timecode when a segment get both invalid
start
andend
.See the following example.
Raw data from alignment model:
Filled result:
We can see the end of
seg1
(3) >= start ofseg2
(1), it's non-monotonicWhy
Current code process the start and end independently.
Fix
Let's interpolate them jointly, it can generate monotonic result:
Test Code
Final Notes: Why we get Nan for whole segments?
See this sentence example:
It will be split to 2 sentences badly by the punc model: