video temp file not created

[sharkmonkey0]

Version: 2026.10.09.1

Been trying to get Hybrid setup and working on Mint 22.3, I got the application built from HybridDeploy with the Vapoursynth plugins and it runs, but when I try to process a video it fails at creation of the .265 temp file.

-> 2026-10-30@16_51_38_0710_07_video crashed: ERROR: /tmp/2026-10-30@16_51_38_0710/2026-10-30@16_51_38_0710_07.265 was not created! Aborting '2026-10-30@16_51_38_0710_07_video' due to: ERROR: /tmp/2026-10-30@16_51_38_0710/2026-10-30@16_51_38_0710_07.265 was not created! 2026-10-30@16_51_38_0710_02_audio finished after 00:03:36.997

It seems like when it builds the x265 command the --input file string is empty, is anyone else having this problem?

x265 --frame-threads 5 --wpp --no-pmode --no-pme --pools 32 --log-level 2 --input - --fps 24000/1001 --output-depth 10 --y4m --profile main10 --high-tier --min-cu-size 8 --ctu 64 --qg-size 32 --no-opt-cu-delta-qp --tu-intra-depth 1 --tu-inter-depth 1 --limit-tu 0 --max-tu-size 32 --no-hme --me hex --subme 2 --merange 57 --no-analyze-src-pics --limit-modes --no-rect --no-amp --max-merge 3 --no-early-skip --rskip 1 --no-mcstf --no-temporal-mvp --rdpenalty 0 --no-tskip --strong-intra-smoothing --no-constrained-intra --no-open-gop --gop-lookahead 0 --scenecut 40 --scenecut-bias 5 --scenecut-aware-qp 0 --no-hist-scenecut --opt-ref-list-length-pps --keyint 250 --min-keyint 0 --max-ausize-factor 1 --radl 0 --bframes 4 --no-weightb --no-b-intra --bframe-bias 0 --b-adapt 2 --no-b-pyramid --ref 3 --weightp --rc-lookahead 20 --slices 1 --lookahead-threads 0 --lookahead-slices 0 --qpstep 4 --qpmin 0 --qpmax 69 --qblur 0.50 --cplxblur 20.0 --crf 24.00 --no-opt-qp-pps --no-rc-grain --cbqpoffs -2 --crqpoffs -2 --ipratio 1.40 --pbratio 1.30 --nr-intra 0 --nr-inter 0 --qpfile GENERATED_QP_FILE --limit-refs 0 --rd 2 --no-fast-intra --no-ssim-rd --no-rd-refine --psy-rd 2.50 --rdoq-level 1 --psy-rdoq 2.50 --signhide --no-splitrd-skip --qcomp 0.60 --qp-adaptation-range 1 --no-aq-motion --aq-mode 0 --no-hevc-aq --no-const-vbv --vbv-maxrate 0 --vbv-bufsize 0 --vbv-init 0.90 --vbv-end 0.000 --min-vbv-fullness 50.00 --max-vbv-fullness 80.00 --no-hrd --aud --no-info --no-idr-recovery-sei --no-deblock --repeat-headers --log2-max-poc-lsb 8 --no-fades --no-psnr --no-ssim --no-interlace --range limited --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --no-single-sei --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(40000000,50)" --hdr --no-hdr-opt --sar 1:1 --output "/tmp/Fifth Element_t00.265"

I can get this file to process as expected in Hybrid in Windows.

Any help is appreciated!

[Selur]

Looking at the debug ouput, the error ist:

VSPipe : Failed to initialize VSScript. VSScript reported error: Failed to initialize the VapourSynth Python module for VSScript use.

My guess is that this is related to the setup of the system and a change in the Vapoursynth version required to run Hybrid.
I assume this is fixed when using the AppImage, which ships the Vapoursynth&Co environment with it. (no installation of Vapoursynth or it's dependencies or adjusting of the misc.ini should be needed)

Try using latest dev (currently: Hybrid-2026.10.29.1-x86_64_oldGlibc.AppImage).

Let me know whether it works with that version.

Cu Selur

[sharkmonkey0]

I get the same result with Hybrid-2026.10.29.1-x86_64_oldGlibc.AppImage:

vspipe failed with exitCode: 1
-> 2026-10-31@13_46_20_9810_07_video crashed: vspipe, exitCode: 1
Aborting '2026-10-31@13_46_20_9810_07_video' due to: vspipe, exitCode: 1

and:
2026.10.31 - 13:57:13_Linux Mint 22.3 (64bit)_2026.10.31.1 - level 9: analyseOutput of vspipe: Failed to initialize VSScript. VSScript reported error: Failed to initialize the VapourSynth Python module for VSScript use.

If I disable using KNLMeansCL it processes the video as expected.

[Selur]

Since you didn't post a debug output from that version, check the Tools settings from KNLMeansCL. (scroll to the right)
I should offer multiple filters that can be used to provide NLMeans.
Potentially:

• knlm
  
• nlm_ispc
  
• knlmvk
  
• vszipcl
  
• vszipcu
  

Do all of them crash for you?
I build Hybrid for Linux on Ubuntu 24.04 and Ubuntu 26.04 and on both the KNLMeansCL works fine for me.

VSPipe : Failed to initialize VSScript. VSScript reported error: Failed to initialize the VapourSynth Python module for VSScript use.

normally does indicate that something with the Vapoursynth setup is broken, but that should not be caused by a single filter, but should be a general problem.

=> share a debug output from the dev version. Also check whether the Vapoursynth Preview works. (share a debug output if it fails)

Cu Selur

[sharkmonkey0]

Yes they all crash for me using the dev version, debug attached.

I prefer to use KNLMeansCL since my AMD GPU (at least in windows) handles the denoising well. I tried other filters, seems anything I pick in vapoursynth crashes it.

Vapoursynth Preview also does not work, the log is:

2026-10-31 22:25:24.391
Failed to get VSScript API!
Library found in /tmp/.mount_Hybridiladkk/usr/vapoursynth/python/lib/python3.14/site-packages/vapoursynth/libvsscript.so but failed to get VSScript API!
Failed to initialize the VapourSynth Python module for VSScript use.
Library found in /tmp/.mount_Hybridiladkk/usr/vapoursynth/python/lib/python3.14/site-packages/vapoursynth/libvsscript.so but failed to get VSScript API!
Failed to initialize the VapourSynth Python module for VSScript use.
Library found in /tmp/.mount_Hybridiladkk/usr/vapoursynth/python/lib/python3.14/site-packages/vapoursynth/libvsscript.so but failed to get VSScript API!
2026-10-31 22:25:24.446
Failed to get VSScript API!
Failed to create VSScript handle!

[Selur]

What do you get if you open a terminal and call:

echo $LD_LIBRARY_PATH

and

ls /usr/local/lib/libvapoursynth*

Does it work if you start Hybrid with:

env -u LD_LIBRARY_PATH ./Hybrid-2026.10.31.1-x86_64_oldGlibc.AppImage

, from a Terminal next to the Hybrid AppImage?

Cu Selur

Ps.: I'm also trying to add a workaround for this to the AppImage. => try Hybrid-2026.11.01.1-x86_64_oldGlibc.AppImage (it should overwrite LD_LIBRARY_PATH)
PPs.: In case that also fails with the same error, please additionally share what you get when calling:

echo $LD_LIBRARY_PATH and env | grep -i -E "preload|python

in a terminal.

[sharkmonkey0]

ben@DESKTOPR3:~$ echo $LD_LIBRARY_PATH /home/ben/opt/vapoursynth/lib

There is nothing in /usr/local/lib/ with vapoursynth

This gives the same vspipe crash

env -u LD_LIBRARY_PATH ./Hybrid-2026.10.31.1-x86_64_oldGlibc.AppImage

This returns nothing (I assumed there was supposed to be a trailing ")

echo $LD_LIBRARY_PATH and env | grep -i -E "preload|python

I noticed this in the debug, maybe I'm missing something in order to get opencl working with my AMD gpu, though I don't think this explains why it doesn't work when I use other non-opencl vapoursynth filters:

2026.11.01 - 08:16:42_Linux Mint 22.3 (64bit)_2026.10.31.1 - level 9: Main call started,.. 2026.11.01 - 08:16:42_Linux Mint 22.3 (64bit)_2026.10.31.1 - level 9: VSPipe : Critical: Failed to load /tmp/.mount_HybridceDOaE/usr/vapoursynth/python/lib/python3.14/site-packages/vapoursynth/plugins/vszipcu/libvszipcu.so. Error given: libcuda.so.1: cannot open shared object file: No such file or directory 2026.11.01 - 08:18:21_Linux Mint 22.3 (64bit)_2026.10.31.1 - level 9: VSPipe : 2026.11.01 - 08:18:22_Linux Mint 22.3 (64bit)_2026.10.31.1 - level 9: VSPipe : Script evaluation failed: Python exception: knlm.KNLMeansCL: no compatible opencl platforms available! Traceback (most recent call last):   File "vapoursynth.pyx", line 4634, in vapoursynth._vpy_evaluate   File "vapoursynth.pyx", line 4635, in vapoursynth._vpy_evaluate   File "/tmp/2026-11-01@08_16_34_4110/encodingTempSynthSkript_2026-11-01@08_16_34_4110_0.vpy", line 36, in <module>     clip = core.knlm.KNLMeansCL(clip, a=1, s=8, device_id=0)   File "vapoursynth.pyx", line 4325, in vapoursynth.Function.__call__ vapoursynth.Error: knlm.KNLMeansCL: no compatible opencl platforms available! 2026.11.01 - 08:18:22_Linux Mint 22.3 (64bit)_2026.10.31.1 - level 9: x265 output: x265 [error]: unable to open input file <-> 2026.11.01 - 08:18:22_Linux Mint 22.3 (64bit)_2026.10.31.1 - level 9: 2026-11-01@08_16_34_4110_04_video ### /home/ben/Videos/Encoded/Fifth Element_t00.mkv ### x265 [error]: unable to open input file <-> 2026.11.01 - 08:18:22_Linux Mint 22.3 (64bit)_2026.10.31.1 - level 9: 2026-11-01@08_16_34_4110_04_video ### /home/ben/Videos/Encoded/Fifth Element_t00.mkv ### vspipe failed with exitCode: 1

[Selur]

1. About the libcuda message:

short: The libcuda.so.1 message is harmless, that's only the NVIDIA variant vszipcu.

longer:
The log about the libcuda.so line comes from VapourSynth loading every plugin at startup.
libvszipcu.so needs libcuda.so.1, which comes with the NVIDIA driver and can't be included in the AppImage.
On a machine without that driver the load fails and VapourSynth logs Critical: Failed to load …libvszipcu.so … libcuda.so.1. It then carries on without that plugin.
(I'll look into hiding such messages in the future.)

2. The real problem is the failing of "knlm".

Python exception: knlm.KNLMeansCL: no compatible opencl platforms available!

• Please try Hybrid-2026.11.01.1-x86_64_oldGlibc.AppImage started normally (without env -u). It should handle that by itself now. Test with a non-OpenCL filter first (e.g. NLMeans with tools vszip) and share a debug output if it still fails.
  
• KNLMeansCL needs an OpenCL driver for your AMD GPU, which on Linux isn't installed by default (on Windows the AMD driver ships it). Check with clinfo (sudo apt install clinfo). If it lists no platform, install one (e.g. "sudo apt install mesa-opencl-icd") and start with RUSTICL_ENABLE=radeonsi set, or use AMD's ROCm OpenCL. Once clinfo shows your GPU, restart Hybrid.
  
• Alternative without OpenCL: knlmvk (Vulkan, works with the normal Mesa RADV driver) or vszip (CPU).
  

My guess is you atm. use Mesa's old Clover driver (mesa-opencl-icd). It lists the Radeon as a GPU, but supports only OpenCL 1.1 and has no image support and Hybrid doesn't check that atm.
=> I'll also look into Hybrid better detection whether a newer opencl is available. (klmn and vszipcl both require OpenCL 1.2 or newer)

Cu Selur

[Selur]

I uploaded Hybrid-2026.11.01.2-x86_64_oldGlibc.AppImage which should check for Vulkan and OpenCL version and image support, and thus hopefully hide the not usable filters on your system. (=> you might want to install current Vulkan and/or OpenCL drivers for your GPU on your system, otherwise KNLMenasCL will only work through the cpu)


Cu Selur

[sharkmonkey0]

I didn't see NLMeans as an option, but I switched to SMDegrain and that seems to run through vspipe as expected.

Hybrid-2026.11.01.1-x86_64_oldGlibc.AppImage still shows me KNLMeansCL as an option to choose, but vspipe still crashes trying to use it.

I already had clinfo, installed the mesa icd, and added the rusticl.

I'm unsure which version number exactly is important, so I attached the clinfo. I see both OpenCL 3.0, and 1.2 in there. vulkaninfo shows a couple different version numbers.

I may have to try ROCm at this point, since I don't seem to be getting anywhere this way and I don't know what else I would need to install/upgrade.