Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

GearlessGoG

7
Posts
A member registered Dec 08, 2020

Recent community posts

(3 edits)

I'm on 1.18.2

I ran dedup on a frame folder, it said 'difference from frame 00000001.png to 00000002.png: 1,97% - Deleting. Total: 0 kept / 1 deleted' then proceed to delete the whole folder with over 115000 frames.

[edit]

1 small update: I tried several different settings: tried changing the threshold to 1% (was 2% I think, the default value) - same; changed threshold to 4% - (obviously) same; tried the 'only analyse, don't delete' option - same (it deleted the whole folder yet again); copied a bunch of random frames to a folder (absolutely different from one another), renamed them to 00000001, 00000002, 00000003, 00000004, etc. (15 frames total) it said 'kept 15 frames, deleted 0 frames', but deleted the whole folder again.

The solution is to get a graphics card with more VRAM or use another algorythm. DAIN uses A LOT of VRAM. They recommend at least 10GB for 720p interpolating. If it's linear with number of pixels, 4GB should be enough for DVD 16:9 max (ie 853x480) and 2GB for ~ 610 * 343 resolution (if it's 16:9)

lol my bad I didn't realize the changenotes were always up to date.

I think for some reason it had disabled that function. For now I will keep the duplicate frames because I'm running some time demanding projects. I will look for the 'dynamic timing' thing after.

Thanks!

That means your card can't use the selected algorythm at the intended resolution because of VRAM. DAIN uses A LOT of VRAM (they recommend at least 10gb for interpolating 720p, you can only safely interpolate 1080p using it with workstation-grade cards, such as QUADRO RTX 6000, 8000, A6000). PyTorch version of RIFE also needs lots of VRAM. Try RIFE-NCNN or CAIN.

I have one question because I feel I might be missing something. If I enable the 'remove duplicated frarmes', won't I have a final video with different timing, thus rendering it very difficult to resync sound? I tried it once and the number of frames was (obviously) lower than 'x times the original source' so when reencoding the final video was totally out of sync. Did I do something wrong? Should then the frames get different timings? Or is it 'by design'?

Also, do you have changenotes somewhere?


Thank you

Two questions:

1. Any prevision as to when will V17 be available to free users? Scene detection is a highly anticipated feature.

2. Could it be possible to assign x3, x5, x6, x7 (ie not only binary numbers)? 

Thanks!

I had the same problem, discovered that for some reason it was using GPU '0,1' I changed to '0' and that problem was gone