Skip to content

Conversation

@BeauregardTA
Copy link

While this information is hinted at elsewhere in the documentation, is is only found in pages concerning training models. People who are looking to deploy pre-trained models are likely to miss this information and it should be explicitly stated in parts of the documentation that they are likely to look.

While this information is hinted at elsewhere in the documentation, is is only found in pages concerning training models. People who are looking to deploy pre-trained models are likely to miss this information and it should be explicitly stated in parts of the documentation that they are likely to look.
@HarikalarKutusu
Copy link

I think the importers here are for this purpose:

https://github.com/coqui-ai/STT/tree/main/bin

Shouldn't that phrase point to them?
It is not only the audio format but the cvs files are also needed.

@BeauregardTA
Copy link
Author

Well, the readme in that directory says that those are all for training models. Somebody with more knowledge of how the project works will have to tell me if they are also relevant to transcribing audio files.

@HarikalarKutusu
Copy link

Right. The whole workflow (train/test/inference) needs 16 kHz .wav files as input.
Train and test (evaluate) also need .cvs files in a specific format, either prepared by the importers or custom scripts.

Maybe like this?

Currently, 🐸STT is only compatible with 16 kHz .WAV format. Datasets in other formats will need to be converted using the provided importers or custom scripts before they can be used in 🐸STT.

What do you and the maintainers think?

Copy link
Collaborator

@wasertech wasertech left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

… 🐸STT can is only compatable …

Can is only?

@wasertech
Copy link
Collaborator

wasertech commented Mar 19, 2023

It also works with opus files in MLS I.e.

https://github.com/coqui-ai/STT/blob/main/bin/import_mls.py

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants