RVC-Project / RVC-Project/Retrieval-based-Voice-Conversion-WebUI
Default index ratio increased again in latest release - negatively impacting performance for little to no gain?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 38.4k
- Forks
- 5.3k
- PR merge metrics
- No merged PRs in 30d
Description
I noticed that the default value seems to have changed again. I would like to know the reasoning because despite messing with the other option for voiceless consonant and crepe with median filter, it seems to still underperform compared to the old default value. 0.75 is probably a good default to stick with, or maybe a sweetspot of 0.7, considering how much the nearly maxed out index seems to cause raspy sounds, and how little the index really helps when it comes to accuracy (not much)
QuickExample.zip
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is named. Review the current default index ratio and compare it with the older value using the reported voiceless-consonant and CREPE median-filter settings and QuickExample.zip; done requires an agreed default backed by a clear performance comparison.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100