mciavi: MCI_OPEN @NNNN should use an open AVIFile/Stream handle.

[Joerg-Cyril.Hoehle at t-systems.com]

Hi,

MSDN documents (and I verified) that the MCIAVI allows to access an
open AVIFile object via the special name @NN...NN (decimal address).
Conversely,
open @-1024 type avivideo alias a
crashes native at address ffffc000.

This makes it likely that MCIAVI internally uses the AVIFile API (it
might also pull the MMIO file handle out of the AVIFile structure).

Furthermore, other parameters that the MCI exports, e.g.
MCI_ANIM_*_SPEED, map to what the AVIFile objects provide and is not
present in MMIO handling, reinforcing the hypothesis that the MCIAVI
uses the AVIFile API.

Hence mciavi.c should be rewritten to use the AVIFile API.  It's not
in my TODO list but I hope that doing so would prevent a skew that
I've sometimes observed with some apps, where sound and video
rendering do not match after a few seconds.

Regards,
 Jörg Höhle
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-mciavi-MCI_OPEN-NNNN-should-use-an-open-AVIFile-St.patch
Type: application/octet-stream
Size: 2153 bytes
Desc: 0001-mciavi-MCI_OPEN-NNNN-should-use-an-open-AVIFile-St.patch
URL: <http://www.winehq.org/pipermail/wine-patches/attachments/20101112/55e93207/attachment.obj>