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

Add custom location for OpenImageIO and FFMpeg #3935

Closed
antirotor opened this issue Oct 4, 2022 · 1 comment · Fixed by #3982
Closed

Add custom location for OpenImageIO and FFMpeg #3935

antirotor opened this issue Oct 4, 2022 · 1 comment · Fixed by #3982
Assignees
Labels
type: feature Larger, user affecting changes and completely new things

Comments

@antirotor
Copy link
Member

antirotor commented Oct 4, 2022

Feature

We should add option to set custom path OpenImageIO binaries and ffmpeg. This would allow adventurous TDs to use their own custom builds.

Proposal

Add option to System Setttings to set those paths. If set, use those.

Question: Do we need it per project?

Related #3858

[cuID:]

@antirotor antirotor added the type: feature Larger, user affecting changes and completely new things label Oct 4, 2022
@m-u-r-p-h-y
Copy link
Member

I was testing ffmpeg 5 and there were a lot of issues with some deprecated arguments we use with our older build, so maybe per project toggle to use custom paths would allow us not to break running production when testing these custom builds..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature Larger, user affecting changes and completely new things
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants