![]() |
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
|
RE: Deoldify Vapoursynth filter - Selur - 15.09.2024 Okay. Anything that needs to be downloaded once to setup vs-dedoldify should end somewhere below the vsdeoldify folder. This way, I can make a torchAddon with all the stuff in it. Anything that is generated during runtime should be in a configurable folder. So that if Hybrid is normally installed, this can be by default set to the temp folder (or in newer versions the engine folder) and changed by the user. vsdeoldify should throw an error is it can't write to somewhere where is need to write and not silently quit, so that Hybrid and the user can know whats happening. Cu Selur RE: Deoldify Vapoursynth filter - Selur - 15.09.2024 Updated the download to make sure ScFrameDir/sc_framedir is only set when set by the user, otherwise it stays at None. This causes: clip = HAVC_main(clip=clip, EnableDeepEx=True, DeepExMethod=1, DeepExRefMerge=0, DeepExModel=1) HAVC_deepex: method != 0 but sc_framedir is unset => Updated the download Cu Selur RE: Deoldify Vapoursynth filter - Dan64 - 15.09.2024 In the GUI when Ref merge <> "no", threshold is receiving the value of weight. If not changed the default value of threshold is 0.10. Dan P.S. ColorMNet is working on your side ? RE: Deoldify Vapoursynth filter - Selur - 15.09.2024 Hybrid, like the code: if enable_refmerge: Hybrid starts out with 'threshold 0.1' due to: def HAVC_main(clip: vs.VideoNode, Preset: str = 'Fast', VideoTune: str = 'Stable', ColorFix: str = 'Violet/Red', RE: Deoldify Vapoursynth filter - Dan64 - 15.09.2024 The box "Weight" should contain the value of parameter "ref_weight". As shown in the code "ref_weight" can have the value "refmerge_weight[ref_merge]" or 1.0 if ref_merge = 0. The problem is that in the GUI is see these values in the box "Threshold" not in the box "Weight". Moreover "ref_merge" should be enabled only when method is in: 0, 1, 2 In the code there is this check: if ref_merge > 0 and method > 2: Dan RE: Deoldify Vapoursynth filter - Selur - 15.09.2024 Quote:The problem is that in the GUI is see these values in the box "Threshold" not in the box "Weight".should be fixed now Not sure whether I got the rest, correctly. (Updated test version) --- Okay, got the models&co under Hybrid\64bit\Vapoursynth\Lib\site-packages\vsdeoldify\models expexted them under colormnet somewhere. ![]() Cu Selur RE: Deoldify Vapoursynth filter - Selur - 15.09.2024 using: # Imports Error on frame 0 request: Cu Selur RE: Deoldify Vapoursynth filter - Dan64 - 15.09.2024 Under colormnet must be put only the file DINOv2FeatureV6_LocalAtten_s2_154000.pth that must be saved in "\Lib\site-packages\vsdeoldify\colormnet\weights" The location of torch cache is the same for all the models used by vsdeoldify. Dan RE: Deoldify Vapoursynth filter - Selur - 15.09.2024 I had DINOv2FeatureV6_LocalAtten_s2_154000 in Hybrid\64bit\Vapoursynth\Lib\site-packages\vsdeoldify\colormnet\weights so that is correct. ![]() Quote:The location of torch cache is the same for all the models used by vsdeoldify.Okay. => so if the files are all there, deoldify should not need to write anywhere under "Program Files" on normal installations. ![]() Cu Selur RE: Deoldify Vapoursynth filter - Dan64 - 15.09.2024 (15.09.2024, 19:30)Selur Wrote: => so if the files are all there, deoldify should not need to write anywhere under "Program Files" on normal installations. It is called cache because is a temporary store. If a network file stored in the cache is updated on the torch repository, the first time that the network is used by torch, the cache will be updated with the new version. This is not a frequent situation but in theory it could happen. Dan |