View Full Version :
IVTC 2.10 too slow ?
ppera2
7th December 2001, 23:36
I started today to convert movie Bambi. It is Chinese, picture little noisy, res 720x480, NTSC .
Usual, considered as fastest way: DVD2AVI, AVYSinth etc...
But I get only 11-12 fps on my Athlon with DDR board. It forced me to try IVTC with TMPGEnc.
After automatic IVTC i get about 17 fps in VDub. By same resize parameters. It is very interesting. OK, IVTC was already done in TMPGEnc, but this methode is much slower, and I worked with full processing and resize in VDub. AVYSinth methode was of course with fast recompress.
At end TMPGEnc methode made all it faster... Also, I have impression that IVTC 2.10 is not too reliable, sometimes it results with choppy movement.
Is this plugin really so slow ? Is problem high resolution ?
DJ Bobo
14th December 2001, 21:49
very interesting! well, on my PIII@700 I get only 5fps using AviSynth/IVTC, I will give TMPG a try and see what happens...
UPDATE:
Well, I tested the TMPG method and I got this time only 3,6fps in VirtualDub! (filters: precisebicubic(0.6)+temporalsmoother(3))
I don't know how do you managed to get it work faster than AviSynth, you may post your settings here!
The source was a 720x480 NTSC-DVD.
fisix
15th December 2001, 00:54
you know, i tried doing ivtc with some copies of the prisoner (NTSC on the copies i have) in both the new gknot (avisynth ivtc) and using nandub/tmpg. i cant tell you about speed right now (wasn't looking) but i CAN tell you that it seems that the tmpg way, using just the ivtc wile encoding option, works much better than the avisynth plug-in. the end result looks better and seems less choppy. this might just be a problem with gknot's new generic settings.. i'm going to be testing a little more, and i'll post back here about speed.
-fisix
ppera2
15th December 2001, 01:40
bobotns: You must be careful with TMPGEnc. It has not switch for resize, and if it works, it is very slow.
To ensure that no resize you must set in and out res to same, of course. But also must set source aspect ratio (setting, advanced) and video aspect ratio to same (best VGA). Video arrange method to full screen.
For better speed you will need also following: In DVD2AVI set RGB, because TMPGEnc work with RGB, crop in DVD2AVI - so less data to frameserve & IVTC. Resize better in VDub, TMPGenc is slow in that.
By Bambi I didn't make resize, only crop, that's way I have so big framerate. I didn't used smoother too. By noisy source bilinear resize is better.
anecd0te
15th December 2001, 09:47
Xmas is just around the corner... why not ask for a new 'puter? :D
I usually get 24 fps with IVTC on my P4 1.7GHz, and about 33+ fps without IVTC.
Have you given GreedyHMA a try? I just used it on my last encode and was very impressed with the results.
Happy Holidays!
ppera2
15th December 2001, 15:33
Is that GreedyHMA IVTC or just deinterlace ?
macdaddy
15th December 2001, 15:42
You can read all about Greedy HMA here (http://rilanparty.com/vbb/showthread.php?s=&threadid=7254).
fisix
15th December 2001, 17:24
does the new gknot use greedyHMA when you try ivtc?
Toon_Junkie
16th December 2001, 19:07
Hi Guys...
can you point me in the right direction on how to use the TMPG within VDub.
I usually just use AVISynth and CCE.. but am curious about the process for TMPG. (I used to use it before with AVIUtil doing the IVTC so I am kinda familiar with the programs)
Thanks
fisix
18th December 2001, 01:51
i tried using the greedyHMA with gordian knot, nandub etc, and it works VERY well. on par with tmpg. you have to edit the avs file manually to apply greedyHMA, you can't just click on the IVTC button in the gordian knot save and encode gui. anyway, it was also quite fast.
a good guide on how to use tmpg with vdub or nandub is on doom9's site. go to guides->divx3->nandub sbc and read the guide all the way through.
-fisix
DJ Bobo
20th December 2001, 19:37
Well, I compared the newest versions of GreedyHMA and IVTC 2.101.
I found, they are equal in quality, but GreedyHMA is about 5 to 6% faster on my PIII @700MHz.
But for some reason I don't trust GreedyHMA, I feel better using IVTC 2.101!
fisix
20th December 2001, 20:19
Well, I compared the newest versions of GreedyHMA and IVTC 2.101.
I found, they are equal in quality, but GreedyHMA is about 5 to 6% faster on my PIII @700MHz. But for some reason I don't trust GreedyHMA, I feel better using IVTC 2.101!
you realize that this is proper evidence to have you committed?
loco, crazy, nuts, rocks instead of marbles.
greedy is a godsend, and i'm a little surprised that you got IVTC 2.101 to look as good quality wise, i've not been able to get it to perform that well.
5-6% faster on a p3700 has got to be worth the leap in faith!
-fisix
DJ Bobo
21st December 2001, 20:38
@ fisix
I gived GreedyHMA (0.4) a chance yesterday with a whole Anime DVD, I must say, I was wrong, the quality is worse than IVTC 2.101!!!
Well, that means, I'll keep using IVTC 2.101, I feel save with it!
trbarry
21st December 2001, 22:46
I gived GreedyHMA (0.4) a chance yesterday with a whole Anime DVD, I must say, I was wrong, the quality is worse than IVTC 2.101!!!
What parameters did you use? Anything specific you feel could be improved? I might get back to trying to improve it one of these days.
- Tom
DJ Bobo
22nd December 2001, 00:28
@ trbarry
EDIT: Excuse me for disturbing you, after precise looking, IVTC wasn't that different, both filters cause small drawing lines jitter and skip sometimes frames that shouldn't be skipped.
And now it comes: with another new DVD, AviSynth can't process the video using IVTC 2.101 at all!! (reading error or something!) with GreedyHMA, it works without any errors!
NB: I use the following parameters:
LoadPlugin("C:\AV\GKnot\mpeg2dec.dll")
LoadPlugin("C:\AV\GKnot\hma\greedyhma.dll")
mpeg2source("C:\dbz\1\1.d2v")
GreedyHMA(1,0,4,0,0,0,0,0)
crop(12,0,700,478)
BilinearResize(448,336)
TemporalSmoother(2,1)
Well, after this small lesson, I think I will stick to GreedyHMA.
I apologize and thank you for that great tool and... merry christmas :)
vBulletin® v3.8.4, Copyright ©2000-2009, Jelsoft Enterprises Ltd.