Developers, As far as I have seen you have successfully implementeted the API technology to select interlacers in the video pipeline as video postprocessor since middle of last year. The VDR community is still waiting for MotionAdaptive or MotionCompensated. Could you comment on your schedule for that? - Is it for some reason technologically impossible to get it implemented? - Are the plans for IVB or SBR to make it available? Best regards - Mario $ ./vaapi-vpp libva info: VA-API version 0.34.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/local/lib/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_0_34 libva info: va_openDriver() returns 0 video/vaapi: libva 0.34 (Intel i965 driver - 1.0.16.pre1) initialized Maximum VAProfiles: 11 Maximum VAProcFilterCount: 8 Maximum VAProcDeinterlacingCount: 5 Profiles available: 10 1: VAProfileMPEG2Simple 2: VAProfileMPEG2Main 3: VAProfileH264Baseline 4: VAProfileH264Main 5: VAProfileH264High 6: VAProfileVC1Simple 7: VAProfileVC1Main 8: VAProfileVC1Advanced 9: VAProfileNone 10: VAProfileJPEGBaseline postproc: video postprocessor available postproc returned 2 filters postproc returned 1 denoisers postproc returned 1 interlacers postproc filter 0 is noise reduction postproc filter 1 is deinterlacer postproc deinterlacer 0 is bob
