[GUIDE] VapourSynth + QTGMC Deinterlace + Hybrid UI FAQ for macOS

[Selur]

A few notes to the package you build:

Why do you add the 'Scripts' to your package, when Hybrid already comes with the scripts? (Hybrid.app/Contents/MacOS/vsscripts)
Doesn't seem like you added additional script aside from the scripts from https://github.com/Selur/VapoursynthScriptsInHybrid so there should be no need for these, especially since Hybrid by default automatically loads the 'vsscripts' it comes with:

# Import scripts folder
scriptPath = '/Users/selur/workspace/Hybrid/Hybrid.app/Contents/MacOS/vsscripts'
sys.path.append(os.path.abspath(scriptPath))

(snippet of a generated Vapoursynth script where Hybrid uses one of the scripts)

Also when copying the dylib files from your package to /Library/Frameworks/VapourSynth.framework/lib/vapoursynth and call 'sudo spctl --master-disable'
I get the following popups:

• “libautocrop.dylib” is damaged and can’t be opened.

• “libdpid.dylib” is damaged and can’t be opened.

• “libdecross.dylib” is damaged and can’t be opened.

these seem to be all broken.
So they should either be removed or replaced with working versions.
Neither 'libautocrop' nor 'libdpid' is used by Hybrid, so they should not there.

You also might want to investigate if there's a better way to allow those dylib files since using 'sudo spctl --master-disable' on a productive machine seems like a bad idea.

Problem: Filtering -> ColorMatrix don't works.
Problem fix: Use only Filtering -> VapourSynth -> Color -> ColorMatrix

'Filtering -> ColorMatrix' works fine here, it simply should not be used in combination with Vapoursynth unless you know what effect this has, which you clearly don't.

THIS IS A RECOMMENDED UPDATE

Not by me, since it's based on a build that was meant for testing,... but what do I care?

Cu Selur