open source codec with HD
Bretton Vine
Broadcom launches a new codec open source. BV codec was designed from the
ground up to be optimized for voice transmission over IP networks. The main
design goal of BroadVoice was to make the coding delay and codec complexity
as low as possible while maintaining output speech quality as close to
transparent as possible. The following list summarizes the attributes of
BroadVoice16 and BroadVoice32:
[...]
see also http://www.broadcom.com/support/broadvoice/
--
Bretton
openpgp: http://bretton.hivemind.net/bretton_vine.asc
Every one of us is precious in the cosmic perspective. If a human disagrees
with you, let him live. In a hundred billion galaxies, you will not find
another. - Carl Sagan
Raphaël Jacquot
> *delurk* (via link from @RobLith)
>
> http://voiptoday.org/index.php?option=com_content&view=article&id=204:new-open-source-codec-with-hd-quality&catid=46:codec&Itemid=98
>
> Broadcom launches a new codec open source. BV codec was designed from the
> ground up to be optimized for voice transmission over IP networks. The main
> design goal of BroadVoice was to make the coding delay and codec complexity
> as low as possible while maintaining output speech quality as close to
> transparent as possible. The following list summarizes the attributes of
> BroadVoice16 and BroadVoice32:
> [...]
>
> see also http://www.broadcom.com/support/broadvoice/
>
still waiting on documentations for all their chips...
Michael Graves
all to try. I'm very curious to hear what folks have to say once
they've had a look through the source. A very early comment from one of
the Freeswitch developers was that there may be issues with it not
being thread safe. Freeswitch has been very quick to implement wideband
codecs in the past.
Michael
Michael Graves
mgraves<at>mstvp.com
http://www.mgraves.org
o713-861-4005
c713-201-1262
sip:mgr...@mstvp.onsip.com
skype mjgraves
Twitter mjgraves
Alexander Chemeris
On Thu, Nov 12, 2009 at 17:06, Michael Graves <mgr...@mstvp.com> wrote:
> The interesting thing is that they have released the C source code for
> all to try. I'm very curious to hear what folks have to say once
> they've had a look through the source. A very early comment from one of
> the Freeswitch developers was that there may be issues with it not
> being thread safe. Freeswitch has been very quick to implement wideband
> codecs in the past.
100% of codecs I've ever seen are not thread-safe, and that's the right
approach. Have you meant it uses global variables for storing a state?
--
Regards,
Alexander Chemeris.