[Bug 781069] postproc: framerate should not be always duplicated

GStreamer (GNOME Bugzilla) bugzilla at gnome.org
Mon Apr 17 21:44:40 UTC 2017


https://bugzilla.gnome.org/show_bug.cgi?id=781069

--- Comment #16 from sreerenj <bsreerenj at gmail.com> ---
(In reply to Benjamin from comment #15)
> @Victor, I tried every deinterlace option in vaapipostproc 
>   
>      deinterlace-method  : Deinterlace method to use flags: readable,
> writable
>                         Enum "GstVaapiDeinterlaceMethod" Default: 1, "bob"
>                            (0): none             - Disable deinterlacing
>                            (1): bob              - Bob deinterlacing
>                            (2): weave            - Weave deinterlacing
>                            (3): motion-adaptive  - Motion adaptive 
>                            (4): motion-compensated - Motion compensated 
> 
> and they all doubling the framerate and GPU usage goes 20% just for
> deinterlacing alone.
> 
> 
> In the other hand i tried with https://github.com/01org/gstreamer-media-SDK
> gst-inspect-1.0 mfxvpp:
> deinterlacing with MSDK also uses bob by default
> 
>   deinterlace-mode    : Deinterlace mode to use
>                         flags: readable, writable
>                         Enum "GstMfxDeinterlaceMode" Default: 1, "bob"
>                            (1): bob              - Bob deinterlacing
>                            (2): adi              - Advanced deinterlacing
>                            (11): adi-noref        - Advanced deinterlacing 
>                            (12): adi-scd          - Advanced deinterlacing 
>                            (13): weave            - Field weaving
> 
> Frame rate is not doubled with bob and video is not shaking.
> Also with MSDK deinterlcing has very low GPU footprint like 2% max.
>

Can you check the performance with out the encoder in pipeline ? eg: a decdoer
! deinterlacer deinterlace-method=2 !

Just to check whether the driver is actually doing the deinterlacing and not
doing the interlaced encoding over interlaced content.

But most probably performance impact should be investigated from driver side.

> 
> 
> As of right now with VAAPI I can't do more then 3x 1920x1080 at 25 leaner
> transcodes GPU goes to 100% and it's Skylake HD Graphics 530 
> 
> vs MSDK 12x 1920x1080 at 25

How many streams you can encode with gstreamer-vaapi, but with no
de-interlacing?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.


More information about the gstreamer-bugs mailing list