+- Selur's Little Message Board (https://forum.selur.net)
+-- Forum: Talk, Talk, Talk (https://forum.selur.net/forum-5.html)
+--- Forum: Small Talk (https://forum.selur.net/forum-7.html)
+--- Thread: Deoldify Vapoursynth filter (/thread-3595.html)
Pages:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
RE: Deoldify Vapoursynth filter - Selur - 16.02.2026
The headers and dll should be somwhere under Lib/site-packages,... but I'll do some testing after work.
Cu Selur
RE: Deoldify Vapoursynth filter - Dan64 - 16.02.2026
You're right, the dlib initialization script requires the user to have the CUDA SDK and cuDNN installed, while torch only needs to be installed in the same environment.
Replace the __init__.py file in the dlib folder with the attached version and clear the cache.
Key Changes applied in the attached script:
- Removed Static CUDA Paths: Eliminated hardcoded references to the NVIDIA CUDA Toolkit.
- Dynamic Torch Path Detection: Used torch.__file__ to locate the torch package and constructed the path to its lib folder.
- Windows-Specific Logic: Wrapped the DLL path modification in a check for os.name == 'nt' to ensure it only runs on Windows.
- Robust Error Handling: Maintained try-except blocks to prevent failures if torch is not installed or paths are inaccessible.
Installation Requirement:
Ensure that the torch package with CUDA 13.0 is installed in the same Python environment as dlib, so that the script can locate torch\lib correctly.
This modification allows dlib to dynamically use the CUDA DLLs bundled with torch, improving portability and reducing dependency on system-wide CUDA installations.
Dan
P.S.
Tested and working on my side.
RE: Deoldify Vapoursynth filter - Selur - 16.02.2026
I installed 'dlib-20.0.99-cp313-cp313-win_amd64.whl', then replaced the __init__.py, made sure to delete the __pycache__ folder inside Hybrid\64bit\Vapoursynth\Lib\site-packages\dlib and Hybrid\64bit\Vapoursynth\Lib\site-packages.
Sadly I get:
2026-02-16 18:46:54.861
Error on frame 0 request:
Traceback (most recent call last):
File "src/cython/vapoursynth.pyx", line 3222, in vapoursynth.publicFunction
File "src/cython/vapoursynth.pyx", line 3224, in vapoursynth.publicFunction
File "src/cython/vapoursynth.pyx", line 837, in vapoursynth.FuncData.__call__
File "F:\Hybrid\64bit\Vapoursynth\Lib\site-packages\torch\utils\_contextlib.py", line 124, in decorate_context
return func(*args, **kwargs)
File "F:\Hybrid\64bit\Vapoursynth\Lib\site-packages\vscodeformer\__init__.py", line 122, in inference
face_helper[local_index].get_face_landmarks_5(
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
only_center_face=only_center_face, resize=640, eye_dist_threshold=5
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "F:\Hybrid\64bit\Vapoursynth\Lib\site-packages\vscodeformer\face_restoration_helper.py", line 218, in get_face_landmarks_5
return self.get_face_landmarks_5_dlib(only_keep_largest)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^
File "F:\Hybrid\64bit\Vapoursynth\Lib\site-packages\vscodeformer\face_restoration_helper.py", line 182, in get_face_landmarks_5_dlib
det_faces = self.face_detector(self.input_img, scale)
RuntimeError: Error while calling cudaOccupancyMaxPotentialBlockSize(&num_blocks,&num_threads,K) in file D:\PProjects\dlib\dlib\cuda\cuda_utils.h:164. code: 209, reason: no kernel image is available for execution on the deviceCu Selur
RE: Deoldify Vapoursynth filter - Dan64 - 16.02.2026
But the output of: test_dlib_cuda_13.py ?
This is my env
build 1.4.0
colorama 0.4.6
dlib 20.0.99
filelock 3.20.0
fsspec 2025.12.0
Jinja2 3.1.6
MarkupSafe 2.1.5
mpmath 1.3.0
networkx 3.6.1
ninja 1.13.0
numpy 2.3.5
packaging 25.0
pefile 2024.8.26
pillow 12.0.0
pip 26.0.1
pyproject_hooks 1.2.0
setuptools 82.0.0
spatial_correlation_sampler 0.5.0
sympy 1.14.0
torch 2.10.0+cu130
torchvision 0.25.0+cu130
typing_extensions 4.15.0
wheel 0.46.3RE: Deoldify Vapoursynth filter - Selur - 17.02.2026
F:\Hybrid\64bit\Vapoursynth>python test_dlib_cuda_13.py
=== Verifica CUDA in dlib ===
DLIB_USE_CUDA: True
Numero GPU rilevate: 1
✅ CUDA ATTIVATO e GPU rilevata
✅ Dispositivo CUDA 0 impostato correttamente
✅ Modello CNN caricato con successo (conferma uso CUDA)
⚠️ Errore durante test CNN: Error while calling cudaOccupancyMaxPotentialBlockSize(&num_blocks,&num_threads,K) in file D:\PProjects\dlib\dlib\cuda\cuda_utils.h:164. code: 209, reason: no kernel image is available for execution on the device
✅ VERIFICA COMPLETATA: dlib usa CUDA sulla tua RTX 5070 TiCu Selur
RE: Deoldify Vapoursynth filter - Dan64 - 17.02.2026
I identified the problem: dlib's setup.py does not handle the CMAKE_ARGS variable for CUDA parameters correctly.
When the setup.py is unable to get the architecture, switch by default to "native" that in my case is sm_120, so the build that I sent you was able to run only on RTX50.
I changed the build script by using "CUDAARCHS=89;120" and now the problem is solved.
Install the dlib wheel with the command:
pip install dlib-20.0.99-cp313-cp313-win_amd64.whl --force-reinstallDan
RE: Deoldify Vapoursynth filter - Selur - 17.02.2026
Hurray! That version works fine!
Thanks!
Cu Selur
Ps.: once a. vsgan works with numpy2 https://github.com/rlaphoenix/VSGAN/issues/45 and HolyWus stuff works with TRT+FP16 https://github.com/HolyWu/vs-scunet/issues/8 I can release a Vapoursynth R73+Python3.13 version of the torch add-on
PPs.: vs-mlrt doesn't work either atm. since there isn't a nvidia-modelopt for 3.13 ¯\_(ツ)_/¯
RE: Deoldify Vapoursynth filter - Selur - 05.04.2026
Vapoursynth R74 is out.
see: https://github.com/vapoursynth/vapoursynth/releases/tag/R74
Quote:added the new _Range property which follows the H.273 numbering (0 and 1 switched) instead of the now deprecated _ColorRange property, all filters compiled against api version 4.2 and later must only use the _Range property=> you might want to check where you use '_ColorRange' and then use:
prop_name = '_Range' if core.version_number() >= 74 else '_ColorRange'https://github.com/dan64/vs-deoldify/blob/39eae9f838e6857cf9479d8a90ae65a6fff91c2f/vsdeoldify/havc_utils.py#L88
Cu Selur
RE: Deoldify Vapoursynth filter - Dan64 - 05.04.2026
I will check.
Thanks,
Dan
RE: Deoldify Vapoursynth filter - Selur - 05.04.2026
small addition:
DeprecationWarning: core.version_number() is deprecated, use core.core_version.release_major!