Update Readme to recommend same Openvino as Python tools #3138
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
danbev
approved these changes
May 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Today I noticed that Python was using OpenVINO 2024.6.0 in the script models/convert-whisper-to-openvino.py
I did a build with 2024.6.0 and - voila - OpenVINO versions were readable by whisper-cli
Prior to noticing this OpenVINO has never worked (as I've used 2023.0.0 as told) I also tried current a while ago - don't think that worked either
I also Added a pointer to the binary archives
I researched the issue and provided a close but wrong answer in #3105 - might be worthwhile creating a README.openvino once I've done test builds on other platforms