FaSTTUBe/GST-Tensordecoder-ov_ep
37
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

doc: Trivial spelling and consistency update

Browse Source
This commit is contained in:
Arun Raghavan 2014-11-20 20:18:45 +05:30
parent 3d7b0f30d7
commit a98294f849
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/design/design-rtpretransmission.txt
View File

@ -18,7 +18,7 @@ element when it receives a NACK from the network.
rtprtxsend element rtprtxsend element
------------------ ------------------
-- basic mecansim -- basic mechanism
rtprtxsend keeps a history of rtp packets that it has already sent. rtprtxsend keeps a history of rtp packets that it has already sent.
When it receives the event GstRTPRetransmissionRequest from the downstream When it receives the event GstRTPRetransmissionRequest from the downstream
@ -49,7 +49,7 @@ To choose rtx_ssrc it randomly selects a number between 0 and 2^32-1 until
it is different than master_ssrc. it is different than master_ssrc.
rtx_seqnum is randomly selected between 0 and 2^16-1 rtx_seqnum is randomly selected between 0 and 2^16-1
- deeper in the stored buffer history -- deeper in the stored buffer history
For the history it uses a GSequence with 2^15-1 as its maximum size. For the history it uses a GSequence with 2^15-1 as its maximum size.
Which is resonable as the default value is 100. Which is resonable as the default value is 100.
@ -86,7 +86,7 @@ So that it can be handled by the rtppayloader.
rtprtxreceive element rtprtxreceive element
------------------ ------------------
-- basic mecanims -- basic mechanism
The same rtprtxreceive instance can receive several master streams and several The same rtprtxreceive instance can receive several master streams and several
retransmission streams. retransmission streams.
@ -141,7 +141,7 @@ A stored request actually means that actually the couple seqnum,ssrc is stored.
If it's happens the request is droped but it avoids to do bad associations. If it's happens the request is droped but it avoids to do bad associations.
In this case the association is just delayed to the next request. In this case the association is just delayed to the next request.
- building original packet from rtx packet -- building original packet from rtx packet
Header, extensions, payload and padding are mostly the same. Except that the Header, extensions, payload and padding are mostly the same. Except that the
OSN is removed from the payload. Then ssrc, seqnum, and original payload type OSN is removed from the payload. Then ssrc, seqnum, and original payload type