[Bug 793495] New: msdk (vaapi/x264/etc): encode: renaming the target-usage to speed-preset

[GStreamer (GNOME Bugzilla)]

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

            Bug ID: 793495
           Summary: msdk (vaapi/x264/etc): encode: renaming the
                    target-usage to speed-preset
    Classification: Platform
           Product: GStreamer
           Version: 1.13.1
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: Normal
         Component: gst-plugins-bad
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: bsreerenj at gmail.com
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

This is for discussing the unification of speed-quality-tradeoff property in
different encoders which could be most commonly used tuning option for general
users.

The current msdk encoders have a property "target-usage":
target-usage        : 1: Best quality, 4: Balanced, 7: Best speed
                        flags: readable, writable
                        Unsigned Integer. Range: 1 - 7 Default: 4 


The same thing in gstreamer-vaapi is:
quality-level       : Encoding Quality Level (lower value means
higher-quality/slow-encode,  higher value means lower-quality/fast-encode)
                        flags: readable, writable
                        Unsigned Integer. Range: 1 - 7 Default: 4 


x264enc has this:
speed-preset        : Preset name for speed/quality tradeoff options (can
affect decode compatibility - impose restrictions separately for your target
decoder)
                        flags: readable, writable
                        Enum "GstX264EncPreset" Default: 6, "medium"
                           (0): None             - No preset
                           (1): ultrafast        - ultrafast
                           (2): superfast        - superfast
                           (3): veryfast         - veryfast
                           (4): faster           - faster
                           (5): fast             - fast
                           (6): medium           - medium
                           (7): slow             - slow
                           (8): slower           - slower
                           (9): veryslow         - veryslow
                           (10): placebo          - placebo


Does it make sense to use the same property for all?
It could break the backward compatibility for gstreamr-vaapi and x264.
But for msdk, this seems to be the right time for a change like this.
I would like to get some general opinion on this.

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