Deoldify Vapoursynth filter

[Dan64]

I tested the new version and it seems working.

The ColorMNet[local] is working on your side ?

In my experience the only case that i found for failing in initialize ColorMNet[remote] is the issue of some warning (even in some loaded library) that are not trapped by the Vapoursynth logger because the "remote" thread don't install any logger. This is the reason why I tried to suppress all warnings in __init__.py.

I don't spent too many time to fix this issue because the previous version was working on your side.
I will try to reproduce the problem, to see if there is a way to fix it.

In any case in the recommended settings for Hybrid: https://github.com/dan64/vs-deoldify#col...ing-hybrid
I suggested to use ColorMNet[local], because I recommended to set SCMinFreq=3 and in this case, since Vivid is also checked, the memory will be reset every 3 frames that is below the limit for using ColorMNet[local]. To feed the frames to ColorMNet[remote] they need to be converted in ASCII and then after the coloring need to be converted again in ASCII when the colored frames are retuned back to the client. This conversion is introducing an overhead that is not justified in this case because the memory is reset every 3 frames.

I hope to be able to fix the issue, in meanwhile you can use ColorMNet[local].

Thanks,
Dan