Add VapourSynth extra plugin path to Dockerfile to fix FFMS2 loading#1255
Open
Eauldane wants to merge 1 commit into
Open
Add VapourSynth extra plugin path to Dockerfile to fix FFMS2 loading#1255Eauldane wants to merge 1 commit into
Eauldane wants to merge 1 commit into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
With VapourSynth R74, the packaging system has changed. This means that plugins like FFMS2 aren't counted as loaded anymore - Arch still installs them at the same place, VapourSynth just needs an extra pointer to see them. This is just a quick fix that sets an ENV var during build that should solve that.
Tested and validated in a local transcode.