[Bug 762213] rtpmux: property should overrule both upstream and downstream

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=762213

--- Comment #3 from Håvard Graff (hgr) <havard.graff at gmail.com> ---
(In reply to Olivier Crête from comment #2)
> I think the idea is that the controlling property is in the rtpsession..
> Because it's the one that has to be in control because it knows about SSRC
> collisions. Right now if we have rtp*pay ssrc=X ! rtpmux ssrc=Y ! rtpsession
> ssrc=Z, then the rtpsession one wins I think, if I understand what you're
> proposing, the rtpmux would win ?

Well... If you purposely specify three different properties with three
different values you deserve to end up in a puddle of flow fail. It should be a
given that rtpmux can override any ssrc specified upstream from it, since it
has the power to combine several, and then obviously all upstream ones can't
have their will/ssrc.


Now, the specific reason for this patch is that sometimes rtpbin will generate
a sender-source for you, with a random ssrc. Now, if you *wish* to control what
ssrc you are sending with, using a rtpmux, I would think that setting the
ssrc-property would do just that, given that it is now the *only* ssrc-property
that have been set. Without this patch this might not be the case, since you
will instead be using a randomly generated ssrc from inside rtpbin. Now if you
have the know-how (not so easy) to specify a ssrc directly on rtpsession, I
would hope that you would not *also* try to specify a *different* ssrc on
rtpmux...

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.