RVC-Project / RVC-Project/Retrieval-based-Voice-Conversion-WebUI

training tricks?

Open
#2,326 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
38.4k
Forks
5.3k
PR merge metrics
No merged PRs in 30d

Description

train with 20min high quality speech data. batchsize 8 for 40 epoch. with pitch guiding on.
loss decreases from 32 to 25 around.
The audio to audio result is far from fidelity to trained voice. It's much much worse than a simple oneshot result with VITS TTS.
There is no overfitting, the result sound quality is just as nice as input audio with no fake distortions.

here are some questions if the rvc can possible be trained with any careful tuning:

  1. What level of loss is supposed to be usually if the training converges ?
  2. My data audio contains empty blanks. Though they take very small percent in 20min. The sliced audios may contain totally blank pieces, can that hurt the training to the degree that there is no any fidelity ?
  3. What's the most often happening issue if the training of RVC gets under-fitting ? I don't think improving epoch is the answer. Can you provide some stardard rules for the training data quality?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or entry point is named; start by reproducing the stated 20-minute, batch-size-8, 40-epoch training setup with pitch guidance and inspect the resulting fidelity. Done would require a confirmed cause and a clearly defined training-data or tuning change that resolves the reported gap.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
audio-video-rtc, machine-learning
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
18/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.