DO you think we should create a dev function. It would
a) get huggingface JSON
b) generate JSON using createindex.py -
c) merge both JSON and save to the repo. Remove any other json in this repo
sherpa-onnx then would getVoices with no token or model path - with ALL data in the local JSON. Actually speeding things up as the end user doesnt download this file..
rename local download path to not ~/mms but ~/sherpaonnx or something more relevant
I think a user should be able to provide their own onnx path - and then settings for this generation too..
I have a feeling it may not work great. In part because my createindex.py was broken. It was calculating the language codes correctly of each model etc.
@willwade
I added your comment in the PR so it would not get lost.
DO you think we should create a dev function. It would a) get huggingface JSON b) generate JSON using createindex.py - c) merge both JSON and save to the repo. Remove any other json in this repo
sherpa-onnx then would getVoices with no token or model path - with ALL data in the local JSON. Actually speeding things up as the end user doesnt download this file.. rename local download path to not ~/mms but ~/sherpaonnx or something more relevant I think a user should be able to provide their own onnx path - and then settings for this generation too..
I have a feeling it may not work great. In part because my createindex.py was broken. It was calculating the language codes correctly of each model etc.
@willwade I added your comment in the PR so it would not get lost.