TelecideNV: input must be YV12

Support forum for DGDecNV
Post Reply
DAE avatar
Guest 2
Posts: 903
Joined: Mon Sep 20, 2010 2:18 pm

TelecideNV: input must be YV12

Post by Guest 2 »

I tried to deinterlace HEVC file and I got:

TelecideNV: input must be YV12

The HEVC file is 10 bit, so DGSource feeds DGTelecideNV with a 16 bit frame.

Could you please introduce HBD to it? I don't know if there is any other 8 bit DGTool left.

Thanks.
User avatar
Rocky
Posts: 3557
Joined: Fri Sep 06, 2019 12:57 pm

TelecideNV: input must be YV12

Post by Rocky »

Please provide a sample of 10-bit HEVC that requires field matching and tell me its provenance. I have never seen such a source. You know that DGTelecide is not a deinterlacer, right?
DAE avatar
Guest 2
Posts: 903
Joined: Mon Sep 20, 2010 2:18 pm

TelecideNV: input must be YV12

Post by Guest 2 »

Rocky wrote:
Mon Jul 11, 2022 3:28 pm
Please provide a sample of 10-bit HEVC that requires field matching and tell me its provenance. I have never seen such a source. You know that DGTelecide is not a deinterlacer, right?
I know that. I need to process pulldown to a source I lazily ripped and encoded from BD some time ago, without noticing that it was 29.97 fps.

The originals are not in my hands anymore, otherwise I would have ripped them again. To minimize loss, I am trying to process them without bitdepth conversion.

NSFW sample: https://krakenfiles.com/view/DV9q2LNPQw/file.html
User avatar
Rocky
Posts: 3557
Joined: Fri Sep 06, 2019 12:57 pm

TelecideNV: input must be YV12

Post by Rocky »

That clip does not have field pulldown, but rather frame repetition, i.e., one of every 5 frames is duplicated. So it's not a candidate for DGTelecide. You can fix that clip using:

selectevery(5,0,1,3,4)

For the full stream the correct frame number to omit may be different depending on how the stream starts. We also assume the phase doesn't change, which it won't if this was encoded straight through.
DAE avatar
Guest 2
Posts: 903
Joined: Mon Sep 20, 2010 2:18 pm

TelecideNV: input must be YV12

Post by Guest 2 »

Rocky wrote:
Tue Jul 12, 2022 7:45 am
That clip does not have field pulldown
:oops:

ANYWAY, would you please add HBD support? :mrgreen:
User avatar
Rocky
Posts: 3557
Joined: Fri Sep 06, 2019 12:57 pm

TelecideNV: input must be YV12

Post by Rocky »

HONESTLY, I don't see the point. And with my timeline of life...
DAE avatar
Guest 2
Posts: 903
Joined: Mon Sep 20, 2010 2:18 pm

TelecideNV: input must be YV12

Post by Guest 2 »

Rocky wrote:
Tue Jul 12, 2022 8:41 pm
HONESTLY, I don't see the point. And with my timeline of life...
Simply because someone can use hevc as source and they are 10 bit :mrgreen:

Anyway, much better to have avscube on cuda now ;)
User avatar
Rocky
Posts: 3557
Joined: Fri Sep 06, 2019 12:57 pm

TelecideNV: input must be YV12

Post by Rocky »

When someone shows a 3:2 pulldown HBD HEVC clip in the wild, and not created artificially to prove a point, then we can consider it.
Post Reply