[RESOLVED] DGDecodeNV(deinterlace=1) vs. KernelDeint

Support forum for DGDecNV
Post Reply
DAE avatar
Deadeye
Posts: 14
Joined: Sun Oct 17, 2010 3:28 pm

[RESOLVED] DGDecodeNV(deinterlace=1) vs. KernelDeint

Post by Deadeye »

Hi,

I'm just wondering, which deinterlace kernel acheives the best result, DGDecodeNV(deinterlace=1) or KernelDeint?

I'm planning on converting a bunch (aprox 200 hrs) of interlaced material from Canon HF10 and HF20 cameras and want to get a recommendation for the best deinterlace results possible.

All things being equal I'd prefer to have the delinterlace happen in the GPU so the CPU can be freed up for the encode. Is DGDecodeNV(deinterlace=1) just an implementation of KernelDeint in CUDA?

Any recommendations for getting the absolute best results possible? I'd like to eventually delete the source material.

Thanks in advance...
DAE avatar
Deadeye
Posts: 14
Joined: Sun Oct 17, 2010 3:28 pm

Re: DGDecodeNV(deinterlace=1) vs. KernelDeint

Post by Deadeye »

Well, it's a bit problematic for me to do a side-by-side / frame-by-frame analysis searching for motion combing and other deinterlace artifacts in various scenarios, so I thought I'd ask whether they're equivalent algorithms.

But thanks for the mention of QTGMC, I'll check into that.
DAE avatar
Didée
Posts: 22
Joined: Wed Oct 27, 2010 2:19 pm

Re: DGDecodeNV(deinterlace=1) vs. KernelDeint

Post by Didée »

A few small tests I did, sporting CUDA-deint, TGMC, tdeint(kernel), and Yadif: one, two, three
DAE avatar
Deadeye
Posts: 14
Joined: Sun Oct 17, 2010 3:28 pm

Re: DGDecodeNV(deinterlace=1) vs. KernelDeint

Post by Deadeye »

Didée wrote:A few small tests I did, sporting CUDA-deint, TGMC, tdeint(kernel), and Yadif: one, two, three
Thanks!!
User avatar
laserfan
Posts: 108
Joined: Thu Sep 09, 2010 5:16 pm

Re: DGDecodeNV(deinterlace=1) vs. KernelDeint

Post by laserfan »

For those of us with limited bandwidth to dl the samples, is there a clear winner?
User avatar
laserfan
Posts: 108
Joined: Thu Sep 09, 2010 5:16 pm

Re: DGDecodeNV(deinterlace=1) vs. KernelDeint

Post by laserfan »

Groucho2004 wrote:
laserfan wrote:For those of us with limited bandwidth to dl the samples, is there a clear winner?
Do you use one of these to connect?
Worse. A satellite dish! :evil:
User avatar
laserfan
Posts: 108
Joined: Thu Sep 09, 2010 5:16 pm

Re: DGDecodeNV(deinterlace=1) vs. KernelDeint

Post by laserfan »

Thank you. I guess we know now why your handle is Anon17!
User avatar
laserfan
Posts: 108
Joined: Thu Sep 09, 2010 5:16 pm

Re: DGDecodeNV(deinterlace=1) vs. KernelDeint

Post by laserfan »

Anon17 wrote:
laserfan wrote:I guess we know now why your handle is Anon17!
I don't get it. :?
Well duh. I asked a simple question, and instead of answering you gave me crap about my ISP. :roll:
DAE avatar
Didée
Posts: 22
Joined: Wed Oct 27, 2010 2:19 pm

Re: DGDecodeNV(deinterlace=1) vs. KernelDeint

Post by Didée »

<Here> is a page with some "objective numbers" about various (bob-) deinterlacers.


But there is bad news: For you, QTGMC probably is out of reach, anyway.
Reason: the package-of-plugins for QTGMC is approx. 18.5 MB in size. And as we have learned, you obviously cannot download such a gigantic file.

So, just forget about the slow QTGMC, and be happy with the simple, fast-running, flickering & bitrate-sucking traditional deinterlacers . (:
User avatar
laserfan
Posts: 108
Joined: Thu Sep 09, 2010 5:16 pm

Re: DGDecodeNV(deinterlace=1) vs. KernelDeint

Post by laserfan »

Didée wrote:<Here> is a page with some "objective numbers" about various (bob-) deinterlacers.
Thanks for the useful link.
people happily use slow, slower and evenslower x264 settings to improve 2 percent here, another percent there. But when it's about vastly improved frame quality at vastly reduced birate, then no, thanks, it is too slow. Let's rather use the poor Yadif to quickly turn the source into a psychedelic something, then compress with insane x264 settings to no avail.
I will look for the oppty to try it! :ugeek:

QTGMC that is! :D
DAE avatar
Deadeye
Posts: 14
Joined: Sun Oct 17, 2010 3:28 pm

Re: DGDecodeNV(deinterlace=1) vs. KernelDeint

Post by Deadeye »

I haven't been able to check back here in a while, but thanks all for the helpful info.
DAE avatar
Sharc
Posts: 233
Joined: Thu Sep 23, 2010 1:53 pm

Re: DGDecodeNV(deinterlace=1) vs. KernelDeint

Post by Sharc »

Instead of using a `compromise` deinterlacer you don`t fully trust, why not encoding interlaced? MBAFF has seen significant improvements recently.
User avatar
admin
Posts: 4551
Joined: Thu Sep 09, 2010 3:08 pm

Re: DGDecodeNV(deinterlace=1) vs. KernelDeint

Post by admin »

Can you tell us what the improvements were? Is it actually adaptive now? Thank you.
DAE avatar
Sharc
Posts: 233
Joined: Thu Sep 23, 2010 1:53 pm

Re: DGDecodeNV(deinterlace=1) vs. KernelDeint

Post by Sharc »

Adaptive quantization and efficiency improvements as I understand; more details e.g. from here:
https://github.com/DarkShikari/x264-dev ... its/master
Post Reply