Skip to content
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

OpenVINO bloat #285

Open
tadejsv opened this issue Sep 25, 2024 · 3 comments
Open

OpenVINO bloat #285

tadejsv opened this issue Sep 25, 2024 · 3 comments
Labels

Comments

@tadejsv
Copy link
Member

tadejsv commented Sep 25, 2024

Comment:

Is it really necessary to bundle in OpenVINO? It significantly increases the size of this package, for a feature that 99.99% of the users will not need.

@hmaarrfk
Copy link
Contributor

hmm, this is a fair question.

@ilya-lavrenov can you help us understand all the different intel solutions:

  • OpenVINO
  • VAAPI
  • Intel Quick Sync

@ilya-lavrenov I know ffmpeg supports many "hot" plugins. Can we have openvino as a "soft" dependency similar to how the cuda dependency will "gracefully fail" if cuda isn't installed on the end user system?

@hmaarrfk
Copy link
Contributor

Regarding:

for a feature that 99.99% of the users will not need.

Much of FFMPEG's strength comes from its great flexibility. Each users likely only uses 1-2 features, but FFMPEG makes them all interoperable.

@hmaarrfk
Copy link
Contributor

hmaarrfk commented Oct 3, 2024

It seems that compiling with openvino makes it a hard dependency:

conda uninstall --force libopenvino --offline --yes
ffmpeg -hide_banner -f lavfi -i nullsrc=s=256x256:d=8 -vcodec libopenh264 -f null -
ffmpeg: error while loading shared libraries: libopenvino_c.so.2440: cannot open shared object file: No such file or directory

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants