ts-jitterbuffer: fix request-pt-map emission

When a new payload type is encountered, we first check whether
it matches the caps received as an event before emitting the
request-pt-map signal if not, which means we shouldn't consider
errors from the first call to parse_caps as fatal.
This commit is contained in:
Mathieu Duponchelle 2020-03-04 17:20:08 +01:00
parent e5e29b18d1
commit 9e665ae807

View file

@ -665,7 +665,8 @@ impl JitterBuffer {
gst_debug!(CAT, obj: pad, "New payload type: {}", pt); gst_debug!(CAT, obj: pad, "New payload type: {}", pt);
if let Some(caps) = pad.get_current_caps() { if let Some(caps) = pad.get_current_caps() {
self.parse_caps(state, element, &caps, pt)?; /* Ignore errors at this point, as we want to emit request-pt-map */
let _ = self.parse_caps(state, element, &caps, pt);
} }
} }