Quote:
Originally Posted by Didée
Code:
Lanczos4resize(720,576)
AssumeTFF() #choose the SAME field order like before deinterlacing
Blur(0,1).SeparateFields().SelectEvery(4,0,3).Weave() #reinterlace.
|
Would there be any advantage (or disadvantage) in doing the Blur before the resize?
Given you have to vertically blur the results, is there in fact any point in using (Q)TGMC for deinterlacing just in order to do an re-interlaced downsize? Would an 'inferior' but faster deinterlacer give equally good results, or do you still gain something from the temporal processing of (Q)TGMC?
Quote:
Originally Posted by Boulder
Any chance you could release masktools-25.dll or -26.dll for testing? It seems that most of my crashes in VDub point to that dll.
|
I suspect that is simply because most of the time in QTGMC is spent inside masktools, so that's usually where it is when it runs out of memory or gets a bad pointer from the Avisynth cache. However, it
is important to use the right version (25 or 26) to match your Avisynth.