| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
DV interlaced content is always bottom field first. Fixes #591712.
|
|
|
|
|
|
|
|
|
|
|
| |
framerate is available
For cameras/drivers that don't support e.g. VIDIOC_G_PARM we'd end up without
a framerate and would try to divide by 0, causing run-time warnings and all
frames to be timestamped with 0, which makes sinks that sync against the clock
drop them, causing 'hangs' (observed with the pwc driver and a Logitech QuickCam
Pro 4000). So if we do not know the framerate, simply don't adjust the
timestamps. Fixes #591451.
|
|
|
|
|
|
| |
Clear format list and probed caps when going to NULL so if a new device
is set we'll probe the formats again instead of using previously
detected ones. Fixes bug #591747.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Hook up build infrastructure (autotools, docs, unit test).
|
|
|
|
| |
Fixes #590797
|
|
|
|
|
|
|
| |
Add the NULL caps check where it matters and also cover another case of
potential NULL caps.
Fixes #590030
|
| |
|
|
|
|
|
| |
When we get a BYE packet, don't do lip-sync with the SR inside because some
senders have trouble constructing valid SR packets after BYE.
|
|
|
|
|
|
|
| |
After a BYE packet from a source, stop forwarding the SR packets for lip-sync
to rtpbin. Some senders don't update their SR packets correctly after sending a
BYE and then we break lip-sync. We prefer to let the jitterbuffers drain with
the current lip-sync instead.
|
|
|
|
|
| |
When iterating the sources of a BYE packet, don't signal a reconsideration for
each of them but signal after we handled all sources.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Connect to the pad-removed signal of the ptdemux elements so that we remove the
ghostpads for them. Fixes cleanup when going to NULL as well as when releasing
the sinkpads.
Fixes #561752
|
| |
|
|
|
|
|
|
| |
Remove all individual SDES properties and use one sdes property that takes a
GstStructure instead. This will allow us to add more custom stuff to the SDES
messages later.
|
|
|
|
|
|
| |
Remove all individual SDES properties and use one sdes property that takes a
GstStructure instead. This will allow us to add more custom stuff to the SDES
messages later.
|
| |
|
|
|
|
|
|
|
| |
Add support for sending buffer-lists.
Add unit test for testing that the buffer-list passed through rtpbin.
fixes #585839
|
| |
|
|
|
|
| |
Fixes #584165
|
| |
|
|
|
|
| |
Bring the network address in netowkr byte order to the host order.
|
|
|
|
|
| |
Since the port in GstNetAddress is in network order we might need to byteswap it
before adding it to the source statistics.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Add action signal to clear an SSRC in the ssrc demuxer.
Add signal to notify of removed ssrc.
See #554839
|
|
|
|
|
| |
Since we keep a reference to our ghostpads, we can use them to track sessions.
This avoid us having to mess with the target of the ghostpad.
|
| |
|
|
|
|
|
| |
Allow getting the request pads multiple times, just return the previously
created pads.
|
|
|
|
| |
Add the RTP and RTCP sender addresses in the stats structure.
|
|
|
|
| |
Reuse the RTPSource object property instead of duplicating code.
|
| |
|
|
|
|
|
| |
Add the beginnings of an rtpbin unit test
Add some more stuff to .gitignore
|
|
|
|
|
| |
Set the state on newly added elements to the state of the parent.
Add some debug info and do some cleanups
|
| |
|
|
|
|
| |
See #561752
|
|
|
|
|
|
| |
Keep the signal handlers so they can be disconnected at release time
See #561752
|
|
|
|
| |
Use the right lock when iterating the sessions.
|
|
|
|
|
|
|
|
|
| |
Free the session when all the request pads are released.
Don't mess with the session list in free_session as it is called from a foreach
on that list.
Set the state of the upstream element to NULL first.
See #561752
|
| |
|
| |
|
|
|
|
| |
See #561752
|
|
|
|
| |
See #561752
|
|
|
|
|
|
|
|
| |
We usually only get SR packets in our chain function but if an invalid packet
contains the SR packet after the RR packet, we must not fail but simply ignore
the malformed packet.
Fixes #581375
|
|
|
|
|
|
|
|
|
| |
Since neither rtpmanager nor any of the payloaders properly implement
pad allocation, there is no way for the rtpmanager to inform downstream elements
of the new SSRC if there is an SSRC collision. So the warning is emitted all the
time and it is confusing.
Fixes #580144
|