![]() |
|
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
|
RE: Deoldify Vapoursynth filter - Selur - 27.09.2025 uploaded a new test version RE: Deoldify Vapoursynth filter - Dan64 - 27.09.2025 This dev version is Ok. There are some filter combinations which are not compatible with this method. When I will complete the tests I will provide you the exclusion list for this method. Thanks, Dan RE: Deoldify Vapoursynth filter - Selur - 27.09.2025 ok RE: Deoldify Vapoursynth filter - Dan64 - 28.09.2025 Hello Selur, this new method provides more stability, but is quiet slow, on my RTX 5070ti I get an average speed of 4.5fps. I will keep it, but I will suggest to using it only on high end GPU. Unfortunately on AI models the GPU power has a significant impact on the performance. Regarding the compatibility, when ColorTemp is not "none" the "Exemplar Models" check box must be unchecked and disabled. The "Exemplar Models" check box can be enabled if ColorTemp is set to "none". I tried to use this new method with "Exemplar Models", but apart the speed that decrease to 1.65fps the are random errors, so I prefer to disable "Exemplar Models" when ColorTemp is enabled. I was able to fix the problem by allocating the Colormnet class as singleton. To be able to run 2 parallel colormnet process, I had to duplicate the class (but not the weights). Now the encoding speed with all the models available enabled: deoldify + ddcolor + deepex + colormnet + colorment2 is about 5.9 fps. Really a big improvement ! These are the current defaults of the function HAVC_main, please check your list. Preset: 'Medium', (default)Regarding the GUI I would prefer something more similar to the old one, like this Thanks, Dan RE: Deoldify Vapoursynth filter - Selur - 28.09.2025 Quote: Regarding the compatibility, when ColorTemp is not "none" the "Exemplar Models" check box must be unchecked and disabled.just when I implemented it,... Quote: These are the current defaults of the function HAVC_main, please check your list.this will take a while,... RE: Deoldify Vapoursynth filter - Dan64 - 28.09.2025 (28.09.2025, 13:17)Selur Wrote:Quote: Regarding the compatibility, when ColorTemp is not "none" the "Exemplar Models" check box must be unchecked and disabled.just when I implemented it,... Sorry for this, I didn't expect to find a solution, but I finally did. ![]() Please look also to my suggestion on GUI widgets arrangement. Thanks, Dan RE: Deoldify Vapoursynth filter - Selur - 28.09.2025 Aside from RefRange: (0, 0) (default)=> uploaded new test version Cu Selur RE: Deoldify Vapoursynth filter - Dan64 - 28.09.2025 The new dev. version has a small bug. At startup, once HAVC is enable "B&W mode" and "B&W blend" are grey-out. It is enough to change value to "B&W tune" and they are enabled again. Dan P.S. Attached the new RC2 RE: Deoldify Vapoursynth filter - Selur - 28.09.2025 Quote: At startup, once HAVC is enable "B&W mode" and "B&W blend" are grey-out.Strange,.. that is not the case here. ![]() Might be a wrong initialization. => Yes, changing the default for BWTune requires the initial state to change,... uploaded a new test version Cu Selur RE: Deoldify Vapoursynth filter - Dan64 - 28.09.2025 Problem fixed with the last dev version. Thanks, Dan |