RVC-Project / RVC-Project/Retrieval-based-Voice-Conversion-WebUI
Model Inference Hangs Indefinitely at RMVPE Model Loading
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 38.4k
- Forks
- 5.3k
- PR merge metrics
- No merged PRs in 30d
Description
Copy# Title: Model Inference Hangs Indefinitely at RMVPE Model Loading on RTX 4060
Issue Description
When trying to perform voice conversion inference on RTX 4060, the process stops responding at the RMVPE model loading stage. The last log message shows "Loading rmvpe model,assets/rmvpe/rmvpe.pt" and then hangs for over 5 minutes with no further logs or progress indicators. This makes it impossible to determine if the process is still working or has frozen completely.
Environment
- GPU: NVIDIA GeForce RTX 4060
- CUDA Version: 12.6
- Driver Version: 560.94
- Docker container environment
Steps to Reproduce
- Trained model successfully (model1)
- Generated index file successfully at
/app/logs/model1/added_IVF378_Flat_nprobe_1_model1_v2.index - Attempted inference with the following settings:
- Input file:
/app/data/M_Ehyun/EJ_DeEssed.wav - Model: model1
- Pitch extraction method: Initially RMVPE, then tried pm (both hang)
- Input file:
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
Reproduce inference in the Docker environment with the reported RTX 4060 setup, starting from the log entry "Loading rmvpe model,assets/rmvpe/rmvpe.pt". Compare the RMVPE and pm pitch-extraction runs and inspect whether either produces further logs or an error; done means the hang is explained or inference progresses past model loading.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- audio-video-rtc, machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100