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 659110 - Theoraenc exposes 4 independent settings for VP3 compatibility
Theoraenc exposes 4 independent settings for VP3 compatibility
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
git master
Other Linux
: Normal enhancement
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on: 522205
Blocks:
 
 
Reported: 2011-09-15 01:50 UTC by Jean-François Fortin Tam
Modified: 2018-05-04 11:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jean-François Fortin Tam 2011-09-15 01:50:18 UTC 
The theora codec, as can be seen in pitivi, exposes 4 different switches that govern VP3 compatibility:
- vp3 compatibility
- frame dropping
- capping of bit reservoirs overflows
- capping of bit reservoirs underflows

Strictly speaking they are independent settings, but in practice it only makes sense if they are all on or all off at once. 

It would make a lot more sense, for end users, that they be a single property.
Comment 1 David Schleef 2011-09-17 19:53:37 UTC 
No, it would make more sense not to show any of those to end users.  They're not at all relevant, and the defaults are correct.
Comment 2 Vincent Penquerc'h 2012-01-18 12:30:13 UTC 
Drop frames might be useful.
It's not particular to VP3 compatibility (though its implementation is), and I  believe (eg) Youtube fails to properly convert a Theora stream with drop frames, which is true by default.
Comment 3 Tim-Philipp Müller 2012-02-06 10:28:16 UTC 
> No, it would make more sense not to show any of those to end users.

See bug #522205 for USER_EDITABLE or EXCLUDE_FROM_UI_HINT or so param spec flag to signal this. I think we just need to decide on the right name really..
Comment 4 Tim-Philipp Müller 2012-06-28 22:10:39 UTC 
Don't see what the bug is here, so marking as enhancement.

Anything we should change with these properties in 0.11 ? Remove? Rename? Make flags?
Comment 5 Edward Hervey 2018-05-04 11:09:36 UTC 
Closing after 6 years of inactivity. Was ported as is and issue isn't clear. Please re-open if you have more details and clear explanation of what should be done.