We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
A bug happened!
No response
options: { "path": "C:\\test.mp3-20240711T045511Z-001\\test.mp3", "lang": "en", "verbose": false, "n_threads": 5, "init_prompt": "", "temperature": 0.4, "translate": null, "max_text_ctx": null, "word_timestamps": null, "max_sentence_len": null } Caused by: Failed to create ONNX Runtime environment: D:\a\ort-artifacts-staging\ort-artifacts-staging\onnxruntime\onnxruntime\core\platform\windows\logging\etw_sink.cc:142 onnxruntime::logging::EtwRegistrationManager::LazyInitialize ETW registration failed. Logging will be broken: -2147024882 Location: C:\Users\runneradmin/.cargo\registry\src\index.crates.io-6f17d22bba15001f\pyannote-rs-0.2.2\src\session.rs:7:19 Location: core\src\transcribe.rs:145:108 App Version: vibe 2.4.0 Commit Hash: 9111fcd0685666727039182e8904634f298e3825 Arch: x86_64 Platform: windows Kernel Version: 10.0.22631 OS: windows OS Version: 10.0.22631 Cuda Version: n/a Models: ggml-medium.bin Default Model: "C:\\Users\\test\\AppData\\Local\\github.com.thewh1teagle.vibe\\ggml-medium.bin" Cargo features: opencl { "avx": { "enabled": true, "support": true }, "avx2": { "enabled": true, "support": true }, "f16c": { "enabled": true, "support": true }, "fma": { "enabled": true, "support": true } }
The text was updated successfully, but these errors were encountered:
Hey! Thanks for reporting. Does it happens only when you hit transcribe with diarization or you can't use the app at all?
This issue might be related: microsoft/onnxruntime#21566
Sorry, something went wrong.
No branches or pull requests
What happened?
A bug happened!
Steps to reproduce
What OS are you seeing the problem on?
No response
Relevant log output
The text was updated successfully, but these errors were encountered: