Hi,
Currently there are no tests in Wine of mciavi or mciqtz. The reason is incredibly trivial: I'd need a test.avi with defined properties that the tests check, and of course the file should be as small as possible to not weight too much in git.
If you happen to know clock.avi (found in some versions of MS-Windows), this comes close. It displays an analog clock with a single clock hand plus numbers from 1 to 12. It ticks one frame per second, showing numbers from 1 to 12 in addition to moving the hand.
What I think would be useful is a video with - frames: key - key - delta - key (if delta is possible) - displaying digits 1 - 2 - 3 - 4 - speed: one frame per second - sound would be very useful, but it might increase the file size a lot (3 seconds of sound...). Perhaps MS-ADPCM might well compress a sound file that beeps, then pauses for most of the rest of every second. Beeps at different frequencies would be best. - simplify graphics to minimize disk space.
Actually, I don't know whether such an animation with 4 frames would play for 3 seconds (final frame displayed at the end) or 4 (final frame displayed for one second, like the others, then stop).
Any volunteer?
How would that be incorporated into winetest.exe? As a resource, copied at execution time to the current directory?
Thank you for your help, Jörg Höhle
On 17 November 2010 09:13, Joerg-Cyril.Hoehle@t-systems.com wrote:
Hi,
How would that be incorporated into winetest.exe? As a resource, copied at execution time to the current directory?
You would add it to the AVI section of the resource block (RC file) for the test executable. That would be the best way, as it keeps the test executable standalone.
- Reece
Joerg-Cyril.Hoehle@t-systems.com wrote:
Currently there are no tests in Wine of mciavi or mciqtz. The reason is incredibly trivial: I'd need a test.avi with defined properties that the tests check, and of course the file should be as small as possible to not weight too much in git.
There is already some test AVI data in the avifil32 tests. I wanted this data to be as small as possible, so I created a 8x6 single frame file and stripped that as much as possible. This file is now generated by the avifil32 tests each time they're run. The create_avi_file function in api.c creates this file using the static data in the same file.
In case you wonder about the source, it's the first frame of AJ's WineConf 2009 keynote after conversion. I cannot imagine anything remotely recognizable is still left in the test data though :)
Regards, Julius