OPENGIT/Retrieval-based-Voice-Conversion-WebUI
1
0
Fork 0
mirror of https://github.com/RVC-Project/Retrieval-based-Voice-Conversion-WebUI.git synced 2025-01-30 18:22:51 +08:00
Code Issues Packages Projects Releases Wiki Activity

Updated FAQ (Frequently Asked Questions) (markdown)

Rice Cake 2023-05-06 17:23:07 +08:00
parent 0dc4c0dcd2
commit c83797a75d
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
FAQ-(Frequently-Asked-Questions).md

@ -44,8 +44,8 @@ Data of less than 1min duration has not been successfully attempted so far. This
## Q10:What is the index rate for and how to adjust it?
If the tone quality of the pre-trained model and inference source is higher than that of the training set, they can bring up the tone quality of the inference result, but at the cost of a possible tone bias towards the tone of the underlying model/inference source rather than the tone of the training set, which is generally referred to as "tone leakage".<br>
  The index rate is used to reduce/resolve the timbre leakage problem. If the index rate is set to 1, theoretically there is no timbre leakage from the inference source and the timbre quality is more biased towards the training set. If the training set has a lower sound quality than the inference source, then a higher index rate may reduce the sound quality. Turning it down to 0 does not have the effect of using retrieval blending to protect the training set tones.<br>
  If the training set has good audio quality and long duration, turn up the total_epoch, when the model itself is less likely to refer to the inferred source and the underlying model, and there is little "tone leakage", the index_rate is not important and you can even not create/share the index file.<br>
The index rate is used to reduce/resolve the timbre leakage problem. If the index rate is set to 1, theoretically there is no timbre leakage from the inference source and the timbre quality is more biased towards the training set. If the training set has a lower sound quality than the inference source, then a higher index rate may reduce the sound quality. Turning it down to 0 does not have the effect of using retrieval blending to protect the training set tones.<br>
If the training set has good audio quality and long duration, turn up the total_epoch, when the model itself is less likely to refer to the inferred source and the underlying model, and there is little "tone leakage", the index_rate is not important and you can even not create/share the index file.<br>
## Q11:How to choose the gpu when inferring?
In the config.py file, select the card number after "device cuda:". The mapping between card number and graphics card can be seen in the graphics card information section of the training tab.<br>