![]() |
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 - Dan64 - 06.02.2025 The new RC3 removed and added some file, maybe is better to replace completely the vs-deoldify folder with the new RC3 (keep the models stuff like *.pth and related files). The error on colorizer it is normal at the first run because of order on witch are compiled the python scripts. If you run again the second time should work. In the attachment are provided 2 sample script, that you can use to test the method=5 in RC3. HAVC_main_method5.vpy with the call to HAVC_main sc_framedir="test_green_color.mp4" HAVC_custom_method5.vpy with the call to custom functions clip_ref = havc.HAVC_read_video(source="test_green_color.mp4", fpsnum=24000, fpsden=1001) In the previous version released for test, all was working (including the custom section) with the only exception of method=5. So I concentrate the explanations only on the management of method=5. I'm not asking to rewrite all the HAVC Hybrid code. Just to add the management of method=5. This imply few steps: 1) read from the GUI the path to clip to restore 2) call the HAVC functions as shown in HAVC_main_method5.vpy when is used the Speed != "custom" HAVC_custom_method5.vpy when is used the Speed == "custom" I don't want to complicate the implementation more than necessary. ![]() Thanks, Dan P.S. please re-enable the "custom" section RE: Deoldify Vapoursynth filter - Selur - 06.02.2025 Quote:please re-enable the "custom" sectionNot until the non-custom section is working completely. Quote:DeepExMethod=havc.HAVC_RESTORE_VIDEOWhere did that come from? I thought DeepExMethod was an integer? :param DeepExMethod: Method to use to generate reference frames. Quote: The new RC3 removed and added some file, maybe is better to replace completely the vs-deoldify folder with the new RC3 (keep the models stuff like *.pth and related files). ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() I'll look at it over the weekend. Cu Selur RE: Deoldify Vapoursynth filter - Dan64 - 06.02.2025 Respect to version 4.6.8 the version 5.0.0 RC3 Added: havc_constants.py havc_filters.py havc_utils.py Removed vsslib\constants.py in the function havc_constants.py I added some constants to identify the models and to assign defaults values. The constants related to Parameter Values are: HAVC_SAME_AS_VIDEO=0 I'm planning to add the identifiers for the other models: deoldify, ddcolor, Zhang... If at the beginning of the script you add the following code import vsdeoldify as havc you can use these constants inside the script. Dan RE: Deoldify Vapoursynth filter - Selur - 06.02.2025 Quote:you can use these constants inside the script.I know, maybe I'll do that at some point, atm. I don't want to add another change. First, the existing stuff needs to work. Then I can look into things one at a time. Atm. I spend an hour coding, just to see that you changed stuff and I can start rewriting again since there are changes everywhere. Your RCs are basically alphas, normally RC implies a feature&interface freeze. After a RC, there should only be bug fixes, no new features an interface changes. => until non-custom HAVC works, 'custom' stays removed. Then I look at method 0, 1, 2, 4, 5, if the interface&co until custom works complete, custom gets disabled and I go back to first testing non-custom. Cu Selur RE: Deoldify Vapoursynth filter - djilayeden - 07.02.2025 Dear Selur, Please continue to support DeepRemaster. Your work on HAVC is already remarkable, and what you're doing with it is truly impressive. Thank you for your dedication and for moving things forward with such precision. A big thank you also to Dan for all his efforts and incredible ideas with HAVC! Yours sincerely RE: Deoldify Vapoursynth filter - Dan64 - 07.02.2025 Sometime I forgot that python is not a true language. I spent 3 hours to understand that ColorMNet was broken because I called a constant ColorMNet and python was calling the constant instead to call the function, obviously without issue any message that made sense. Also the debugger was unable to recognize that was called a constant instead of a function. It simple refuse to step-in, even in this case without issue any message that made sense. Attached the new RC4. Removed: havc_constants.py havc_filters.py Added: havc_utils.py vsslib\constants.py Removed all the parameters constants. Included new sample test, with the parameters constants removed. Sorry for the inconvenience, I had to rollback a lot of code before find the reason of ColorMNet failure. Dan RE: Deoldify Vapoursynth filter - Selur - 07.02.2025 With that version non-custom seems to work. RE: Deoldify Vapoursynth filter - Selur - 07.02.2025 'custom' does not work for me on my first test: # adjusting color space from YUV420P8 to RGB24 for vsDeOldify Failed to evaluate the script: Updated Hybrid_deoldify. (did not write code when FilterQueue is used, so this is limited to FilterOrder) Cu Selur RE: Deoldify Vapoursynth filter - Selur - 07.02.2025 https://github.com/HolyWu/vs-rife/commit/670ae68fa9130b3453e6eee2619766063beae292 => unbelievable ![]() RE: Deoldify Vapoursynth filter - Dan64 - 07.02.2025 When Hybrid call HAVC_read_video must provide also the parameters fpsnum, fpsden My example was not perfect, the exact way to call HAVC_read_video is clip_ref = HAVC_read_video(source=ScFrameDir, fpsnum=clip.fps_num, fpsden=clip.fps_den) the clip_ref can have different frame size or number of frames, but must have the same fps of clip to be colored, so it is necessary to pass clip.fps_num, fpsden=clip.fps_den Thanks, Dan (07.02.2025, 17:47)Selur Wrote: https://github.com/HolyWu/vs-rife/commit/670ae68fa9130b3453e6eee2619766063beae292 HolyWu is deeply involved in the development of torch. I think that he is using his projects to test and develop new features for torch. Unfortunately torch is not stable and is still under strong development. ![]() Dan |