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 760526 - volume element: when volume property set by gst_timed_value_control_source_set it is 10x expected value
volume element: when volume property set by gst_timed_value_control_source_se...
Status: RESOLVED DUPLICATE of bug 740502
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
1.4.5
Other Windows
: Normal major
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-01-12 13:50 UTC by Thomas Roos
Modified: 2016-01-12 23:49 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
min example (3.04 KB, text/x-csrc)
2016-01-12 13:50 UTC, Thomas Roos
Details

Description Thomas Roos 2016-01-12 13:50:18 UTC
Created attachment 318869 [details]
min example

volume element: when volume property is set by gst_timed_value_control_source_set it is 10x the expected value. When setting the value by g_object_set is the expected value?!
When setting volume by gst_timed_value_control_source_set on audiotestsrc the value is set correctly, that's why i expect an volume element error!
I attached an min example based on tests/examples/controller

$ GST_DEBUG=2 ./audio-example.exe
0:00:00.029718760  3320   0294B3E0 WARN           audioresample gstaudioresample.c:1537:plugin_init: Orc disabled, can't benchmark int vs. float resampler
0:00:00.030637461  3320   0294B3E0 WARN         GST_PERFORMANCE gstaudioresample.c:1540:plugin_init: orc disabled, no benchmarking done
0:00:05.125310924  3320   0294B3E0 ERROR                default audio-example.c:96:main: val: 10.000000
Comment 1 Tim-Philipp Müller 2016-01-12 23:49:31 UTC
Thanks for the bug report.

This is not a bug however, but intended behaviour, the value range 0-1.0 corresponds to the min-max value of the volume property here, which is 0-10.0, so 1.0 maps to 10.0. Which arguably is confusing, but that's how it was designed.

To make it work as expected, upgrade to 1.6 and use gst_direct_control_binding_new_absolute() instead of gst_direct_control_binding_new().

*** This bug has been marked as a duplicate of bug 740502 ***