Writing Your Own AVI Files

The reason why I deal with AVI-Files is the following: I have a program that does any (long) calculation, and the output is immediately displayed (a function graph). After each step I can save the current window content as bitmap, and after the calculation I added all the bitmaps to an AVI (using VFD.EXE). But the bitmaps take a lot of room, (up to some G-Bytes). Therefore I wanted to create a AVI-File, and add the frames immediately when they are displayed.

The vfw.h reads like a binary file, and so I have tried to press the sample WriteAVI into a C++-class. I don't want to documentate the source code in detail, just add WriteAVI.cpp and WriteAVI.h to your project and use the class.

Some problems there are still with that class:

  1. The user will be prompted to select a compression method, it should be choosen automatically or by parameter.
  2. I create DIB's (not compressed) for adding to an AVI-stream. The resulting AVI-File is not compressed even when I choose a compression method.
  3. The time for a frame is fix.

If anybody knows how to fix the problems please send me a mail, so that everybody can benefit from it.


Then these few lines will create your own AVI-file:

CAVIFile avi("test.avi");
for (int i=0; i<=20; i++)
{
CBitmap bmp;
... // fill with data
avi.AddFrame(bmp);
}
if (avi.IsOK())
AfxMessageBox("AVI created");
else
AfxMessageBox("Error");

You see writing AVI-Files is easy (now).

Download source - 4KB



Comments

  • There are no comments yet. Be the first to comment!

Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • Live Event Date: December 11, 2014 @ 1:00 p.m. ET / 10:00 a.m. PT Market pressures to move more quickly and develop innovative applications are forcing organizations to rethink how they develop and release applications. The combination of public clouds and physical back-end infrastructures are a means to get applications out faster. However, these hybrid solutions complicate DevOps adoption, with application delivery pipelines that span across complex hybrid cloud and non-cloud environments. Check out this …

  • Due to internal controls and regulations, the amount of long term archival data is increasing every year. Since magnetic tape does not need to be periodically operated or connected to a power source, there will be no data loss because of performance degradation due to the drive actuator. Read this white paper to learn about a series of tests that determined magnetic tape is a reliable long-term storage solution for up to 30 years.

Most Popular Programming Stories

More for Developers

RSS Feeds