That seems strange.
Hybrid uses:
to check whether avx2 is supported, which seems to work fine for all my systems.
Hybrid does this check on each start.
Even if no AVX2 support was detected Vapoursynth should still work.
=> try deinstalling Hybrid before installing the new version, my guess is the switch from Vapoursynth R72 to R73 might cause problems if their files are mixed.
Cu Selur
Hybrid uses:
bool HybridMainWindow::cpuSupportsAVX2() const
{
unsigned int ebx = 0;
#ifdef _MSC_VER
int cpuInfo[4];
__cpuid(cpuInfo, 0);
if (cpuInfo[0] < 7)
return false;
__cpuidex(cpuInfo, 7, 0);
ebx = cpuInfo[1];
#elif Q_OS_WIN
unsigned int eax, ecx, edx;
unsigned int cpuInfo[4];
__cpuid(0, eax, ebx, ecx, edx);
if (eax < 7)
return false;
__cpuid_count(7, 0, eax, ebx, ecx, edx);
#endif
// Bit 5 of EBX in CPUID leaf 7 subleaf 0 indicates AVX2 support
return (ebx & (1 << 5)) != 0;
}Hybrid does this check on each start.
Even if no AVX2 support was detected Vapoursynth should still work.
=> try deinstalling Hybrid before installing the new version, my guess is the switch from Vapoursynth R72 to R73 might cause problems if their files are mixed.
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.

