d60b240341
H26x shall contain all code common to H26{4,5,6} and H26{4,5,6}
files shall contain format-specific code which is mainly just
NAL unit fragmentation.
This commit also changes the HEVC RTP format name from RTP_FORMAT_HEVC
to RTP_FORMAT_H265 to unify naming with upcoming AVC/VVC support
|
||
|---|---|---|
| .. | ||
| README.md | ||
| binding.cc | ||
| configuration.cc | ||
| custom_timestamps.cc | ||
| deallocation_1.cc | ||
| deallocation_2.cc | ||
| deallocation_3.cc | ||
| receiving_hook.cc | ||
| receiving_poll.cc | ||
| rtcp_hook.cc | ||
| rtcp_poll.cc | ||
| sending.cc | ||
| sending_fragmented.cc | ||
| sending_generic.cc | ||
| srtp_user.cc | ||
| srtp_zrtp.cc | ||
| zrtp_multistream.cc | ||
README.md
uvgRTP example codes
This directory contains a collection of simple and thoroughly commented examples that demonstrate how to use uvgRTP
Basic RTP functionality
How to create a simple RTP sender
How to create a simple RTP receiver (hooking)
NOTE: The hook should not be used for media processing. It should be used as interface between application and library where the frame handout happens.
How to create a simple RTP receiver (polling)
Advanced RTP functionality
How to fragment generic media types
How to configure uvgRTP to send high-quality video
RTCP
How to use RTCP instance (polling)
How to use RTCP instance (hooking)