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.

Deoldify Vapoursynth filter
Very exciting to test this new release :-)

I'm getting this error on preview:  This with VapoursynthR68_torch
Failed to initialize VapourSynth environment!


Is it possible to run 2 versions of Hybrid (R65 & R68) on the same computer?  If R65 version is run on Drive C and R68 version on Drive D?
Reply
Quote:Is it possible to run 2 versions of Hybrid (R65 & R68) on the same computer?
You can't install multiple versions of Hybrid. (they would share the tools paths etc.)
But you can use different portable versions. (not sure one can mix a portable and a systemwide install)
But when using vsViewer outside of Hybrid you need to adjust the environments of the two.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
what about having two Vapoursynth folders in the 64bit folder VapoursynthR65 and VapoursynthR68 and depending on which version I want to run, just rename it to Vapoursynth.  
Or will that still have conflicts?
Reply
Quote:what about having two Vapoursynth folders in the 64bit folder VapoursynthR65 and VapoursynthR68 and depending on which version I want to run, just rename it to Vapoursynth.
Or will that still have conflicts?
Nope, that should work, since Hybrid does check the torch&co addons on each start.

For the future: please use a different thread for such questions.
This thread should be DeOldify only.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
Here another interesting case: https://imgsli.com/MjcxMDI3

In this example the colors provided by HAVC without DeepEx are very wrong, using DeepEx it is possible to improve the result (RefMerge=1 is the best in this case).

I released another RC where I introduced a check on the directory specified to store the images, if are not found reference frames is raised an Error.

Dan


Attached Files
.zip   vsdeoldify-4.0.0_RC4.zip (Size: 295,29 KB / Downloads: 32)
Reply
Nice. What to DeOldify and ddColor on their own look for this?
Used this clip from https://www.pexels.com/search/videos/flowers/.
=> for serious coloring, one probably should still stick with settings different value per scene (especially when the content type changes,..) or if possible provide deepEx with enough reference frames.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
Strange R65 with 'clip = HAVC_main(clip=clip)' works here. Ahh,.. VapoursynthR65_torch_2024.05.11.7z does contains vsdeoldify 3.5.2 not 3.5.3, maybe that is the problem.
=> deleted R65 torch from the GoogleDrive.
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
(09.06.2024, 18:48)Selur Wrote: Nice. What to DeOldify and ddColor on their own look for this?
Used this clip from https://www.pexels.com/search/videos/flowers/.
=> for serious coloring, one probably should still stick with settings different value per scene (especially when the content type changes,..) or if possible provide deepEx with enough reference frames.

Cu Selur

For serious coloring the best approach is the following.

1) Start with a simple

clip = HAVC_main(clip=clip)

If one is happy with results the next steps are not necessary. 
If there are some scenes with the wrong colors it is possible to adjust them following these steps:

2) Switch to "custom" mode, enable DeepEx, select method HAVC, set the "Ref FrameDir" and enable "Reference frames only",
    Then set "SC thresh = 0.1". This will output a non usable video, but will produce also in the selected directory the reference frames used by DeepEx.

3) If one is lucky the frames that need to be adjusted are already included in the directory specified previously. Otherwise is necessary to manually add new reference frames.

3) supposing that only the reference frames that need to be adjusted are: ref_000890.png and ref_0021450.png.
    These frames can be substitute with images containing the same elements and having the same size but with the correct colors.
    Then it is necessary to put the adjusted frames in another folder (with the same frame number), for example: "new_ref_frames" 

4) Select the method: "HAVC + RF same as video", and Ref merge = "med" and set the "Ref FrameDir" to "new_ref_frames"   
    In this way DeepEx will use the same frames as in the step 2, but the frames contained in  "Ref FrameDir" will override the frames produced by HAVC.
    The output of the movie produced in this way should contain the correct colors.

Dan
Reply
(09.06.2024, 18:48)Selur Wrote: Nice. What to DeOldify and ddColor on their own look for this?
Used this clip from https://www.pexels.com/search/videos/flowers/.

This is a simple movie where the reference image is enough to cover all the clip length (are not introduced new elements)

Provided 2 coloring results:

1) 1345932_DeepEx : movie colored with DeepEx only (for the reason explained above) 

2)  1345932_HAVC : movie colored with HAVC Stable (without DeepEx)


More interesting this case (1345932_DeepEx2) where I changed the color of reference image (included in the archive).

Dan


Attached Files
.zip   1345932_DeepEx.zip (Size: 1,49 MB / Downloads: 29)
.zip   1345932_HAVC.zip (Size: 1,51 MB / Downloads: 34)
.zip   1345932_DeepEx2.zip (Size: 1,75 MB / Downloads: 34)
Reply
@zspeciman:
Please, learn to use 'code'-tags.
Did you delete the old Vapoursynth folder before adding R68?
Might look at it more next weekend.
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply


Forum Jump:


Users browsing this thread: 3 Guest(s)