Any idea of a better fix to this QTGMC issue?

[kuchikirukia]

http://forum.doom9.org/showthread.php?t=172744

Recap: Avisynth likes to create and destroy input filter threads if you use QTGMC in a heavy script or on an HD source, creating massive slowdowns. Using Trim can fix this.

I'm getting kinda tired of doing two encodes at trim(0,99) and trim(100,0), so is there a better way to do this?

Edit: After looking at Trim examples, this seems to work, adding a single frame:
Trim(4,length=1) ++ Trim(0,0)

Now how to delete (or not output) that frame...

E2: erm, well this one of course resyncs for that frame:
Trim(4,length=1) ++ Trim(1,0)

[kuchikirukia]

Well, we seem to have a better version now that starts by fetching frame 4 and overlays frame 0 on it.

But why the heck would Avisynth be bugging out like this unless you fetch frame >=4 first? It does NOT like starting with frame 0.

[kuchikirukia]

Update: Avisynth 2.6 MT with SetMTMode(5) before the source filter fixes the problem.

So:
Broken in Avisynth 2.6 ST
Broken in Avisynth+
Broken in Avisynth 2.6 MT without SetMTMode

Trimming ahead fixes it.
SetMTMode (5) or (6) fixes it.