UEMCLIP: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
(2 intermediate revisions by 2 users not shown) | |||
Line 2: | Line 2: | ||
* Company: [[NTT]] | * Company: [[NTT]] | ||
* Description: http://uemclip.com/doc/HighLevelDescription.pdf | * Description: http://uemclip.com/doc/HighLevelDescription.pdf | ||
* Sample: http://uemclip.com/data/UEMCLIP.wav | * Sample: http://uemclip.com/data/UEMCLIP.wav (decoded UEMCLIP to pcm) | ||
* RTP payload format: https://tools.ietf.org/html/draft-ietf-avt-rtp-uemclip | |||
UEMCLIP (mU-law EMbedded Coder for Low-delay IP communication) is [[μ-law]]-based voice codec. | UEMCLIP (mU-law EMbedded Coder for Low-delay IP communication) is [[μ-law]]-based voice codec. This codec is base of [[G.711.1]] [https://www.ntt-review.jp/archive/ntttechnical.php?contents=ntr200808le1.html]. | ||
The RTP payload format document describes the data packets and chapter 4 explains the transcoding possibility between G.711 and UEMCLIP. It is mentioned here that sub layer index 0 is standard G.711 data, but this sub layer block might or might not follow immediately the headers (so the sub layer headers must be parsed). | |||
[[Category:Audio Codecs]] | [[Category:Audio Codecs]] | ||
[[Category:Vocoders]] | [[Category:Vocoders]] | ||
[[Category:Undiscovered Audio Codecs]] | [[Category:Undiscovered Audio Codecs]] | ||
[[Category:MDCT Audio Codecs]] |
Latest revision as of 17:12, 29 January 2011
- Website: http://uemclip.com/English/index_e.htm
- Company: NTT
- Description: http://uemclip.com/doc/HighLevelDescription.pdf
- Sample: http://uemclip.com/data/UEMCLIP.wav (decoded UEMCLIP to pcm)
- RTP payload format: https://tools.ietf.org/html/draft-ietf-avt-rtp-uemclip
UEMCLIP (mU-law EMbedded Coder for Low-delay IP communication) is μ-law-based voice codec. This codec is base of G.711.1 [1].
The RTP payload format document describes the data packets and chapter 4 explains the transcoding possibility between G.711 and UEMCLIP. It is mentioned here that sub layer index 0 is standard G.711 data, but this sub layer block might or might not follow immediately the headers (so the sub layer headers must be parsed).