vpxenc creates .webm files in incorrect endian on big endian machines

[GoogleCodeExporter]

I am not a programmer so I apologise in advance for not being thorough or using 
correct terms in reporting this issue.

In at least version 0.9.5 and 0.9.6 of libvpx, the encoder example vpxenc (and 
perhaps the simple_encoder too) creates .webm files on a big endian machine in 
big endian (as far as I can tell), as opposed to swapping the endian before 
writing the data.

Comparing the .webm output file against one made in Windows or Linux, the files 
seem to be identical except for the byte-ordering. The library itself seems to 
be OK when used in ffmpeg.

I am using AmigaOS 4.1 (be kind). vpxdec works fine if used with existing .webm 
files, but cannot process the files vpxenc made on the same big endian machine.

Likely the same issue exists when encoding to ivf too.

Original issue reported on code.google.com by mickj...@gmail.com on 13 May 2011 at 9:26

[GoogleCodeExporter]

Original comment by iss...@webmproject.org on 13 May 2011 at 9:30

[GoogleCodeExporter]

Original comment by jkoles...@google.com on 9 Jun 2011 at 6:38

• Added labels: Component-libvpx

[GoogleCodeExporter]

I've had another glance. It looks like it's only the header that has the wrong 
byte-ordering and not the actual video data itself.

Original comment by mickj...@gmail.com on 10 Jun 2011 at 4:31

[GoogleCodeExporter]

Sorry for this late fix. Please check out the git commit - "Fix vpxenc encoding 
incorrect webm file header on big endian machines(Issue 331))(commit: 
c156a68d06ace37b87d91c97774e06c05bee1f08) to see if it works for you.

Yunqing

Original comment by yunqingw...@google.com on 15 Jul 2011 at 12:28

• Changed state: Fixed

[GoogleCodeExporter]

It is fixed.

Original comment by mickj...@gmail.com on 9 Aug 2011 at 10:11