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 670608 - [0.11] Schroenc should have force-profile settings moved to caps
[0.11] Schroenc should have force-profile settings moved to caps
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
0.11.x
Other Linux
: Normal normal
: 0.11.x
Assigned To: Tim-Philipp Müller
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-02-22 13:18 UTC by Christian Fredrik Kalager Schaller
Modified: 2012-09-03 18:32 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Christian Fredrik Kalager Schaller 2012-02-22 13:18:25 UTC 
The options of the force-profile property should be in the caps, like we do for other profiles and other codecs.
Comment 1 Tim-Philipp Müller 2012-02-22 14:20:42 UTC 
What's the difference between "profile" and "force-profile" ?

schroenc's property descriptions are a bit lacking really.
Comment 2 David Schleef 2012-02-22 19:36:47 UTC 
"profile" is the profile actually used, based on any restrictions that may be chosen, and is read-only.  "force-profile" is read/write and has the highest priority setting any restrictions to get a particular profile.
Comment 3 Tim-Philipp Müller 2012-09-03 18:32:35 UTC 
commit bc93340fd4cb3893ce2b0ff9ea87201588d8546e
Author: Tim-Philipp Müller <tim@centricular.net>
Date:   Mon Sep 3 14:04:40 2012 +0100

    schroenc: configure profile/level from allowed downstream caps instead of properties
    
    This is how it's done elsewhere and works better with encodebin.
    
    Removes "force-profile" property, read-only "profile" property and
    "level" property.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=670608