Forums

Running G.726 test vector (Newbie)

Started by pavan_gup February 28, 2005


Hi,
I am running the test vectors for G.726 codec on ARM9E. They have
been downloaded from ITU-T website. However, output differs from the
expected output file.

Does anyone have any clue as to why this may be happening. Codec code
has been downloaded from ITU-T site. It has been compiled using ARM9E
compiler and run on its simulator.

Thank You for your help.
Pavan



Pavan--
Well am not sure if I understand enough to comment, but still... have you attempted any optimization (algorithm or file level) on the ITU-T code before testing for bot exactness? If you have, then that is the culprit/clue for you.

But if you have taken virgin ITU-T code and tested it for bit exactness and still experiencing failures, then I think it could be either a:

1] bad download of code or bit vectors
2] Errant bit exactness testing algorithm

--bhooshan
pavan_gup <> wrote: Hi,
I am running the test vectors for G.726 codec on ARM9E. They have
been downloaded from ITU-T website. However, output differs from the
expected output file.

Does anyone have any clue as to why this may be happening. Codec code
has been downloaded from ITU-T site. It has been compiled using ARM9E
compiler and run on its simulator.

Thank You for your help.
Pavan
To
---------------------------------



Hi Pavan,
If you used G726demo.c as wrapper, it assumes input files to be in binary format, whereas test vectors provided ( ALAW, ULAW directory) are in hexadecimal format. Have you converted them to required format before running G726?

Satheesh

>
>
>Hi,
>I am running the test vectors for G.726 codec on ARM9E. They have
>been downloaded from ITU-T website. However, output differs from the
>expected output file.
>
>Does anyone have any clue as to why this may be happening. Codec code
>has been downloaded from ITU-T site. It has been compiled using ARM9E
>compiler and run on its simulator.
>
>Thank You for your help.
>Pavan >




Hi Bhooshan,
Thanks for your reply. I realized that I am reading
the input test vector file as it is ( ascii format).
Hence, data is read incorrectly.

G.726 needs input in form of short data type ( 16
bit).
Now my question is, if the input in ascii form is:

1f0178f2.....

How should this be read in binary format ( short data
type).

short input[];

input[0] = 0x10f1;
input[1] = 0x2f87

Is this the correct way to read data from the input
file. Is there any utility which converts ascii file
to binary ? Note that I am using ARM 9E tools in
little endian format.

Thank You for your help.
Pavan
--- Bhooshan Iyer <> wrote:

> Pavan--
> Well am not sure if I understand enough to comment,
> but still... have you attempted any optimization
> (algorithm or file level) on the ITU-T code before
> testing for bot exactness? If you have, then that is
> the culprit/clue for you.
>
> But if you have taken virgin ITU-T code and tested
> it for bit exactness and still experiencing
> failures, then I think it could be either a:
>
> 1] bad download of code or bit vectors
> 2] Errant bit exactness testing algorithm
>
> --bhooshan
> pavan_gup <> wrote: > Hi,
> I am running the test vectors for G.726 codec on
> ARM9E. They have
> been downloaded from ITU-T website. However, output
> differs from the
> expected output file.
>
> Does anyone have any clue as to why this may be
> happening. Codec code
> has been downloaded from ITU-T site. It has been
> compiled using ARM9E
> compiler and run on its simulator.
>
> Thank You for your help.
> Pavan >
> To >
> ---------------------------------
>
__________________________________
Celebrate Yahoo!'s 10th Birthday!
Yahoo! Netrospective: 100 Moments of the Web
http://birthday.yahoo.com/netrospective/