03.10.2024, 18:29
I discovered that, for some reason the warnings issued by other threads will affect the colormnet thread.
For this reason I removed all the workings raised by vsdeoldify.
I added the following function in vsdeoldify\__init__.py
on my side this function is working properly and the warnings are not shown any more.
I attached my last version (there is my work in progress on scene detection) where I removed the field port. Now when I create the server I set the port=0 so that the O.S. will assign the first port available (useful in case of parallel encoding).
Please let me know if with this version the warnings are removed.
Thanks,
I attached a sample for testing ColorMNet (remote).
On my PC is very fast (16 fps).
Dan
For this reason I removed all the workings raised by vsdeoldify.
I added the following function in vsdeoldify\__init__.py
def disable_warnings():
logger_blocklist = [
"matplotlib",
"PIL",
"torch",
"numpy",
"tensorrt",
"torch_tensorrt"
"kornia",
"dinov2" # dinov2 is issuing warnings not allowing ColorMNetServer to work properly
]
for module in logger_blocklist:
logging.getLogger(module).setLevel(logging.ERROR)
warnings.simplefilter(action='ignore', category=FutureWarning)
warnings.simplefilter(action='ignore', category=UserWarning)
warnings.simplefilter(action='ignore', category=DeprecationWarning)
# warnings.simplefilter(action="ignore", category=Warning)
torch._logging.set_logs(all=logging.ERROR)
on my side this function is working properly and the warnings are not shown any more.
I attached my last version (there is my work in progress on scene detection) where I removed the field port. Now when I create the server I set the port=0 so that the O.S. will assign the first port available (useful in case of parallel encoding).
Please let me know if with this version the warnings are removed.
Thanks,
I attached a sample for testing ColorMNet (remote).
On my PC is very fast (16 fps).
Dan