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
Plan for the next release #24
Comments
I can probably help with building for more platforms, including Windows and different flavors of ARM. One approach is to use cross-compiler images from dockcross. Let me know if you would consider merging a PR using GitHub actions to automate building/uploading Python wheels. |
I checked github actions and didn't find critical advantages over travis. You can try if you want of course. |
I made some progress on getting a Windows build out. I'm currently blocked on some errors when compiling OpenFST (opened this issue: kkm000/openfst#25). This is much more complicated than expected :) |
@dtreskunov Thank you. For Win build I really consider mingw with anaconda, that will be much easier than stock python with VS. I think anaconda build should be enough. We don't have to spend much time on it. |
Also, as far as I know @kkm000 uses very recent openfst, you might have better chances with openfst-1.6.7 instead of 1.7 something he is using. |
Thanks. I really think I'm very close to getting it working. I got the
Python wheels compiled with VS 2017, however, when doing `import vosk`, I
was getting an `ImportError` saying DLL could not be loaded. That's when I
found out that VS 2015 must be used to build Python extensions. However, it
won't build OpenFST :)
I'll try 1.6.7 when I get a chance.
…On Sun, Feb 16, 2020, 12:37 Nickolay V. Shmyrev ***@***.***> wrote:
Also, as far as I know @kkm000 <https://github.com/kkm000> uses very
recent openfst, you might have better chances with openfst-1.6.7 instead of
1.7 something he is using.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#24?email_source=notifications&email_token=AA2RDSH5ZBALEOQVT3JTXG3RDGPX5A5CNFSM4KNK5IRKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEL4RQAA#issuecomment-586749952>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA2RDSEL7JNXXQHGIOEET4LRDGPX5ANCNFSM4KNK5IRA>
.
|
@dtreskunov ah, I see. Given openfst uses C++11, no chance we can make it working. VS14 simply doesn't support c++11 well enough. https://docs.microsoft.com/en-us/cpp/overview/visual-cpp-language-conformance?view=vs-2019 Consider mingw and anaconda. |
I was able to fix it thanks to this article. It turns out that the The resulting I would appreciate it if you could test it: vosk-0.3.1_dtreskunov_183_ga8b2c22-cp38-cp38-win_amd64.whl.zip I'm not sure why it works. It's built using Visual Studio 15 2017, despite the requirement to use Visual Studio 14 2015. I'm going to clean up the scripts a bit and will send a PR soon. |
@nshmyrev I can do |
@bedapudi6788 that would be great! |
@nshmyrev this is my idea of "pythonic" api. import vosk
# print available models
print(vosk.list_models())
# auto downloads the model if not found in local
asr = vosk.load("en-us")
# word_list is optional
# if stream=True, will return iterator for partial results
# if stream=False will return final result
# default stream = False
result = asr.recognize('wav_file_path', word_list, stream=True) let me know if this is ok or any changes required. |
@bedapudi6788 I have created a separate issue about this: #31, please check |
Help is very much needed on all this, any contribution will be appreciated.
The text was updated successfully, but these errors were encountered: