![]() |
|
Deoldify Vapoursynth filter - Printable Version +- 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
|
RE: Deoldify Vapoursynth filter - Selur - 27.05.2026 removed encode_mode and updated Hybrid_havc_test Cu Selur RE: Deoldify Vapoursynth filter - Dan64 - 28.05.2026 Hello Selur, using the R74 I compared the encoding speed of a 10min clip, using "core.num_threads = 1" vs "core.num_threads = 0" (no limitation on threads count). Using only 1 thread I obtained a speed of about 5.28fps, while with no threads limitation I obtained a encoding speed of about 5.62 (see picture) So in this case, using only 1 thread the speed decreased only of about 6%. But while in R74 the correct thread management is performed automatically, in R76 now this management is left to the user, that need to guess when is necessary or not. I hope there are no further "improvements" of this kind in the new R76, which have not yet been discovered. Dan P.S. I'm going to the rename the github project "vs-deoldify" in "vs-havc" and to rename the package "vsdeoldify" in "vshavc", in the next days I will provide you the preview of "vshavc" package RE: Deoldify Vapoursynth filter - Selur - 28.05.2026 Quote:Setting to a value less than one makes it default to the number of hardware threads.source: https://amusementclub.github.io/doc3/pythonreference.html#Core.num_threads Quote: I'm going to the rename the github project "vs-deoldify" in "vs-havc" and to rename the package "vsdeoldify" in "vshavc", in the next days I will provide you the preview of "vshavc" packageI'll adjust Hybrid accordingly when the time comes. ![]() Cu Selur RE: Deoldify Vapoursynth filter - Selur - 28.05.2026 I'm uploading a new torch add-on and Hybrid dev, which should be online in ~1 1/2 hours. Cu Selur RE: Deoldify Vapoursynth filter - Dan64 - 28.05.2026 Hello Selur, I renamed the project as: vs-havc no need on your side to update to version v5.8.1 I attached the new RC8 with the change of package's name. The simplest way to move to the new package's name is to manually rename in you packages library the folder "vs-deoldify" in "vs-havc" and to rename the subfolder "vsdeoldify" in "vshavc" and then to overwrite the folder "vshavc" with the one included in the attached archive. On Hybrid application side it will be necessary to change import vsdeoldify as havcimport vshavc as havcThat's all. Thanks, Dan RE: Deoldify Vapoursynth filter - Selur - 28.05.2026 the torch I uploaded included 5.8.1 and the dev already uses "import vshavc as havc" will look at the new rc tomorrow |