OK, well thanks for looking at it Reinhard.

It seems like there is a lot of work required with xine and ffmpeg, which is a shame because using them is obviously the more desireable solution at the moment. If spatial direct mode was properly implemented as well as these issues it would almost a complete solution - but so many channels use spatial direct then it looks like the kludge using CoreAVC might still be the only way at the moment. :-(

On Jan 20, 2008 11:16 PM, Reinhard Nissl rnissl@gmx.de wrote:

Hi,

Morfsta schrieb:

...

I was testing VDR with the H264 channels in Norway. It exhibits the same kind of artifacting I reported earlier with BBC HD channels (not spatial direct mode).

I have uploaded an example to: -

http://www.megaupload.com/?d=7N0J2G1L

Looks like the broadcaster has set the progressive frame flag and as such, no deinterlacing is applied when running the deinterlacer like that:

-Dtvtime:method=Greedy2Frame,cheap_mode=0,pulldown=0,use_progressive_frame_flag=1

To force deinterlacing even for progressive frames use this one:

-Dtvtime:method=Greedy2Frame,cheap_mode=0,pulldown=0,use_progressive_frame_flag=0

But it then looks like top and bottom field are shown in the incorrect order. Don't know whether this can be fixed. When the broadcaster sets the progressive frame flag, then there is usually no way to decide, which field must be displayed first. And it seems that tvtime's decision is the wrong one :-(

Bye.

Dipl.-Inform. (FH) Reinhard Nissl mailto:rnissl@gmx.de

---

vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr