Add correct_vuv option for data pre-processing #123
Merged
+52
−15
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
this prevents unwanted F0 estimation failrues on silence regions tested on ofuton-p database Note that there's possible downside that we may mask out valid F0s so far `correct_vuv` is enabled for configs that involve vibrato estimation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
this prevents unwanted F0 estimation failrues on silence regions
tested on ofuton-p database
Note that there's possible downside that we may mask out valid F0s
so far
correct_vuvis disabled by default.Examples
from ofuton-p database
kagome_kagome_seg0.wav
kagome_kagome_low_seg0.wav