Hybrid VSviewer crash on windows 10/11 PC

[MacNB]

Logs from crashes from Sandy Bridge based Laptop and Ivy Bridge based desktop.
Both show vapoursynth.dll crashing at the same offset.

  vapoursynth-crash.zip (Size: 3,16 KB / Downloads: 12)

[Selur]

On my old Laptop with Windows 10 (19045.6456 <- same you mentioned) and a i5-4200U CPU Hybrid and vsViewer works fine.
Here another user had the problem that Hybrid didn't work because his Windows version was too old.
Since it's the vapoursynth.dll that is crashing, it probably isn't a problem with Hybrid itself.
Looking at the changelog of 2025.07.27.1, first thing it states is "Vapoursynth: changed to Vapoursynth R72".
So maybe replacing the Vapoursynth files with files from an older portable Vapoursynth version helps,...
https://github.com/vapoursynth/vapoursynth/releases
afaik there should be no avx2 requirement for Vapoursynth with R72 (not sure about R73 which I will switch to at the end of the year).
(Nope, R73 is the final Windows 7 release, so that probably isn't the issue either)

Cu Selur

[MacNB]

Your laptop is 4th Gen Haswell so it's one gen later than my desktop.

As I said I have latest Windows 10 & 11 and vapoursynth fails on both so it's not old version of Windows.

The portable version of vapoursynth has different folder and files structure and does not contain vapoursynth.dll.

2025.07.21.1 change log says "Vapoursynth: make sure Hybrid comes with a vsViewer.config on Windows"
What's that about ?

Also when you "package up" vapoursynth for Hybrid, do you build it from scratch and add the binaries to Hybrid ?

Which version of vapoursynth was used with Hybrid version 2025.05.18.2 ?

[Selur]

Your laptop is 4th Gen Haswell so it's one gen later than my desktop.

That's the oldest cpu I can test with.

[@uote]As I said I have latest Windows 10 & 11 and vapoursynth fails on both so it's not old version of Windows.[/quote]
good.

The portable version of vapoursynth has different folder and files structure and does not contain vapoursynth.dll.

The additional folder in Hybrids Vapoursynth are from the portable Python version and vsViewers Qt dependencies.

2025.07.21.1 change log says "Vapoursynth: make sure Hybrid comes with a vsViewer.config on Windows"
What's that about ?

Without it vsViewer didn't start with the right environment, but did start.

Also when you "package up" vapoursynth for Hybrid, do you build it from scratch and add the binaries to Hybrid ?

What I did was:

• created a new empy Vapoursynth-folder
  
• downloaded 'Windows embeddable package (64-bit)' of Python 3.12 from https://www.python.org/
  
• extracted the Python download into the download into the 'Vapoursynth'-folder
  
• downloaded 'VapourSynth64-Portable-R72.7z' from https://github.com/vapoursynth/vapoursynth/releases
  
• extracted the Vapoursynth portable download into the 'Vapoursynth'-folder
  
• downloaded get-pip.py from https://bootstrap.pypa.io/get-pip.py and save it into the 'Vapoursynth'-folder
  
• opened a 'Windows Command Prompt'-window and navigate into the 'Vaporusynth'-folder
  
• installed pip by calling: pyhton get-pip.py
  
• opened the python312._pth in a text editor and added the following to lines above anything else in that file and saved the file
  
  Scripts
Lib\site-packages

Cu Selur

[MacNB]

Thanks for the steps you take to get vapoursynth.

After you finish editing the python312._pth file, do you simply copy the vapoursynth folder into Hybrid'd folder structure ?

[Selur]

Yes, I also add vsViewer + it's dependencies into the Vapoursynth-folder and copy it into Hybrid/64bit (which has no Vapoursynth folder at that point)

Cu Selur

Ps.: you could also download an older Hybrid version and replace the Vapoursynth-folder in the current version with the on from the older version.

[MacNB]

Yes, I also add vsViewer + it's dependencies into the Vapoursynth-folder and copy it into Hybrid/64bit (which has no Vapoursynth folder at that point)

From where are do you download the vsViewer and it's dependencies ?

Ps.: you could also download an older Hybrid version and replace the Vapoursynth folder from there with the current for testing,...

OK I just did that:

• Uninstalled the latest Hybrid.
  
• Installed the older Hybrid version 2025.05.18.2
  
• Copied the vapoursynth folder to vapoursynth-V70 folder (I think that's the version used in that older Hybrid).
  
• Uninstalled the Hybrid 2025.05.18.2
  
• Installed latest Hybrid
  
• Replaced the vapoursynth folder with vapoursynth-V70
  
• Renamed vapoursynth-V70 to vapoursynth
  

Now there are no crashes.

So I have a "Frankenstein" Hybrid.

Obviously I am missing features and bug fixes in vapoursynth.

[Selur]

From where are do you download the vsViewer and it's dependencies ?

I don't download them, I copy them using windeployqt from the Qt SDK I used to build the vsViewer binary.
i.e.

c:\qt\6.10.1\msvc2022_64\bin\windeployqt.exe --no-opengl-sw --force --no-system-d3d-compiler --no-quick-import --no-translations  --release "F:\Vapoursynth\vsViewer.exe"

Cu Selur

[MacNB]

I don't download them, I copy them using windeployqt from the Qt SDK I used to build the vsViewer binary.

Ah I see. That's beyond me....Miracles I can perform...but the Impossibles are beyond me

So if you "build the vsViewer binary", with those flags, is there possibility that flags may have an affect on how the binary runs on 2nd & 3rd Gen Intel Core CPU's or certain platforms as that's where the problem is ?

[Selur]

I doubt it, haven't really changed much there aside from:
a. updating Qt
b. updating Vapoursynth interface files. (needed to communicate with Vapoursynth)
=> I think it's a Vapoursynth incompatibility, not a vsViewer compatibility problem.

Cu Selur