Anssi Hannula wrote:

JJussi wrote:

...

Hi!

I have very simple and still hard question..

At vdr pluging setup - xineliboutput - Video. Post processing (ffmpeg) and Deinterlaceing. What ARE best values (to select) when you have HD LCD (via DVI) as TV and enough CPU power (Intel Core 2 Duo) to use.

I think that I'm not only one who thinks that there is too many choices.. ;-)

I use vdr-sxfe with "--video=xv --aspect=16:9 --post tvtime:method=Greedy2Frame,cheap_mode=0,pulldown=0,use_progressive_frame_flag=1".

Is there a document somewhere which explains all switches in above command ?

Anssi Hannula wrote:

Lauri Tischler wrote:

...

Anssi Hannula wrote:

...

JJussi wrote:

...

Hi!

I have very simple and still hard question..

At vdr pluging setup - xineliboutput - Video. Post processing (ffmpeg) and Deinterlaceing. What ARE best values (to select) when you have HD LCD (via DVI) as TV and enough CPU power (Intel Core 2 Duo) to use.

I think that I'm not only one who thinks that there is too many choices.. ;-)

I use vdr-sxfe with "--video=xv --aspect=16:9 --post tvtime:method=Greedy2Frame,cheap_mode=0,pulldown=0,use_progressive_frame_flag=1".

Is there a document somewhere which explains all switches in above command ?

I think they are shown somewhere in xine gui, but quoting from xine-lib source:

...

PARAM_ITEM( POST_PARAM_TYPE_INT, method, enum_methods, 0, 0, 0, "deinterlace method" ) PARAM_ITEM( POST_PARAM_TYPE_BOOL, enabled, NULL, 0, 1, 0, "enable/disable" ) PARAM_ITEM( POST_PARAM_TYPE_INT, pulldown, enum_pulldown, 0, 0, 0, "pulldown algorithm" ) PARAM_ITEM( POST_PARAM_TYPE_INT, framerate_mode, enum_framerate, 0, 0, 0, "framerate output mode" ) PARAM_ITEM( POST_PARAM_TYPE_BOOL, judder_correction, NULL, 0, 1, 0, "make frames evenly spaced for film mode (24 fps)" ) PARAM_ITEM( POST_PARAM_TYPE_BOOL, use_progressive_frame_flag, NULL, 0, 1, 0, "disable deinterlacing when progressive_frame flag is set" ) PARAM_ITEM( POST_PARAM_TYPE_BOOL, chroma_filter, NULL, 0, 1, 0, "apply chroma filter after deinterlacing" ) PARAM_ITEM( POST_PARAM_TYPE_BOOL, cheap_mode, NULL, 0, 1, 0, "skip image format conversion - cheaper but not 100% correct" )

And in a bit more detail, also from the source:

Advanced tvtime/deinterlacer plugin with pulldown detection This plugin aims to provide deinterlacing mechanisms comparable to high quality progressive DVD players and so called line-doublers, for use with computer monitors, projectors and other progressive display devices.

Parameters:

Method: Select deinterlacing method/algorithm to use, see below for explanation of each method.

Enabled: Enable/disable the plugin.

Pulldown: Choose the 2-3 pulldown detection algorithm. 24 FPS films that have being converted to NTSC can be detected and intelligently reconstructed to their original (non-interlaced) frames.

Framerate_mode: Selecting 'full' will deinterlace every field to an unique frame for television quality and beyond. This feature will effetively double the frame rate, improving smoothness. Note, however, that full 59.94 FPS is not possible with plain 2.4 Linux kernel (that use a timer interrupt frequency of 100Hz). Newer RedHat and 2.6 kernels use higher HZ settings (512 and 1000, respectively) and should work fine.

Judder_correction: Once 2-3 pulldown is enabled and a film material is detected, it is possible to reduce the frame rate to original rate used (24 FPS). This will make the frames evenly spaced in time, matching the speed they were shot and eliminating the judder effect.

Use_progressive_frame_flag: Well mastered MPEG2 streams uses a flag to indicate progressive material. This setting control whether we trust this flag or not (some rare and buggy mpeg2 streams set it wrong).

Chroma_filter: DVD/MPEG2 use an interlaced image format that has a very poor vertical chroma resolution. Upsampling the chroma for purposes of deinterlacing may cause some artifacts to occur (eg. color stripes). Use this option to blur the chroma vertically after deinterlacing to remove the artifacts. Warning: cpu intensive.

Cheap_mode: This will skip the expensive YV12->YUY2 image conversion, tricking tvtime/dscaler routines like if they were still handling YUY2 images. Of course, this is not correct, not all pixels will be evaluated by the algorithms to decide the regions to deinterlace and chroma will be processed separately. Nevertheless, it allows people with not so fast systems to try deinterlace algorithms, in a tradeoff between quality and cpu usage.

One conclusion is that Judder_correction and Pulldown are useless for PAL material. Use_progressive_frame_flag is also quite futile with DVB material, but some DVDs might benefit from it.

-Petri