[XviD-devel] bug report... or something

[suxen_drol]

On Thu, 24 Apr 2003 13:01:38 +0200 "Robsy" <brecevic at algonet.se> wrote:
> Hi...
> 
> Bug report:
> 
> Platform: MS AVIFile lib + Installable Compression Manager (ICM) driver
> 
> Encoding utility: Virtual dub
> 
> Issue #1:
> 
> The AVIStreamReadFormat function usually requires BITMAPINFOHEADER for a video-stream and a WAVEFORMATEX for audio. Video-files encoded with the latest release of xvid require a buffer for the format structure that FAR! exceeds the size of a BITMAPINFOHEADER (40 bytes) - I think it was something like 120 bytes needed to allocate for the format structure. This is not a problem per se, but I am curious about if you could clarify this anomality. So far I have been able to statically allocate a BITMAPINFOHEADER-structure for all video-streams I have been using for my application, xvid is the first encoder that has given me a reason to dynamically allocate a buffer three times larger than that.
> 
> 
> Issue #2
> 
> Once I fired it of with a dynamically allocated format structure everything is fine, until a call to the ICLocate routine (part of the ICM driver package) returned a NULL-handle, meaning that no decompressor was found so support the format.  192x432 (with different bit depths) all seem to be unsporrted by the ICM - these dimensions are multiples of 16 and SHOULD be supported.XVID is properly installed on my system and Windows Media Player 6.4 lays the same movie with no problems at all. My player has supports other codecs such as different version of indeo (with some restrictions, of course) div3 and div4 (allthough divX 5 seems to be non-compliant with Video For Windows). I am wondering if xvid is compatible with ICM?
> 
> grateful for some answers...

xvid vfw (and divx v502) works fine here with virtualdub, avs2avi (and
flask sometime ago).

which build (stable,latest cvs,dev-api-4) are you using?

-- pete