[Bug 672019] rtph264pay restricts sinkpad caps before linking (regression)
GStreamer (bugzilla.gnome.org)
bugzilla at gnome.org
Tue Mar 13 15:10:21 PDT 2012
https://bugzilla.gnome.org/show_bug.cgi?id=672019
GStreamer | gst-plugins-good | git
Olivier Crete (Tester) <olivier.crete> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |olivier.crete at ocrete.ca
--- Comment #2 from Olivier Crete (Tester) <olivier.crete at ocrete.ca> 2012-03-13 22:10:18 UTC ---
I'm afraid that this will might still yield the wrong thing.. As the encoder
could still send something that the other side can't accept.
I guess that in your usecase, you should have a capsfilter after the payloader
with something like this where you state which profiles are acceptable (as I'm
pretty sure you don't want to send the Extended or MultiView profiles):
"application/x-rtp, encoding-name=h264, profile-level-id=423200; # baseline
level 5.0
application/x-rtp, encoding-name=h264, profile-level-id=4D3200; # main, level
5.0
application/x-rtp, encoding-name=h264, profile-level-id=643200" # high, level
5.0
I agree this is a bit annoying, but I can't figure out a better way to do this
as I understand that you're actually getting your media from a file.
As for the level, just put a really high value, I hope that in 0.11, we can put
the actual content as a declaratif profile-level-id in the STREAM_CONFIG sticky
event.
--
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the gstreamer-bugs
mailing list