Hi Stefan, Thanks very much for taking the time to review this draft. Stefan Sayer wrote:
My suggestion is to remove the first diagram (anyway it is clear that the payload follows the RTP header), or add the length bytes to it to make clear that this is the usual mode of packetization.
I have followed your suggestion and removed the diagram.
In 5.2. Low-Overhead Mode, the text says:
"One the a=fmtp: parameter low-
overhead: is defined and contains a single frame size, followed by a
'/', followed by a comma-separated list of the number of bytes per
frame for each stream defined in the channel mapping."
but the example gives:
a=fmtp:97 low-overhead=256/1/86,86,43,30;mapping=2,2,1,1/
L,R,LR,RR,C,MLFE/ITU-RBS.775-1
What is the extra /1 supposed to mean in 256/1/86,86,43,30 ?
Sorry. The /1 was a left-over from a previous revision and is no longer necessary. I've removed it now.
Also, a simpler example (e.g. for mono and stereo streams) could be illustrative.
Thanks for the suggestion. I added a plain mono example. The next now reads:
For example a low-overhead 64 kbit/s mono stream could be signaled
as:
m=audio 8008 RTP/AVP 97
a=ptime: 5
a=rtpmap:97 CELT/48000/1
a=fmtp:97 low-overhead=256/43
and a low-overhead 360 kbit/s 5.1 surround configuration could be
signaled as:
m=audio 8008 RTP/AVP 97
a=ptime: 5
a=rtpmap:97 CELT/48000/6
a=fmtp:97 low-overhead=256/86,86,43,25;mapping=2,2,1,1/
L,R,LR,RR,C,MLFE/ITU-RBS.775-1
Cheers,
Jean-Marc