ExactDeDup Update v0.06 - 15 Feb 2019

[AdamCarter]

Ok thanks

[Shinkiro]

I can't get it to work

Avisynth+ 3.7.0 x64 | ExactDedup 0.07.Beta01

setmemorymax(8192)
SetFilterMTMode("DEFAULT_MT_MODE", MT_MULTI_INSTANCE)
ffms2("lossless - 01.mkv",cache=false)
ExactDedup(firstpass=true, dupinfo="dupinfo.txt", times="times.txt", maxdupcount=20, keeplastframe=false, Show=false)
Prefetch(8)

[Reel.Deel]

@Shinkiro

Try disabling Prefect. I don't think ExactDedup plays nice with MT. I tried SetFilterMTMode("ExactDedup", MT_SERIALIZED) but it still had the same problem.

[StainlessS]

Options:
- firstpass : Default true. Controls which pass the plugin is running.

The first pass generates a mapping of output frames to
input frames (stored in the file specified by dupinfo) and
Matroska v2 timecodes (stored in the file specified by
times); seeking during this pass is impossible.
If not completely linear access from beginning to end of clip, then
will abandon processing, you cannot jump around the clip, and should not
use any multi processing (MT) methods.

The second pass generates a video stream containing only
the frames specified in the dupinfo file. (Seeking is
permissible during this pass.)

Above from author.
Dont use Prefetch, dont follow with any other filter when firstpass==true.
Cant offhand remember why.

[Shinkiro]

Reel.Deel, StainlessS
You're right, everything works now, thank you for your help

[Blankmedia]

His there a way to replace deleted frames with interpolated frames?


Edit: Nevermind found a really recent solution
https://forum.doom9.org/showthread.p...ight=filldrops

[goal1664]

I don't know why but it doesn't remove right frames for me...
so I edit dumpinfo with my frames to remove, but how can I get these kinds of timecodes "166.833333333" ? Mkvextract give me v2 like this: "166"
or is it possible to have timecodes for every frames with ExactDedup? [I have to get the timecodes of all the frames and delete the ones I don't need ]

[StainlessS]

I don't know why but it doesn't remove right frames for me

ExactDedup removes only EXACT duplicates [hence the name], if a single channel of a single pixel is different, then it is not an exact dupe.
Those very precise time codes would require double precision floating point, not do-able from script.

Suggest simple dupe detector based on Ydifference threshold to create frames list and then use RejectRanges().
Maybe see here [Methods for Duplicate Frame Detection & Deletion in Scripts]:- https://forum.doom9.org/showthread.php?t=182156
custom frame dropping:- https://forum.doom9.org/showthread.php?t=155683

RejectRanges:- https://forum.doom9.org/showthread.p...es#post1683559

[goal1664]

Originally Posted by StainlessS

ExactDedup removes only EXACT duplicates....

Many thanks for the immediate response and suggestions, yes I understood that this is for other purposes, I just hoped to be able to get around the problem creatively, since with other automatic detection filters I have not been able and the only way seems to be to insert the pattern manually (or frame list) ... however I'll do a separate thread because I'm having a lot of headaches with this file.