Artifacts When Decoding

[YairGOW]

Hi,

I've noticed some artifacts being generated while loading a file I indexed with DGIndexNV. It's an interlaced h264 bluray stream, and this is how the artifacts look compared to using dss2 to load the clip:
http://screenshotcomparison.com/comparison/39284

Any solution for this while still using DGIndexNV?

Edit: This might relate to the following post: http://www.neuron2.net/board/viewtopic.php?f=8&t=246
The glitches I get are always there, though, regardless of where I choose to seek from.

[admin]

Can you please provide a source sample that I can use to duplicate the issue? Thank you.

[YairGOW]

Here you go - 3 samples:
http://www.mediafire.com/?f7pt5d728c5bqgv
http://www.mediafire.com/?e7zhzzpkr0b52pi
http://www.mediafire.com/?htosttripczxzd5

[YairGOW]

Might be wise to add that using DGAVCIndexDI produces the same glitches.

[admin]

I downloaded the first sample and served it to VirtualDub with DGSource(). I do not see any artifacts. Please give me a specific frame to look at.

In any case, the artifact in your screenshot does not look like a typical decoding error.

[YairGOW]

Second link, frames 917-930 supposedly, though it seems to not be present in the samples(after being muxed to mkv and cut), but only in the full clip when indexed...

[admin]

It's hard to help without a sample that shows the problem.

[YairGOW]

Well, every time I make a cut with mkvmerge where a glitch appears in the complete file, the glitch won't be present in the cut...

Edit: looks like if you separate the fields of the interlaced stream you'd find the glitch, so use separatefields()/QTGMC/etc and test this sample(made it small enough): http://www.mediafire.com/?dd8v9spkfo4j6j4

[admin]

I'm still not seeing any artifacts.

Please check your RAM and cooling. Make sure you are not overclocked.

[YairGOW]

Weird :\

Rig is perfectly fine and not overclocked, so I'm really perplexed here.

[BarryW]

I noticed that your source is NTSC 29.97fps
http://www.mediafire.com/?dd8v9spkfo4j6j4

I think the original source (that this was taken from by the broadcaster) is likely to be 25fps.
So this means you probably have telecined source - telecined from 25fps to 29.97fps.

I'm not sure which method they use to do this. They could be using repeat frames or they could slow it down to 23.97fps (film rate) and then telecine it up to 29.97fps (NTSC rate) using 3:2 pull down. Which ever method is used it usually ends up a mess which could be the cause of the problem.

De-telecining it back to 25fps might help but I'm not an expert on this.