After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 790298 - vtenc: vtenc_h264 property defaults in described help text don't match actual defaults.
vtenc: vtenc_h264 property defaults in described help text don't match actual...
Status: RESOLVED NOTABUG
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
1.12.3
Other Mac OS
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-11-13 17:26 UTC by Miki Grof-Tisza
Modified: 2017-11-13 18:13 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Miki Grof-Tisza 2017-11-13 17:26:49 UTC
some of the properties on vtenc_h264 are described in the output of gst-inspect-1.0 with defaults that don't match actual defaults.  For example:

  allow-frame-reordering: Whether to allow frame reordering or not
                        flags: readable, writable
                        Boolean. Default: true

The #define at the top of the code does in fact imply the default should be TRUE, but it isn't initialized to TRUE in the element's init function.  The element is actually using FALSE as the default, because it's value is 0.  Unless I'm missing something these defaults need to be configured there.
Comment 1 Tim-Philipp Müller 2017-11-13 17:42:10 UTC
Nicely spotted. Are going to make a patch?
Comment 2 Miki Grof-Tisza 2017-11-13 18:09:13 UTC
I was in the process of creating the patch, when I noticed something.  The properties are created with the flag G_PARAM_CONSTRUCT.  Which actually does the initializing.  I've never used that flag (and didn't know what it does), so I didn't see where it gets initialized.  Also in my testing I checked the actual values in gst_vtenc_init() function which is prior to glib's handling of G_PARAM_CONSTRUCT flag.  If I move my check further into the element's code I see now that it actually works as documented.

So I think this is not a bug.  Sorry for wasting time.
Comment 3 Tim-Philipp Müller 2017-11-13 18:13:23 UTC
Ah right, that would work as well (we usually don't use that flag in GStreamer).

No worries, thanks for double-checking.