Log in

View Full Version : Seems like it's DECOMB.DLL's fault...


snake-boy
23rd June 2002, 18:36
Ok,

I have been trying everthing I can think of to solve the problems I am getting with this rip.

(refer to this thread for settings/details (neat the bottom):
http://forum.doom9.org/showthread.php?s=&threadid=24584)

After trying eveything conceivable, it seems the ONLY way this will work is if I do NOT use decomb.dll for IVTC. I d/l the ivtc plugin added in the place of decomb.dll, and suddenly everything is working fine.

ie:
LoadPlugin("F:\PROGRA~1\GORDIA~1\ivtc.dll")
ivtc(44,11,110)

instead of:

LoadPlugin("F:\PROGRA~1\GORDIA~1\decomb.dll")
Telecide()
Decimate(cycle=5)

Now here's the question: The ivtc.dll gives SLIGHTLY poorer results than decomb.dll (I have gotten decomb.dll to work using it in a frameserver script with virtualdub.)

Can ANYONE suggest what might be causing decomb.dll not to be working when I use it directly in gknot? (See the .log file I linked to in the above thread for the exact erros its giving.)

thanks all

-snake

evilhomer
24th June 2002, 16:01
I can't help with your decomb question, but I've seen several people rave about greedyHMA. I haven't tried it myself yet, so I apologize if it only does deinterlace, but I thought I saw posts talking about it's IVTC capabilities.