Nice, then it was just a packaging mistake.
Cu Selur
Happy New Year .Thanks to ALL
recent update Reference frames "ColorMnet" video colorization working good . without any error . 1st image original image from video 2nd image refernce based colorization
![[Image: Edit-final.jpg]](https://i.ibb.co/qR18H0K/Edit-final.jpg)
Hello Selur,
I just released the new vs-deoldify version
v4.6.0
In the new version I added 2 new color models under DDcolor:
Real-Time User-Guided Image Colorization with Learned Deep Priors (Zhang, 2017)
Colorful Image Colorization (Zhang, 2016)
these 2 models has been added as additional models:
siggraph17,
eccv16, in DDcolor since have in common the same settings and tweaks.
On first use the following pytorch models will be downloaded:
In vs-deoldify the torch hub directory is in: Hybrid\64bit\Vapoursynth\Lib\site-packages\vsdeoldify\models
You can install the new version with the command
Code:
.\python -m pip install https://github.com/dan64/vs-deoldify/releases/download/v4.6.0/vsdeoldify-4.6.0-py3-none-any.whl
No additional packages are necessary.
To add the new models in Hybrid GUI is just enough that you add the new DDcolor models 2 & 3 as described in the description of parameter
DDcolor-model contained in the
ddcolor_p list:
Code:
DDColor-model to use (default = 1):
0 = ddcolor_modelscope,
1 = ddcolor_artistic
2 = colorization_siggraph17
3 = colorization_eccv16
I hope that you have time to add them.
Thanks
Dan
I'll try to look into it.
A bit confused.
a. if this is a modification of DDColor, shouldn't DDColor get adjusted?
b. if this has nothing to do with DDColor, shouldn't the parameters&co get renamed?
Cu Selur
To simplify the development on my side, and I hope also on your side.
From the point of view of the GUi are just 2 additional models other that "modelscope" and "artististic".
In the HAVC_ddeoldify when are used the model 2 and 3 in ddcolor_p, like in:
Code:
clip = HAVC_ddeoldify(clip=clip, method=1, ddcolor_p=[2, 16, 1, 0, True], ddtweak=False)
or
clip = HAVC_ddeoldify(clip=clip, method=1, ddcolor_p=[3, 16, 1, 0, True], ddtweak=False)
will use the new "Colorizer" code and not DDcolor.
The 2 new models have the same instability problems than DDcolor, in this way I can use the filters already developed to stabilize DDcolor, to stabilize also the siggraph17 and eccv16 color models.
I will post a comparison in the thread
HAVC Filter User Guide
Dan
Created a new Hybrid_deoldify which adds the new models as choice.
Cu Selur
The new models has been added on DeOldify instead of DDcolor.
The models should be added with index 2 and 3 as described below
Code:
DDColor-model to use (default = 1):
0 = ddcolor_modelscope,
1 = ddcolor_artistic
2 = colorization_siggraph17
3 = colorization_eccv16
Please fix it.
Dan
Before I used:
Code:
values.clear();
values << QString("Video");
values << QString("Stable");
values << QString("Artistic");
this->addListField(QString("vsDeOldifyModel"), values.at(0), values, true);
and assumed you just added models.
But you also changed the old models.
And changed the defaults, thus invalidating any old settings for this in Hybrid.
Changed it now to:
Code:
values.clear();
values << QString("ModelScope");
values << QString("Artistic");
values << QString("Siggraph 17");
values << QString("ECC v16");
this->addListField(QString("vsDeOldifyModel"), values.at(1), values, true);
and updated the Hybrid_deoldify download. Hopefully this works now as requested.
Cu Selur
I think that there is a misunderstanding. You should change the list "vsDDColorModel" (or something similar)
Your version changed the DeOldify list
while DeOldify should be left untouched as shown below
Instead the 2 new models should be added to DDColor as shown below
Please fix it.
Dan