We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Sometimes the user may be curious about what the audio will be like after our preprocessing steps.
We have an API to enable the user to save preprocessed waves, which is good: https://github.com/roedoejet/EveryVoice/blob/d117ece5d29947e171bf181bc481c66bb26352ff/everyvoice/preprocessor/preprocessor.py#L121C9-L121C18
I'm sorry that I didn't figure out how to configure save_wave to TRUE in the configuration files.
save_wave
TRUE
The text was updated successfully, but these errors were encountered:
I think we should just only save .wav files, and not .pt. but we can do a benchmark for training speed between .pt and .wav.
.wav
Sorry, something went wrong.
MENGZHEGENG
marctessier
No branches or pull requests
Sometimes the user may be curious about what the audio will be like after our preprocessing steps.
We have an API to enable the user to save preprocessed waves, which is good:
https://github.com/roedoejet/EveryVoice/blob/d117ece5d29947e171bf181bc481c66bb26352ff/everyvoice/preprocessor/preprocessor.py#L121C9-L121C18
I'm sorry that I didn't figure out how to configure
save_wave
toTRUE
in the configuration files.The text was updated successfully, but these errors were encountered: