RVC-Project / RVC-Project/Retrieval-based-Voice-Conversion-WebUI
Some historical legacy issues
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 38.4k
- Forks
- 5.3k
- PR merge metrics
- No merged PRs in 30d
Description
Unfortunately, I have to tell you the truth that the initial RVC developer, whose name is RVC-Boss, basically refuses ANYONE to do ANY changes (including PR) on HIS project, which is, in his mind, "dirtying" his code. That is the main reason of why this project progresses so slowly. I had a chat with him and decided to REVERT the commit of the main repo to what he like it to be and put the newest code to my repo as below.
https://github.com/fumiama/Retrieval-based-Voice-Conversion-WebUI
My repo will continue to pull the algorithm update from the main repo (this repo), and, is open for everyone to contribute new features. I hope that with this effort, RVC will be better than before by the help from you alls.
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
The issue contains no file, test, or code entry point; start by reading the issue history and comparing the main repository with the linked fumiama/Retrieval-based-Voice-Conversion-WebUI fork. Done would require a maintainer decision about the project's contribution direction and repository ownership, not a localized code change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- developer-experience
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100