Re: Avi file size.

[Jez]

"Fred" > wrote in message
...
> On Wed, 9 Apr 2003 12:47:26 +0100, "Jez"
> > wrote:
>
> >
> >"Rick "Nutcase" Rogers" > wrote in message
> ...
> >Hi,
> >
> >The file size limit is related to the file system in use, are you using
> >FAT32 or NTFS? With FAT32, you will run into trouble with larger files.
> >
> >Well, i capture segments onto a win 98 pc, using fat32,
> >then transfer the sections to my other PC for editing running win XP with
> >NTFS,
> >
> >then join all the bits together, but as I said anything over 2 Gbs fails
to
> >run,
> >and 2 Gbs is around 3 mins of video At 320*240 25fps.....
>
> I know that is not true. Maybe you are using a format of avi that
> does that, but I have seen avi files with more than an hour of video
> that take up less than 1 gigabyte.

Yeah, but they would have been compressed.
(The indeo 5.06 format is quite good.)
but the Avi files I have been using have been un-compressed,
hence the large file size. The idea being, do all editing
in un-compressed format, then convert to mpg2 for vcd/svcd playback.
Ah well, more fiddling about to go yet !


--
Ho Hum
Jez

[Jez]

"Fred" > wrote in message
...
> On Wed, 9 Apr 2003 12:47:26 +0100, "Jez"
> > wrote:
>
> >
> >"Rick "Nutcase" Rogers" > wrote in message
> ...
> >Hi,
> >
> >The file size limit is related to the file system in use, are you using
> >FAT32 or NTFS? With FAT32, you will run into trouble with larger files.
> >
> >Well, i capture segments onto a win 98 pc, using fat32,
> >then transfer the sections to my other PC for editing running win XP with
> >NTFS,
> >
> >then join all the bits together, but as I said anything over 2 Gbs fails
to
> >run,
> >and 2 Gbs is around 3 mins of video At 320*240 25fps.....
>
> I know that is not true. Maybe you are using a format of avi that
> does that, but I have seen avi files with more than an hour of video
> that take up less than 1 gigabyte.

Yeah, but they would have been compressed.
(The indeo 5.06 format is quite good.)
but the Avi files I have been using have been un-compressed,
hence the large file size. The idea being, do all editing
in un-compressed format, then convert to mpg2 for vcd/svcd playback.
Ah well, more fiddling about to go yet !


--
Ho Hum
Jez

[Fred]

On Thu, 10 Apr 2003 14:39:20 +0100, "Jez"
> wrote:
>Yeah, but they would have been compressed.
>(The indeo 5.06 format is quite good.)
>but the Avi files I have been using have been un-compressed,
>hence the large file size. The idea being, do all editing
>in un-compressed format, then convert to mpg2 for vcd/svcd playback.
>Ah well, more fiddling about to go yet !

OK. Hopefully the site you recommended will explain some of this.

[Fred]

On Thu, 10 Apr 2003 14:39:20 +0100, "Jez"
> wrote:
>Yeah, but they would have been compressed.
>(The indeo 5.06 format is quite good.)
>but the Avi files I have been using have been un-compressed,
>hence the large file size. The idea being, do all editing
>in un-compressed format, then convert to mpg2 for vcd/svcd playback.
>Ah well, more fiddling about to go yet !

OK. Hopefully the site you recommended will explain some of this.

[Jez]

"Digger" > wrote in message
...
> Regarding analog (VFW) AVI filesizes:
>
> FAT16 + AVI = 2GB filesize limit.
> FAT32 + Original AVI specification (a.k.a. Old Style Format) = 2GB
filesize
> limit.
> FAT32 + AVI OpenDML 1.02 = 4GB filesize limit.
> NTFS + AVI OpenDML 1.02 = larger than most of us can even imagine. :-)
>
> Note: OpenDML 1.02 extended AVI format is currently supported by VFW
> (analog) MCIAVI decoder.
>
> Minimum requirements for producing analog AVI > 2GB...
> 1. At least a FAT32 partition, NTFS recommended.
> 2. Analog capture and rendering software/ codec must support OpenDML
1.02+.
> 3. If filesize > 4GB and FAT32 partition is necessary, one can use
> multi-segment capturing software as a workaround; i.e. VirtualDub
>
> An uncompressed RGB32 capture to an analog AVI format will render at
> approximately 1.2 GB/min (720x480, 29.97 fps).
>
> MPEG Layer 2 -- NTSC standard (720x480, 29.97 fps, 8 Mb/sec) -- should
> render at roughly 1 MB/sec, or 60 MB/min.
>
> If your MPG-2 filesize is greater than uncompressed RGB32 AVI at
> full resolution, I would suggest that you are correct and something is
> definitely wrong somewhere.
>

Ah-ha....thanks for that !

--
Ho Hum
Jez

[Jez]

"Digger" > wrote in message
...
> Regarding analog (VFW) AVI filesizes:
>
> FAT16 + AVI = 2GB filesize limit.
> FAT32 + Original AVI specification (a.k.a. Old Style Format) = 2GB
filesize
> limit.
> FAT32 + AVI OpenDML 1.02 = 4GB filesize limit.
> NTFS + AVI OpenDML 1.02 = larger than most of us can even imagine. :-)
>
> Note: OpenDML 1.02 extended AVI format is currently supported by VFW
> (analog) MCIAVI decoder.
>
> Minimum requirements for producing analog AVI > 2GB...
> 1. At least a FAT32 partition, NTFS recommended.
> 2. Analog capture and rendering software/ codec must support OpenDML
1.02+.
> 3. If filesize > 4GB and FAT32 partition is necessary, one can use
> multi-segment capturing software as a workaround; i.e. VirtualDub
>
> An uncompressed RGB32 capture to an analog AVI format will render at
> approximately 1.2 GB/min (720x480, 29.97 fps).
>
> MPEG Layer 2 -- NTSC standard (720x480, 29.97 fps, 8 Mb/sec) -- should
> render at roughly 1 MB/sec, or 60 MB/min.
>
> If your MPG-2 filesize is greater than uncompressed RGB32 AVI at
> full resolution, I would suggest that you are correct and something is
> definitely wrong somewhere.
>

Ah-ha....thanks for that !

--
Ho Hum
Jez