Blocky picture?

[vie2233hil]

Hello,

Here's picture from dgindex (no spoiler tag)
http://img20.imageshack.us/img20/2329/17860608ab1.png
Here's picture from media player
http://img520.imageshack.us/img520/6987/17713106eo0.png

As you can see letters on first picture have visible "ladder", cpu=6 does not improve it much.
Is it supposed to be this way, i.e. "blocked" letters were encoded on DVD? How to process the picture to fix it?

Thank you

[Guest]

Please provide a link to an unprocessed source sample corresponding to that scene.

[vie2233hil]

http://rapidshare.com/files/169375908/noname.vob.html

this is a straight cut of first 5M from vob, in media player letters are round, in dgindex letters have visible "steps".

thanks

[Guest]

I don't know what rendering MPC is doing via DirectShow but DGIndex is showing the actual content of the video.

[laserfan]

I don't know what rendering MPC is doing via DirectShow but DGIndex is showing the actual content of the video.I gotta ask a newbie-ish question here and maybe it will help the OP. DGMPGDec w/DGDecode and DGIndex do not use *any* "external" DS MPEG Decoder filter, isn't that right? From the first paragraph of the DGDecode manual:

"DGDecode, part of the DGMPGDec package, is an MPEG-1/2 decoder plug-in designed for AviSynth v2.5 or higher. It's able to decode any MPEG-1 or MPEG-2 stream readable by DGIndex."

Therefore what-you-see in DGindex, or in VirtualDub if you make & open an avs i.e.

LoadPlugin("[PATH\]DGDecode.dll")
MPEG2Source("D:\video.d2v")

uses DGDecode and not any other DS filter in your system such as from ffdshow-tryouts/libavcodec for example.

Hopefully I'm right about this :o as it's made me crazy sometimes to try & figure-out where my videos are getting decoded-from, with various players. And different codecs/players can sure look very different!

As I type this it begs another question: can a .d2v be used with a DIFFERENT DS codec e.g. ffdshow (guess I could try it & see)...

[Guest]

Yes, DGIndex and DGDecode both have internal decoders based on the original MPEG2 reference code. I also opened the stream in VirtualDub using fccHandler's MPEG2 plugin, which is also derived from the reference code, and the frames look identical.

I have to suppose that MPC is using a filter that deinterlaces, resizes, or otherwise processes the frame. I can see that it is at least resized, as it is bigger than the actual frame when I open the file in MPC.

[laserfan]

Thanks neuron2 for your answer!

@ the OP, at least Media Player Classic allows you to see what filter(s) it is using. Look under Play>Filters when your video is loaded.

Sometimes other PC players allow GraphEdit to "Connect to Remote Graph" and see how the files are being rendered with them.

[vie2233hil]

answering my own question, I found another vob with the same blocky picture and it seems to be related to PAL or PAL->NTSC interlacing.
1. None of about 20 avisynth deinterlacing methods worked
2. Only "linear interpolation" and "ffmpeg deinterlacer" from ffmpeg produced good picture without blocking.
any ideas what is this?