Capturing/Playback a sequence of AVI's seamlessly ?

[Hartwig =?iso-8859-1?Q?W=F6llstein?=]

Dear Ray Mercer,

first of all a big big Thank you for EzVidCap and EzAVI. They are
really really great.
With your OCX it's incredibly easy to put so much functionality in a
Playback application and Capturing with your VBversion of Vidcap32 is a
big goal !!

I'm having a great problem with the fact that VFW can capture/playback
only files smaller than
2Gigabyte (or just 1Gb with ezAvi).
That means that I can only capture/playback for about 8min (4min) at
4Mb/s. Is there any way to get a workaround to this problem, e.g. like
Capturing into a sequence of AVI's, that means to immediately begin
writing into a second file when the first has reached it's Sizelimit?
(Opening the 2nd file before the 1st is full, and keep on writing, just
"jumping" from one file to the next)

If that's possible somehow, does it also work this way with Playback?

Thankful for any kind of help,
Hartwig


P.S.: I posted this question in the Newsgroup vb.multimedia_graphics
too, because I think I'm probably not the only one running into that
problem. Just to make sure you really get it, I sent it to your email
adress at macnica as well. (Sorry for the spam...I'm already getting
desperate...)

[Ray Mercer]

"Hartwig Wöllstein" <woellste@rz.fh-muenchen.de> wrote in message
news:3B203686.14B64BDC@rz.fh-muenchen.de...
> Dear Ray Mercer,
>
> first of all a big big Thank you for EzVidCap and EzAVI. They are
> really really great.
> With your OCX it's incredibly easy to put so much functionality in a
> Playback application and Capturing with your VBversion of Vidcap32 is a
> big goal !!

Thanks for the plug! ;-)

> I'm having a great problem with the fact that VFW can capture/playback
> only files smaller than
> 2Gigabyte (or just 1Gb with ezAvi).

This was a limitation in the original AVI file format itself (since there
weren't even disk partitions greater than 2GB when it was first defined. Sorry,
I don't have any VB samples of workarounds to this available at this time. The
C samples you mentioned are all I know about (besides what is in the MSDN and
KBase.

HTH,
Ray Mercer
www.shrinkwrapvb.com

[Hartwig =?iso-8859-1?Q?W=F6llstein?=]

Thanks for your reply,
I'm currently studying your AVITutorials and congratulations to the work you've done
wrapping the C stuff for VB-use, it's really exciting and helps me understanding,
comparing e.g. mAVIDecs and VFW.h.

Can you help me how to get an AVIFile to which I have the pointers pAVIFile and
pAVIStream to play, like passing them to the right API's for playback?
That means, I want to open 2 AVI's , get the pointers to the File and Stream for
each file, pass pAVIFile and pAVIStream of the first AVI to the Playback function,
and when numFrames is reached I pass the pointers of the second AVI to those
Playback functions without having to disconnect the hardware. Maybe this is fast
enough to achieve seamless Playback of two (or more) AVI's in a row.

(When using your control ezAVI2.ocx or using MCI comands, I can only call Macros
that connect and disconnect the hardware resources for each file separately.)

Do you think that's possible, and can you give me a hint which functions I have to
call to get AVI Playback this way?


Sincerely,
Hartwig Woellstein



Ray Mercer wrote:

> "Hartwig Wöllstein" <woellste@rz.fh-muenchen.de> wrote in message
> news:3B203686.14B64BDC@rz.fh-muenchen.de...
> > Dear Ray Mercer,
> >
> > first of all a big big Thank you for EzVidCap and EzAVI. They are
> > really really great.
> > With your OCX it's incredibly easy to put so much functionality in a
> > Playback application and Capturing with your VBversion of Vidcap32 is a
> > big goal !!
>
> Thanks for the plug! ;-)
>
> > I'm having a great problem with the fact that VFW can capture/playback
> > only files smaller than
> > 2Gigabyte (or just 1Gb with ezAvi).
>
> This was a limitation in the original AVI file format itself (since there
> weren't even disk partitions greater than 2GB when it was first defined. Sorry,
> I don't have any VB samples of workarounds to this available at this time. The
> C samples you mentioned are all I know about (besides what is in the MSDN and
> KBase.
>
> HTH,
> Ray Mercer
> www.shrinkwrapvb.com