This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Interface improvement for HINet
#1
Hello Selur,

   the HINet filter is able to perform 3 different tasks: "deblur", "denoise" and "derain".
   Currently it is possible to apply only one of them (even more times using the "Count" parameter)
   It is not possible to apply 2 of them or even all 3 in different sequence.
   A simple solution could be to include HINet in other tabs, for example "derain" in "DeGrain" and "deblur" in "Other" (or I hope in a new tab "Blur").

Thanks,
Dan

P.S.
I noted that HolyWu has archived the project regarding vs-hinet do you think the this project will be not more developed ?
Reply
#2
Quote:It is not possible to apply 2 of them or even all 3 in different sequence.
That is wrong.
1. By using FilterQueue instead of FilterOrder in Hybrid, you can (aside from crop, resize, deinterlace-handling) apply each filter as often as your system supports. (Also some filters might not work when used multiple times, but that is then a limitation of the filter and not of Hybrid.)
-> read: [INFO] About Vapoursynth Filter Order/Queue
2. Additionally, you could always use the custom section to add additional Vapoursynth code.
=> adding the filter multiple times is not needed.

Quote:I noted that HolyWu has archived the project regarding vs-hinet do you think the this project will be not more developed ?
vs-hinet is based on https://github.com/megvii-model/HINet which hasn't been updated for 9 months and he didn't get much user feedback so I guess that HolyWu decided that archiving was the right choice. I agree and don't think that vs-hinet will change in the future. There might be new papers and projects building on it, but that paper is finished.
But if you look at tons of Vapoursynth/Avisynth filters, it's kind of normal that filters don't change any more once the developers deem them finished.

Cu Selur
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)