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
removed encode_mode and updated Hybrid_havc_test

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
Hello Selur,

  using the R74 I compared the encoding speed of a 10min clip, using "core.num_threads = 1" vs  "core.num_threads = 0" (no limitation on threads count).
  Using only 1 thread I obtained a speed of about 5.28fps, while with no threads limitation I obtained a encoding speed of about 5.62 (see picture)

[Image: attachment.php?aid=3617]

  So in this case, using only 1 thread the speed decreased only of about 6%. But while in R74 the correct thread management is performed automatically, in R76 now this management is left to the user, that need to guess when is necessary or not. I hope there are no further "improvements" of this kind in the new R76, which have not yet been discovered.

Dan

P.S.
I'm going to the rename the github project "vs-deoldify" in "vs-havc" and to rename the package "vsdeoldify" in "vshavc", in the next days I will provide you the preview of "vshavc" package


Attached Files Thumbnail(s)
   
Reply
Quote:Setting to a value less than one makes it default to the number of hardware threads.
source: https://amusementclub.github.io/doc3/pyt...um_threads

Quote: I'm going to the rename the github project "vs-deoldify" in "vs-havc" and to rename the package "vsdeoldify" in "vshavc", in the next days I will provide you the preview of "vshavc" package
I'll adjust Hybrid accordingly when the time comes. Smile

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
I'm uploading a new torch add-on and Hybrid dev, which should be online in ~1 1/2 hours.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
Hello Selur,

  I renamed the project as: vs-havc
  no need on your side to update to version v5.8.1

  I attached the new RC8 with the change of package's name.

  The simplest way to move to the new package's name is to manually rename in you packages library the folder "vs-deoldify" in "vs-havc" and to rename the subfolder "vsdeoldify" in "vshavc" and then to overwrite the folder "vshavc" with the one included in the attached archive.

  On Hybrid application side it will be necessary to change

import vsdeoldify as havc
  in
import vshavc as havc

  That's all.


Thanks,
Dan


Attached Files
.zip   vshavc-5.8.5_RC8.zip (Size: 638,99 KB / Downloads: 2)
Reply
the torch I uploaded included 5.8.1 and the dev already uses "import vshavc as havc"
will look at the new rc tomorrow
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply


Forum Jump:


Users browsing this thread: 6 Guest(s)