MoonInTheRiver / MoonInTheRiver/DiffSinger
the test infer using opencpop dataset isnot working
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.9k
- Forks
- 826
- PR merge metrics
- No merged PRs in 30d
Description
I just follow all the steps in docs SVS-opencpop-e2e.md. All the data are as following:
.
|--data
|--raw
|--opencpop
|--segments
|--transcriptions.txt
|--wavs
|--checkpoints
|--MY_DS_EXP_NAME (optional)
|--0109_hifigan_bigpopcs_hop128 (vocoder)
|--model_ckpt_steps_1512000.ckpt
|--config.yaml
- the first error is "Run the following scripts to pack the dataset for training/inference." . the error log shows that the popcs folder is missing? but the test dataset i used is opencpop, so i manualy set the "raw_data_dir" by "opencpop data folder" in binarize.py and modified the "test_prefixes" to ['2044', 2086] in 0228_opencpop_ds100_rel's config.yaml. Then the packing command ran successfully.
- the second error is "Inference from packed test set". The error log shows that the test set batch num is zero. I want to debug the dataloader, and see where the test folder is. However the code is too complex.
So I wanna konw if i should download the popcs dataset to infer with SVS-opencpop-e2e?
if i want to use the opencpop test data to infer, which configs should be modified?
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
Start with docs/SVS-opencpop-e2e.md, then compare the raw_data_dir and test_prefixes settings in binarize.py and the 0228_opencpop_ds100_rel config.yaml. Inspect the dataloader path used by the “Inference from packed test set” step and its error log. Done means the opencpop test set is packed and inference runs with a nonzero test batch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100