I have a small problem, it's very technical but I hope someone here might know.

I'm generating Matrix-code AVI files using a C++ program I wrote. I'm using the Video for Windows functions. Everything's fine, except when the video is > 2GB (which iit is because they have to be uncompressed, HD - long story).

Anyway, it seems to me the problem is that somewhere there is a "size" variable that is a signed long (31-bits), the maximum value of which can be 2^31.

Short of manually creating uncompressed AVIs, which I can do, does anyone have a better idea?

Thanks a lot!

Peter, are you using Win 98 or the FAT32 file system. Win98 had a problem with files over 2GB and sometimes so does FAT32. If your using W2k or XP try changing your file system to NTFS and give that a go.

Hey Adrian,
Nope, it's NTFS. I long ago learned about the file size limitations of FAT32, so all my drives are NTFS. This is a programming issue. The files physically get larger than 2 GB, but nothing will play them properly.

I got the AVI file spec from MSDN. Making uncompressed AVIs (which I'll then compress with Vegas) shouldn't be too hard.

Peter,

The problem is probably in the matrox codec that is being used
to playback your file. I think one codec of matrix supports spanning
over multiple files, but I'm not sure.

I'd output uncompressed or just plain AVI DV. Keep in mind that
to have a > 2 or > 4 GB AVI file you will need to write a TYPE 2
AVI file!!! **NOT** a type 1. I don't know what the technical
difference is, but I do know you need to use the type 2 format.

Ah, then that's almost certainly the problem. The VFW SDK probably is only creating Type 1 files, not Type 2, but I believe the AVI specs I got from Microsoft explain how to do type 2. Or I can probably find it one way or another.

Outputting multiple files is a great idea, which I can most certainly program my Matrix raining code gemerator to do. Thanks for the suggestion!

It does indeed sound like the signed int problem that Peter is describing. AVIs are RIFF formatted with (originally) a single RIFF section occupying the whole file. The RIFF header contains a 32 bit length field which will only allow files up to approx 2 GB.

Anyway the format was extended (Open-DML standard) to allow multiple RIFF sections and therefore allow a MUCH bigger file size.

The VFW AVI functions do not use the Open-DML extension and so are stuck with a maximum file size of 2GB.

I am using DirectShow which does not have this limitation.

If you need to stick with VFW then you may be able to find some OpenDML AVI parsing code somewhere on the net - in VirtualDub for example.

Rob, I'm not sure what you mean but I *think* that the type 2 AVI file that you are referring to is the Open-DML standard (rather the the DV type 1 or 2)? If so it should really be referred to as an OpenDML AVI to avoid confusion with the DV types which are unrelated.

Hm, interesting. I am actually not using DV, but uncompressed hi-def (otherwise this wouldn't be an issue). That's good to know DirectShow doesn't have this problem. Maybe I'll just use that, should be easy enough. Thanks a lot.

Maybe I'll just use [DirectShow], should be easy enough.

I found quite a steep learning curve with DirectShow, particularly if you are not doing something straightforward. It can be pretty frustrating to work with. Good luck.

I was talking about the AVI's you can create with DirectShow
which Microsoft itself calls TYPE 2 AVI's. Sorry, I didn't make up
the name <g>. I think you are correct in saying that these are
using OpenDML extension indeed (but that is a bit hard to
verify?).

VFW is always TYPE 1 and can indeed not playback the larger
files (in theory it should not even create larger files). DV type 1
and type 2 is a different thing (audio in DV stream or not).

Confusing world...

Colin,
All IU'm doing is generating bitmaps in memory (actually DirectDraw surfaces, because they're fast, but all the same) and turning them into movie frames. It's extremely easy to do that with VFW - seems straightforward enough. Any suggestions for approaching that problem?

Rob,
Yes I read the OpenDML spec and that's exactly what AVI "Type 2" is as MS calls it. Basically all they do is have multiple RIFF chunks in the same file, each of <= 1 GB, so that a legacy player can read the 1st GB worth and advanced players can read the whole thing.

Ah yes, there's quite a good explanation at

http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=39eef896.23073548%40news.freeserve.net

Sounds like your app may be quite simple then. You may just have to write a source filter and feed it into a file writer.