|
|
|
| This page describes the process and functions used to encode Opus | |
| This page describes the process and functions used to decode Opus | |
| The repacketizer can be used to merge multiple Opus packets into a single packet or alternatively to split Opus packets that have previously been merged | |
These are convenience macros for use with the opus_encode_ctl interface | |
These macros are used with the opus_decoder_ctl and opus_encoder_ctl calls to generate a particular request | |
| These are convenience macros that are specific to the opus_multistream_encoder_ctl() and opus_multistream_decoder_ctl() interface | |
| The multistream API allows individual Opus streams to be combined into a single packet, enabling support for up to 255 channels | |
| Opus Custom is an optional part of the Opus specification and reference implementation which uses a distinct API from the regular API and supports frame sizes that are not normally supported. Use of Opus Custom is discouraged for all but very special applications for which a frame size different from 2.5, 5, 10, or 20 ms is needed (for either complexity or latency reasons) and where interoperability is less important |
| For more information visit the Opus Website. |
©2014 Generated on Sun Jan 5 2014 23:29:55 for Opus by doxygen 1.8.5 |