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 750545 - glfilter: Lost frame rate info when fixate caps.
glfilter: Lost frame rate info when fixate caps.
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
git master
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-06-08 09:13 UTC by kevin
Modified: 2018-05-06 13:04 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
patch to fix the issue. (1.63 KB, patch)
2015-06-08 09:15 UTC, kevin 		none Details | Review

Description kevin 2015-06-08 09:13:27 UTC 
Lost frame rate info when fixate caps in gstglfilter.c. It will cause down stream element fail, such avimux. Attach patch to fix it.
Comment 1 kevin 2015-06-08 09:15:39 UTC 
Created attachment 304754 [details] [review]
patch to fix the issue.
Comment 2 Sebastian Dröge (slomo) 2015-06-08 11:55:19 UTC 
Why does it get rid of the framerate in the caps at all? That seems like the main cause for this problem and should be fixed.
Comment 3 kevin 2015-06-09 06:18:56 UTC 
Seems still will lost other fields. Do need   result = gst_caps_intersect (othercaps, caps);? And then add needed fields.
Comment 4 Sebastian Dröge (slomo) 2015-06-09 07:58:22 UTC 
Intersecting with the other caps, or a superset of the other caps (with fields we can convert or want to change) probably makes sense here, yes.
Comment 5 Tim-Philipp Müller 2018-02-08 20:27:27 UTC 
Is this still an issue?

At least looking at the debug log and playing with some simple pipelines it seems like the framerate field is maintained.
Comment 6 Matthew Waters (ystreet00) 2018-05-06 13:03:54 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!