> I think that writing a specification myself is the best possible action
to achieve this goal.
Specifications are neat things. Especially for programmers who have little
knowledge/desire of/for the underlying math. For example:
*Analog specification*. The recommended analog requirements for the Codec2
coder are for a nominal bandwidth ranging from 100 Hz to 3800 Hz. To ensure
proper operation of the Codec2 coder, the A-D conversion process should
produce peak values of (or near) -32768 and 32767. Additionally, the coder
should have unity gain, which means that the output speech level should
match that of the input speech.
The specifications could be greatly simplified, in that the codec2 library
contains a lot of code that will never be used. The only two vocoders that
have been implemented with an user interface, are the 1300 bit/s, and the
700 bit/s. All the other vocoders are academic, and of no use to
implementer's.
There is a lot of common code though. Mostly the codebooks and method of
quantization being the difference.
Onward...
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Freetel-codec2 mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freetel-codec2
