![]() |
|
Hybrid VSviewer crash on windows 10 PC - Printable Version +- Selur's Little Message Board (https://forum.selur.net) +-- Forum: Hybrid - Support (https://forum.selur.net/forum-1.html) +--- Forum: Problems & Questions (https://forum.selur.net/forum-3.html) +--- Thread: Hybrid VSviewer crash on windows 10 PC (/thread-4256.html) Pages:
1
2
|
Hybrid VSviewer crash on windows 10 PC - MacNB - 08.11.2025 I just installed Hybrid using the installer on an old windows 10 pc (i7-3770K). I provided a input video file. in the cropping tab, I set the crop area and click the View icon. This plays the video in cropped form. Great. Then, I click on the Crop View check box and click the View Icon. The preview windows starts but before it can display anything, Vapoursynth crashes: Attaching hybrid debug output. This happens everytime irrespective of the input file. Also, after this, the Vapoursynth Tab (next to De-interlacetab) disappears. Is there anything I am suppose to do apart from running the Windows Hybrid Installer ? RE: Hybrid VSviewer crash on windows 10 PC - Selur - 08.11.2025 Quote: Is there anything I am suppose to do apart from running the Windows Hybrid Installer ?No. Works fine here. Just released a new release 2025.11.08.1, does it also happen with this one? Does this also happen if you try to start "C:\Program Files\Hybrid\64bit\Vapoursynth\vsViewer.exe" directly? Using https://www.dependencywalker.com/ (64bit) does is show any missing dependencies for vsViewer? (I suspect some dependencies are missing,..) Cu Selur RE: Hybrid VSviewer crash on windows 10 PC - MacNB - 08.11.2025 Not yet tried the version you just listed above. Running VSViewer on it own fails with an error about .vpy file not presumably because the script has not been generated. There's no vapoursynth tab under Filting tab. I restarted the PC but made no difference. Still no vapoursynth tab. I ran the dependency tools and it listed lots of missing files. it's log (*.dwi file attached) RE: Hybrid VSviewer crash on windows 10 PC - Selur - 08.11.2025 Quote:Running VSViewer on it own fails with an error about .vpy file not presumably because the script has not been generated.That would be okay, since it by default tries to open the last file known to it,... Quote: I ran the dependency tools and it listed lots of missing files.then you are probably missing some C++ runtime files, dwi files doesn't help me at all. Opening it here shows no info at all. RE: Hybrid VSviewer crash on windows 10 PC - MacNB - 08.11.2025 I uninstalled previous version and just installed the latest one. exactly the same issue. Once it crashes, the vapoursynth tab never comes back untill it's uninstalled and re-installed. Just ran the dependency tool again and this time i save the log as text file (attached). Does the Hybrid installer not install the required dependency files like C++ files ? I did not see anything in the downloads section about that dependency RE: Hybrid VSviewer crash on windows 10 PC - Selur - 08.11.2025 Quote: Does the Hybrid installer not install the required dependency files like C++ files ?Not files it assumes should be on any updated pc. Does installing: https://aka.ms/vs/17/release/vc_redist.x64.exe fix the problem for you? Cu Selur Ps.: But a good point, I should really adjust the installer not to work on Windows 10 systems nowadays. RE: Hybrid VSviewer crash on windows 10 PC - MacNB - 08.11.2025 No that vc_distrubution did not make a difference. It said that it was already install and offered me to repair which I did but made no difference. Looks like it's QT that does not work on Win 10 So which version of Hybrid works on Win 10 ? RE: Hybrid VSviewer crash on windows 10 PC - Selur - 08.11.2025 Quote: So which version of Hybrid works on Win 10 ?No, clue wasn't aware that newer Qt versions cause issues on Windows 10. API-MS-WIN-..dlls should either come with the OS or through one of the runtimes. Does your Windows have the latest update that was available for Windows 10 installed? Strange thing is that Hybrid itself does work since it is build with the save Qt version. ![]() Seems the missing dlls are part of ucrtbase.dll I tried reproducing the problem on my old (~10+year old laptop with an i5 4200u), but there I had no problem. It's running Windows 10 Pro 22H2 (19045.6396). (so not even the latest,...) It only has the "Microsoft Visual C++ 2015-2022 Redistributable (x64) - 14.44.35211" runtime installed. => Does "sfc /scannow" show any problems? Cu Selur RE: Hybrid VSviewer crash on windows 10 PC - MacNB - 08.11.2025 Thanks for checking. My Win 10: Edition Windows 10 Pro Version 22H2 Installed on 18/11/2020 OS Build 19045.6456 Processor Intel® Core i7-3770K CPU @ 3.50GHz 3.90 GHz Installed RAM 16.0 GB Storage 1.82 TB SSD Samsung SSD 870 EVO 2TB, 699 GB SSD Crucial_CT750MX300SSD1 Graphics Card Radeon RX 580 Series (8 GB) System Type 64-bit operating system, x64-based processor It is upto date as of this afternoon. I have signed for another year extended support from MS (like many people). C:\WINDOWS\system32>sfc /scannowIt found some issues and said it fixed them. In the log I can't anything related to those DLL's. After the repair, the problem still exist. This is shame as I wanted to try Hybrid on Windows as the Hybrid on the Mac seems very slow on my Mac Pro 5,1 (12 core Xeons) with 48GB RAM running Monterey. It's quite slow responding when clicking Preview button (just couple of filters like deinterlace & denoise). Most of time I have to close the preview window and click preview again to refresh. It's even slower exporting the same test file compared to VirtualDub2 on this Windows PC to carry out the same task (just crop, deinterlace and save as x264). VD2 takes less than ~15s where as the Mac would take over a minute ! RE: Hybrid VSviewer crash on windows 10 PC - Selur - 08.11.2025 I have no clue why the dlls are missing on your system. I also tried it on another Windows 10 system, and it also worked fine there. Is the c:\Windows\system32\ucrtbase.dll present on your system? From what I could find "Microsoft Visual C++ 2015-2022 Redistributable (x64) - 14.44.35211" should fix the problem. => no clue, maybe one of the other Windows 10 users has an idea. Cu Selur |