I got the G 729 ITU-T C code compiled and running. I'm confused about two
issues though.
1) Why is the file size of the encoder output the same/or about same as the
input. (I used a PCM 8000Mhz file for input) Shouldn't this file come out
quite smaller, to the order of 1/8 th the size?
2) I have a sample encoded file from a vendor that does not decode even though I
know it to be valid 729 A.
File Size
Started by ●July 24, 2007
Reply by ●December 11, 20072007-12-11
the reference code source writes out one bit in one byte. the code
source is intended only for simulation and test.
it needs some works to obtain the compressed version. google for it,
you ll find a suitable implementation for you.
nacer
--- In s..., thanneman@... wrote:
>
> I got the G 729 ITU-T C code compiled and running. I'm confused
about two issues though.
>
> 1) Why is the file size of the encoder output the same/or about same
as the input. (I used a PCM 8000Mhz file for input) Shouldn't this
file come out quite smaller, to the order of 1/8 th the size?
>
> 2) I have a sample encoded file from a vendor that does not decode
even though I know it to be valid 729 A.
>
source is intended only for simulation and test.
it needs some works to obtain the compressed version. google for it,
you ll find a suitable implementation for you.
nacer
--- In s..., thanneman@... wrote:
>
> I got the G 729 ITU-T C code compiled and running. I'm confused
about two issues though.
>
> 1) Why is the file size of the encoder output the same/or about same
as the input. (I used a PCM 8000Mhz file for input) Shouldn't this
file come out quite smaller, to the order of 1/8 th the size?
>
> 2) I have a sample encoded file from a vendor that does not decode
even though I know it to be valid 729 A.
>