-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document the DB directory structure #7
Comments
Duplicate of #5 |
I am re-opening this because now train.py wants DB/wav, DB/eval_wav, and DB/wav Could you please explain what the directory structure should be? I have different WAV files I want to train |
As of default, the script is written to read all files with "wav" extension under 'DB/VoxCeleb2/wav' for training, and 'DB/VoxCeleb1/eval_wav/' for speaker embedding extraction in the test phase. Put your dataset under aforementioned directory, or give "DB", "DB_vox2", "dev_wav" as arguments when running scripts :) |
So there are still some details that I am missing, and unfortunately I am having difficulty understanding the code. It's more than all WAV files under Here's what I tried just to create a rough directory structure just to get the code running
But that still doesn't work, it crashes with
So it's constructing the directory paths wrong somehow. I set up a little Google Colab notebook. Or if you could run:
to show your directory structure and also the contents of |
What would be most helpful would be a simple Google Colab notebook that demonstrates how to set up the data and run the code :) |
I have added filetrees. You can discard val_trial.txt as it is unofficial (I just used it for model validation) and veri_test.txt is in "trials" folder. |
I agree that adding documentation and making code available for other datasets will definitely increase readability for other domain researchers : ) However, I'm not sure if I can do it right now.. |
In the meantime, revising |
For people who don't want to use VoxCeleb + VoxCeleb2, it is hard to figure out what the directory structure should be for DB. Could you please document it?
Or even nicer, if there were a simple to download audio dataset (e.g. from torchaudio) that the script would lay out in the right way, people could immediately try your repo and see if it works on their GPU.
The text was updated successfully, but these errors were encountered: