In this article, we will thoroughly explore the phenomenon of Internet Low Bitrate Codec and its implications in today's society. From its origin to its possible future consequences, we will analyze in detail each aspect related to Internet Low Bitrate Codec, with the aim of providing a comprehensive and complete vision of this topic. Through collecting data, reviewing studies, and consulting experts, we aim to shed light on Internet Low Bitrate Codec and offer an informed and enriching perspective for our readers. Read on to discover everything you need to know about Internet Low Bitrate Codec and its relevance in the contemporary world.
Filename extension | |
---|---|
Internet media type | |
Magic number | '#!iLBC30\n' or '#!iLBC20\n' |
Developed by | Global IP Solutions, now Google Inc |
Initial release | 2004 |
Type of format | Audio compression format |
Standard | RFC 3951 |
Developer(s) | Global IP Solutions, now Google Inc |
---|---|
Initial release | 2004 |
Written in | C |
Operating system | Cross-platform |
Type | Audio codec, reference implementation |
License | 3-clause BSD |
Website | https://webrtc.org/license/ilbc-freeware |
Internet Low Bitrate Codec (iLBC) is a royalty-free narrowband speech audio coding format and an open-source reference implementation (codec), developed by Global IP Solutions (GIPS) formerly Global IP Sound (acquired by Google Inc in 2011). It was formerly freeware with limitations on commercial use, but since 2011 it is available under a free software/open source (3-clause BSD license) license as a part of the open source WebRTC project. It is suitable for VoIP applications, streaming audio, archival and messaging. The algorithm is a version of block-independent linear predictive coding, with the choice of data frame lengths of 20 and 30 milliseconds. The encoded blocks have to be encapsulated in a suitable protocol for transport, usually the Real-time Transport Protocol (RTP).
iLBC handles lost frames through graceful speech quality degradation. Lost frames often occur in connection with lost or delayed IP packets. Ordinary low-bitrate codecs exploit dependencies between speech frames, which cause errors to propagate when packets are lost or delayed. In contrast, iLBC-encoded speech frames are independent and so this problem will not occur.
iLBC is defined in RFC 3951. It is one of the codecs used by Gizmo5, WebRTC, Ekiga, Google Talk, Maemo Recorder (on the Nokia N800/N810), Polycom IP Phone, Cisco, QuteCom, Tuenti, Yahoo! Messenger, Ooma and many others.
iLBC was submitted to IETF in 2002 and the final specification was published in 2004.