diff options
author | Frédéric Brière <fbriere@fbriere.net> | 2019-07-06 15:40:56 -0400 |
---|---|---|
committer | Frédéric Brière <fbriere@fbriere.net> | 2020-03-29 11:49:04 -0400 |
commit | 46bee14d3cc49d4fb49eaf36a29dbcc7a11a5ab7 (patch) | |
tree | 795578907f6da6d66b7421beed198d30f385e0dc /src/parser | |
parent | 8767538e965849dd9c4b9693007fdf05a886aa5c (diff) | |
download | twinkle-46bee14d3cc49d4fb49eaf36a29dbcc7a11a5ab7.tar twinkle-46bee14d3cc49d4fb49eaf36a29dbcc7a11a5ab7.tar.gz twinkle-46bee14d3cc49d4fb49eaf36a29dbcc7a11a5ab7.tar.lz twinkle-46bee14d3cc49d4fb49eaf36a29dbcc7a11a5ab7.tar.xz twinkle-46bee14d3cc49d4fb49eaf36a29dbcc7a11a5ab7.zip |
Add support for the new bcg729 API, introduced in version 1.0.2
Starting with version 1.0.2, bcg729 has changed its API to add support
for G.729B, thus requiring us to adjust our function calls depending on
which version is installed.
When dealing with the new API, we merely need to add a few parameters to
disable all G.729B features, namely:
* On the decoder side: When `SIDFrameFlag` is not set, the decoder will
behave just like before, decoding the payload as a standard G.729A
voice frame (or concealing an erased frame). The other parameters,
`rfc3389PayloadFlag` and `bitStreamLength`, are only of use when
dealing with a SID frame sent as per RFC 3389, and are ignored if
`SIDFrameFlag` is not set.
* On the encoder side: When `enableVAD` is disabled, the encoder will
behave just like before, producing only standard G.729A voice frames.
The only API difference is the introduction of `*bitStreamLength`, to
return the length of the encoded frame (0, 2 or 10 bytes). In our
case, this will always be 10 bytes just like before; an assert() was
added to guarantee this.
Closes #104
Diffstat (limited to 'src/parser')
0 files changed, 0 insertions, 0 deletions