added support for model_info in CLI

[p0p4k]

added support for model_info #1586
model info can be called using either model_info_by_name or model_info_by_idx. Both return basic information from the .models.json file along with description and default_vocoder (in case of tts_models). If not present, "description" will print "coming soon" and "default_vocder" will print "None". The .models.json file can be updated in future to add additional info in the description field.

Usage :

tts --model_info_by_name "<model_type>/<language>/<dataset>/<model_name>"
The model_info_by_name uses the name as it from the --list_models.
eg.

$ tts --model_info_by_name tts_models/tr/common-voice/glow-tts
> model type : tts_models
> language supported : tr
> dataset used : common-voice
> model name : glow-tts
> description : Turkish GlowTTS model using an unknown speaker from the Common-Voice dataset.
> default_vocoder : vocoder_models/tr/common-voice/hifigan

tts --model_info_by_idx "<model_type>/<model_query_idx>"
The model_query_idx uses the corresponding idx from --list_models.
eg.

$ tts --model_info_by_idx tts_models/3 
> model type : tts_models
> language supported : en
> dataset used : ljspeech
> model name : tacotron2-DDC
> description : Tacotron2 with Double Decoder Consistency.
> default_vocoder : vocoder_models/en/ljspeech/hifigan_v2

Then, we can query the vocoder model by name as follows,

$ tts --model_info_by_name vocoder_models/en/ljspeech/hifigan_v2
> model type : vocoder_models
> language supported : en
> dataset used : ljspeech
> model name : hifigan_v2
> description : HiFiGAN_v2 LJSpeech vocoder from https://arxiv.org/abs/2010.05646.

In case of out of index for model_info_by_idx,

$ tts --model_info_by_idx tts_models/45
model query idx exceeds the number of available models [32] 

In case of not in dict.key for model_info_by_name,

$ tts --model_info_by_name tts_models/tr/common-voice/flow-tts
> model flow-tts does not exist for tts_models/tr/common-voice.

[erogol]

Nice PR!!

I'd suggest to print the default vocoder for the tts models as well

[p0p4k]

Nice PR!!

I'd suggest to print the default vocoder for the tts models as well

Done. Please re-check the pull and the edited pull description.
Thanks.

[erogol]

@p0p4k there are some linter issues. Once you fix those we can merge this 🌟PR🌟

You can check the linter by running make lint locally

[p0p4k]

@erogol Right now the failing test seems to be really minor code issue (which can be ignored). I think I fixed the remaining lint stuff and added an extra edge case to catch not integer error when using index.
Thanks.

[erogol]

@p0p4k we are still getting out of linter

************* Module TTS.bin.synthesize
TTS/bin/synthesize.py:245:8: R0[9](https://github.com/coqui-ai/TTS/runs/6830909909?check_suite_focus=true#step:8:10)16: Too many boolean expressions in if statement (7/5) (too-many-boolean-expressions)
------------------------------------
Your code has been rated at [10](https://github.com/coqui-ai/TTS/runs/6830909909?check_suite_focus=true#step:8:11).00/10

[p0p4k]

@erogol There is a final lint error. Any idea how to fix this? Rest of the code from my PR is alright, I believe.

Run make lint
pylint tests TTS notebooks recipes
------------------------------------
Your code has been rated at 10.00/10
black tests TTS notebooks recipes --check
Skipping .ipynb files as Jupyter dependencies are not installed.
You can fix this by running ``pip install black[jupyter]``
would reformat TTS/bin/synthesize.py
would reformat TTS/utils/manage.py
Oh no! 💥 💔 💥
2 files would be reformatted, 297 files would be left unchanged.
make: *** [Makefile:47: lint] Error 1
Error: Process completed with exit code 2.

[erogol]

you need to run at the root path. If you have installed dev requirements then it should do it automatically

make style

[p0p4k]

you need to run at the root path. If you have installed dev requirements then it should do it automatically

make style

Thanks a lot for adding the final touches. I really could not get pylint working right on my Windows machine at home. Was gonna try to do stuff at my work Linux pc and saw that you fixed it already.
Ill be careful about following proper code pattern next time. Lots to learn, lots to learn..

[erogol]

No worries. Thanks for the ✨ PR.