-
Notifications
You must be signed in to change notification settings - Fork 506
New issue
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
Input format of SherpaOnnxCreateOnlineStreamWithHotwords #1647
Comments
Please see sherpa-onnx/sherpa-onnx/csrc/online-recognizer.h Lines 155 to 164 in 08d7713
|
it's not working yet, can you check is my model config correct?
|
Sorry, the information you give is too limited. Could you post all of the config? |
By the way, I suggest that you first reproduce the example in our document and then try to add your own hotwords. |
ok, i'll try, thank you |
Hello again. I tryed to reproduce the example with those parameters:
First question is how can i detect that it working with hotwords? It recognizes phares "I LOVE YOU" and "HELLO WORLD" with or without setting hotwords. Dunno, maybe it's a matter of accent or pronunciation, english is not my native language. Second question is what am i doing wrong if i want to pass an abbreviation when creating online stream like "▁K F C", tokens for each separate characters is in tokens file. Third question is are you going to simplify the api for SherpaOnnxCreateOnlineStreamWithHotwords? I would assume that OnlineRecognizer does the same transformation with the hotwords file to bring it to the form "▁I ▁LOVE ▁YOU/▁HE LL O ▁WORLD" using passed vocab or tokens file. Is it possible to encapsulate this logic inside SherpaOnnxCreateOnlineStreamWithHotwords? thank you. |
Hi there. I'm trying to use SherpaOnnxCreateOnlineStreamWithHotwords from c# code like this
I tried to pass as hotwords string hotwords file contents("word0\nword1\n...) or hotwords file path
but it doesn't work. It ignores hotwords. Maybe marshaling error? What is input format of the parameter string hotwords?
Thank you.
The text was updated successfully, but these errors were encountered: