[XviD-devel]
0.9.2 released and important fixes for MPEG4 compliance in other branches.
Edouard Gomez
ed.gomez at free.fr
Mon Jul 28 19:11:24 CEST 2003
First the announce of 0.9.2.
It is available there at the moment and should be uploaded to xvid.org
servers later:
http://ed.gomez.free.fr/xvid-0.9.2/
------------------------------------------------------------------------
We know you are all waiting for XviD 1.0, but there's still work on the
queue that needs to be done before we can lable XviD as a symbolic 1.0
version.
Work on devapi3 and now devapi4 lead to some important bugfixes in the
0.9.x series and we think it's important to release a last version that
definitevely closes that branch of development.
This is a bugfix release only:
- Fixed unaligned bitstream read on platforms that don't support
unaligned memory access (among them ARM).
- Fixed build system for Unix platforms, XviD is now built as
libxvidcore.so.major.minor where major and minor are the API
version. The soname is mapped to libxvidcore.so.major, all releases
with the same major API number will be binary compatible. For this
release major=2, minor=1. XviD 1.0.x series will use major=4
minor=?.
- Fixed wrong "video_object_type_indication" and possible wrong byte
paddings in the VOL header. Note that these bugs do not hurt usual
decoders (even reference software did not detect these errors).
- Fixed a bitstream error in VOP ending (4 erroneous Oxff bytes instead
of a next_start_code().
- Changed default lignment on 64 bit platform for better perfomance.
- Added a MacOSX module building process for transcode users.
- Removed SCO Unix System V code from XviD ;-)
You can download it in the "Download section" or use the cvs tag
release-0_9_2.
------------------------------------------------------------------------
Then a message about bitstream changes in cvshead and devapi4...
i just commited the VOL & padding fixes so it's really important to
upgrade your libs with a fresh checkout/update to obtain a compliant
bitstream.
Note that buggy bitstreams are likely to be decoded w/o much trouble
(otherwise we would have known about the errors before...) but it's
still better to have a 100% compliant bitstream.
So now we end up with:
XviD bitstreams with version 15 are created by cvshead builds.
XviD bitstreams with version 16 are created by devapi4 builds.
--
Edouard Gomez
More information about the XviD-devel
mailing list