Repository navigation
License confirmation for bundling sherpa-onnx-paraformer-zh-small-2024-03-09 in a closed-source commercial Android app #3900
Replies: 1 comment
|
Thanks for providing the exact hashes. There is a provenance detail to resolve before giving a model-specific answer:
For the intended use, please describe it consistently as redistribution of the model and token files inside the APK. Running entirely offline and not offering a separate model download are useful product details, but users still receive copies of the bundled files. Could you provide the exact download URL/revision and the export's original README, license/NOTICE files and conversion provenance available when you obtained it? Please share documentation only, not private app materials or model weights. This will let the original model licensor and export author confirm the applicable terms and any original notices or conversion acknowledgements for these exact artifacts, instead of guessing an attribution text from a similar model name. This reply is a source/provenance clarification, not a new license grant or legal approval of commercial distribution. We are leaving the question open and unanswered pending that artifact-specific confirmation. |
Uh oh!
There was an error while loading. Please reload this page.
Hello FunASR team,
We are Sichuan Xiaorong Technology Co., Ltd. (a registered company in Chengdu, China). We are preparing an Android app ("说写助手", package
cn.com.scxrkj.speechwriter) for release on Chinese app stores. The app performs on-device offline speech recognition: audio never leaves the phone, and we do not redistribute model files to any third party.We bundle the following model, obtained through the sherpa-onnx export:
sherpa-onnx-paraformer-zh-small-2024-03-09damo/speech_paraformer_asr_nat-zh-cn-16k-common-vocab8358model.int8.onnx3ef6c19369b912f7caf3cef8e545c5ccd1a33d9d7ec792a46668dc41c4b229ectokens.txt4b2d964e18b9cf139b473003b6698fb2ed9a2a5ec55b93daa677b28f578897aaThese hashes match the ones listed in k2-fsa/sherpa-onnx issue #3930, so our files are byte-identical to those.
How we use it
What we have determined so far
Our three questions
If this is not the right place to ask, please point us to the responsible party.
Happy to provide any additional materials (app description, distribution model, screenshots of the in-app license page).
Thank you.
Best regards,
Li Luwei
Sichuan Xiaorong Technology Co., Ltd.
13880802105@139.com
All reactions