Tree:
d16079abf4
master
n4.4-jackoutdev
oldabi
release/0.10
release/0.11
release/0.5
release/0.6
release/0.7
release/0.8
release/0.9
release/1.0
release/1.1
release/1.2
release/2.0
release/2.1
release/2.2
release/2.3
release/2.4
release/2.5
release/2.6
release/2.7
release/2.8
release/3.0
release/3.1
release/3.2
release/3.3
release/3.4
release/4.0
release/4.1
release/4.2
release/4.3
release/4.4
v0.6.1
v0.6
v0.5.3
v0.5.2
v0.5.1
v0.5
n4.5-dev
n4.4-dev
n4.3-dev
n4.2-dev
n4.1-dev
n3.5-dev
n3.4-dev
n3.3-dev
n3.2-dev
n3.1-dev
n2.9-dev
n2.8-dev
n2.7-dev
n2.6-dev
n2.5-dev
n2.4-dev
n2.3-dev
n2.2-dev
n2.1-dev
n1.3-dev
n1.2-dev
n1.1-dev
n0.12-dev
n0.11-dev
n4.4
n4.3.2
n4.3.1
n4.3
n4.2.4
n4.2.3
n4.2.2
n4.2.1
n4.2
n4.1.6
n4.1.5
n4.1.4
n4.1.3
n4.1.2
n4.1.1
n4.1
n4.0.6
n4.0.5
n4.0.4
n4.0.3
n4.0.2
n4.0.1
n4.0
n3.4.8
n3.4.7
n3.4.6
n3.4.5
n3.4.4
n3.4.3
n3.4.2
n3.4.1
n3.4
n3.3.9
n3.3.8
n3.3.7
n3.3.6
n3.3.5
n3.3.4
n3.3.3
n3.3.2
n3.3.1
n3.3
n3.2.15
n3.2.14
n3.2.13
n3.2.12
n3.2.11
n3.2.10
n3.2.9
n3.2.8
n3.2.7
n3.2.6
n3.2.5
n3.2.4
n3.2.3
n3.2.2
n3.2.1
n3.2
n3.1.11
n3.1.10
n3.1.9
n3.1.8
n3.1.7
n3.1.6
n3.1.5
n3.1.4
n3.1.3
n3.1.2
n3.1.1
n3.1
n3.0.12
n3.0.11
n3.0.10
n3.0.9
n3.0.8
n3.0.7
n3.0.6
n3.0.5
n3.0.4
n3.0.3
n3.0.2
n3.0.1
n3.0
n2.8.17
n2.8.16
n2.8.15
n2.8.14
n2.8.13
n2.8.12
n2.8.11
n2.8.10
n2.8.9
n2.8.8
n2.8.7
n2.8.6
n2.8.5
n2.8.4
n2.8.3
n2.8.2
n2.8.1
n2.8
n2.7.7
n2.7.6
n2.7.5
n2.7.4
n2.7.3
n2.7.2
n2.7.1
n2.7
n2.6.9
n2.6.8
n2.6.7
n2.6.6
n2.6.5
n2.6.4
n2.6.3
n2.6.2
n2.6.1
n2.6
n2.5.11
n2.5.10
n2.5.9
n2.5.8
n2.5.7
n2.5.6
n2.5.5
n2.5.4
n2.5.3
n2.5.2
n2.5.1
n2.5
n2.4.14
n2.4.13
n2.4.12
n2.4.11
n2.4.10
n2.4.9
n2.4.8
n2.4.7
n2.4.6
n2.4.5
n2.4.4
n2.4.3
n2.4.2
n2.4.1
n2.4
n2.3.6
n2.3.5
n2.3.4
n2.3.3
n2.3.2
n2.3.1
n2.3
n2.2.16
n2.2.15
n2.2.14
n2.2.13
n2.2.12
n2.2.11
n2.2.10
n2.2.9
n2.2.8
n2.2.7
n2.2.6
n2.2.5
n2.2.4
n2.2.3
n2.2.2
n2.2.1
n2.2
n2.2-rc2
n2.2-rc1
n2.1.8
n2.1.7
n2.1.6
n2.1.5
n2.1.4
n2.1.3
n2.1.2
n2.1.1
n2.1
n2.0.7
n2.0.6
n2.0.5
n2.0.4
n2.0.3
n2.0.2
n2.0.1
n2.0
n1.2.12
n1.2.11
n1.2.10
n1.2.9
n1.2.8
n1.2.7
n1.2.6
n1.2.5
n1.2.4
n1.2.3
n1.2.2
n1.2.1
n1.2
n1.1.16
n1.1.15
n1.1.14
n1.1.13
n1.1.12
n1.1.11
n1.1.10
n1.1.9
n1.1.8
n1.1.7
n1.1.6
n1.1.5
n1.1.4
n1.1.3
n1.1.2
n1.1.1
n1.1
n1.0.10
n1.0.9
n1.0.8
n1.0.7
n1.0.6
n1.0.5
n1.0.4
n1.0.3
n1.0.2
n1.0.1
n1.0
n0.11.5
n0.11.4
n0.11.3
n0.11.2
n0.11.1
n0.11
n0.10.16
n0.10.15
n0.10.14
n0.10.13
n0.10.12
n0.10.11
n0.10.10
n0.10.9
n0.10.8
n0.10.7
n0.10.6
n0.10.5
n0.10.4
n0.10.3
n0.10.2
n0.10.1
n0.10
n0.9.4
n0.9.3
n0.9.2
n0.9.1
n0.9
n0.8.15
n0.8.14
n0.8.13
n0.8.12
n0.8.11
n0.8.10
n0.8.9
n0.8.8
n0.8.7
n0.8.6
n0.8.5
n0.8.4
n0.8.3
n0.8.2
n0.8.1
n0.8
n0.7.17
n0.7.16
n0.7.15
n0.7.14
n0.7.13
n0.7.12
n0.7.11
n0.7.10
n0.7.9
n0.7.8
n0.7.7
n0.7.6
n0.7.5
n0.7.4
n0.7.3
n0.7.2
n0.7.1
n0.6.7
n0.6.6
n0.6.5
n0.6.4
ffmpeg-0.6.3
n0.5.15
n0.5.14
n0.5.13
n0.5.12
n0.5.11
n0.5.10
n0.5.9
n0.5.8
n0.5.7
n0.5.6
n0.5.5
N
4 Commits (d16079abf473b51be7686d20f8014bb48a095722)
4 Commits (d16079abf473b51be7686d20f8014bb48a095722)
| Author | SHA1 | Message | Date |
|---|---|---|---|
 Thomas Volkert
|
e1cddd1a0c |
rtpenc_h263_rfc2190: avoid misleading error output
Signed-off-by: Michael Niedermayer <michaelni@gmx.at> |
10 years ago |
 Thilo Borgmann
|
d814a839ac | Reinstate proper FFmpeg license for all files. | 12 years ago |
 Martin Storsjö
|
984b914c55 |
rtpenc: Use MB info side data for splitting H263 packets for RFC 2190
This makes the packetization spec compliant for cases where one single GOB doesn't fit into an RTP packet. Signed-off-by: Martin Storsjö <martin@martin.st> |
13 years ago |
|
Martin Storsjö
|
c4584f3c1f |
rtpenc: Allow packetizing H263 according to the old RFC 2190
According to newer RFCs, this packetization scheme should only be used for interfacing with legacy systems. Implementing this packetization mode properly requires parsing the full H263 bitstream to find macroblock boundaries (and knowing their macroblock and gob numbers and motion vector predictors). This implementation tries to look for GOB headers (which can be inserted by using -ps <small number>), but if the GOBs aren't small enough to fit into the MTU, the packetizer blindly splits packets at any offset and claims it to be a GOB boundary (by using Mode A from the RFC). While not correct, this seems to work with some receivers. Signed-off-by: Martin Storsjö <martin@martin.st> |
13 years ago |