Log in

View Full Version : Comparison: TomsMoComp vs. Hicon³²


zyrill
27th September 2006, 23:42
Over the years, I've encountered a few short articles about HiCon³², the deinterlacing tool written by Fraunhofer, the same guys who brought you mp3 and all the other goodies. A few ressources list it as the ultimate wisdom to aspire to and some ressources say it's just crap. I thought to myself: hell, it just CAN'T be bad - it's from Fraunhofer!
anyway, i wanted to find out: i took a short interlaced hdtv clip and ran it through tomsmocomp and through hicon³². following are the results, judge for yourself.

source clip:
Framerate 29.97 (1920x1080)

settings:
Avisynth: "TomsMoComp(-1,5,1)"
and
HiCon³²: "Demo 038: HDTV to HD-24p"

hicon:
http://img247.imageshack.us/img247/7779/hiconxn2.th.png (http://img247.imageshack.us/my.php?image=hiconxn2.png)
tomsmocomp:
http://img242.imageshack.us/img242/1527/tomsmocompua0.th.png (http://img242.imageshack.us/my.php?image=tomsmocompua0.png)
in case above images are deleted at some point in the future, i'll attach jpgs.

conclusion: i think i'll stick to tomsmocomp - except for the stair-artefacts you can see it clearly produces better results, makes the image more compressible (check sizes - same quality-settings used for both images) and costs less. also, compared to hicon, tomsmocomp is blazing fast. hicon took almost 15 minutes while tomsmocomp finished in say, 10 seconds. :)

anton_foy
28th September 2006, 03:00
hello zyrill!

Is there a certain reason you want to compare with just Tomsmocomp?

Have you tried MVbob (slow but extremely effective) or Tdeint with eedi2?

I use Tdeint+eedi2 all the time on my HDV material and its very fast and I have noticed when comparing with MVbob, tdeint+eedi2 is much sharper in static areas. Though the moving areas leave a lot of artifacts with Tdeint.

@Tritical: don't think Im putting you down in anyway I LOVE Tdeint! Still in progress? :)

Mug Funky
28th September 2006, 05:21
strange. i only get artefacts from Tdeint in very limited situations:

- field order is wrong (i've solved that with an auto-detection batch file :))

- there's very sharp scrolling graphics that move more per frame than the moving object's width (in that case a "hole" is left).

- there's a slow fade and tryweave = true

everything else appears to work perfectly :)

zyrill
28th September 2006, 08:20
Well, there was no particular reason besides me only doing a very quick and not, I'm afraid to say, very thorough investigation.
I have tried LeakTDeint but haven't gotten very good results and that's why I didn't post any images. But that might be due to the fact that I had never used it before and wasn't aware of the ideal settings.
I've deleted the source, so I can't do further tests on the material, but if I can get my hands on another decent interlaced HD sample, I would be willing to do a more thorough comparisson. (You wouldn't know where to find a sample with a lot of movement and clear edges just like the one I used?) :)
In the meantime: why don't you guys suggest some settings to use with MVbob and TDeint? I guess there'll be a bigger discussion, but maybe we can agree on, say, two sets for each deinterlacer - that would leave us with seven (only one from hicon) scenarios.
I write another exam next friday, so I'll be learning higher mathematics until then, but afterwards I have time again, so then we can set to investigating the best deinterlacer further. :)

halsboss
28th September 2006, 10:04
I use Tdeint+eedi2 all the time on my HDV material and its very fast and I have noticed when comparing with MVbob, tdeint+eedi2 is much sharper in static areas.
everything else appears to work perfectly :)
May I ask for a Tdeint+eedi2 sample script please (to learn from) ?

anton_foy
28th September 2006, 12:32
@halsboss & Mug

Hiya

Here is one example of difference between Tdeint and MVbob.
These are the lines I used:

### Tdeint+eedi2 ###
interp = separatefields().selecteven().EEDI2(field=1)
tdeint(order=1,field=1,edeint=interp)

### MVbob ###
MVbob().selecteven()

Tdeint+eedi2 (http://www.xtreem.nu/jonas/T-E.png)
MVbob (http://www.xtreem.nu/jonas/M-V.png)

DarkZell666
28th September 2006, 14:15
What if you run Undot over Tdeint+eedi2 ?
those dots look very small (one-pixel sized ? :))

dunno about the selecteven() but with mvbob you seem to loose more detail.

I'm no deinterlacing freak, I always use vdub's "blend-fields" mode or mencoder's pp=lb (linear blend) and never get any visible artifacts (except field-blending of course x))

krieger2005
28th September 2006, 14:23
For TDeInt: lower the values of "mthreshC" and "mthreshL".

anton_foy
28th September 2006, 17:13
@ DarkZell666

Undot sounds like a pretty creative solution but would it not get information from the previous frame that has the same artifacts? And does selecteven with Tdeint+eedi2 make the quality worse?
How can I halfen the framerate to 25P with MVbob the right way?

EDIT: Thank you DarkZell666 just tried undot and it fixed a lot of those annoying artifacts, only some detail in certain static areas of the image got a little worse but I can live with that!

@Krieger2005

Thanks but wouldn't that mean a loss in quality in for example static areas? I tried it yesterday and it just made it loose too much vertical resolution than with my original script.
Can I combine Tdeint "mthreshC" and "mthreshL" with eedi2 the same way as before?