AVI_IO says No More Disk Space with 41GB left

[NIRVANAX5X]

I'm capturing 704x480 with huffyuv in AVI_IO. The video is like 80 Min long. I had about 84GB left on my storage hdd. I was capping the video fine and then 55 Min into it exactly it stops and says something to the effect of no more disks found/space and stops. The capture so far took up 43.5GB and there is 41GB left on the hdd what is the problem?

-Thanks!
if you could reply asap that would be well

[Soopafresh]

A few possibilities (and they're semi educated guesses)

A bug in Windows or the Capture App or the Huffy Codec that creates the condition

Running out of RAM or swapfile space during the capture due to a bug in the software or in Windows (see the first reason)

I'll bet you exhausted the resources of the OS after an hour of consistent capturing, encoding, and copying video onto your system.

Solutions?

1) Run Chkdsk /f from the command prompt on your capture drives.

2) Resize your swapfile to a larger size - add 512MB to the current number.

3) There's a series of registry modifications you can run to optimize your system for better I/O - http://www.winguides.com/registry/display.php/1265/

4) Apply the post SP2 fixes from http://www.autopatcher.com or Windows Update.

[NIRVANAX5X]

A few possibilities (and they're semi educated guesses)

Solutions?

1) Run Chkdsk /f from the command prompt on your capture drives.
Usually does this whenever I boot up and defraged a few times before final capture.

2) Resize your swapfile to a larger size - add 512MB to the current number.
Done.

3) There's a series of registry modifications you can run to optimize your system for better I/O - http://www.winguides.com/registry/display.php/1265/
Done.

4) Apply the post SP2 fixes from http://www.autopatcher.com or Windows Update.
Think I manually did this.

Thanks a lot for the help frankly I'm a bit afraid to even try to capture past 55 Min now but I have to. I added a different folder on the same drive to AVI_IO so when the first fills it should use the other would this fix it?

Thanks again Soopafresh

[vhelp]

Actually.., avi_io buffers by creating in advance, as many AVI
files (length set to zero) for a given capture job. I'm not sure
how it "calculates" the space and then create as many "zero lenght"
avi files prior to your capturing.
.
But, I think that the amximum (due to FAT32 limitation) is about
4gigs per avi file (ie, cap001.avi; cap002.avi; cap003.avi ... etc)
Remember, it does not set the actual size when it creates all those
files. They are "zero length". But, as it captures, each one of
those segments become full and then closed, and another segmented
opened and begins filling that one segent, and so on, and so on.. until
there are no more "segments" left, or until it runs out of "calculated
space" or just runs out of disk space etc.
.
So, when it runs, try and calculate so that this doesn't happen again
to you at the 55min. limit, and set for a 45min or 1/2hr or, increase
the capture buffers' size.

What you have to do (now that you know how it acts) is work in
smaller increments or, do a better calcualtion. So, find out what
you are using currently. The default, I believe is 2048kb. Maybe
if you set it to 4096kb, you shouldn't run out of hd space. I don't
know, because I only do (have done in the past) 1hr increments,
and use 1024kb size buffers for my captures. (I have my reasons
why I went this why, back who knows when) But I stopped using avi_io
when I switched to winDV.., and now, I'm back to "RsDvCap" again (because
of the improvements) for my DV captures.

-vhelp 3306

[junkmalle]

I used to use AVI_IO a lot. AVI_IO calculates how much disk space will be needed assuming uncompressed video. HuffYUV is compressing the video a by about 1/3 but AVI_IO doesn't take that into account. So when you are 2/3 of the way through your capture AVI_IO thinks your drive must be full. It's very stupid that way. In other words, if you had captured as uncompressed YUY2 your drive would have really been full in 55 minutes.

[The_Doman]

Actually.., avi_io buffers by creating in advance, as many AVI
files (length set to zero) for a given capture job. I'm not sure
how it "calculates" the space and then create as many "zero lenght"
avi files prior to your capturing.

AVI_io does not really calculate the needed capture space.
It just creates as much capture segments as it can fit on the free hd space.
If you set the capturesegments to 2G size and have 20G free, it will just create 10 capture files.
Only the fulll retail version can capture to unlimited file segments, the trial version is limited to 3.

It's a great program I still use it everyday!

[NIRVANAX5X]

Indeed thanks everyone for replying and helping. AVI_IO was set 2048kb for file size and in reality it was giving me .9GB segments. I have doubled the value now. I am also looking into other capture programs freeVCR seems good if not better than AVI_IO but after a capture it gave me errors about the audio saying it was not recorded or saved but then I checked the file and it was all there. Again thanks everyone I'm about to defrag and try to get past the 55 Min mark with AVI_IO or freevcr or I may even try this iuvcr.

[junkmalle]

AVI_IO was set 2048kb for file size and in reality it was giving me .9GB segments. I have doubled the value now.

I don't think that will work. If you originally had 84 GB of free space AVI_IO created 42 files thinking it would put 2 GB in each one. But since the video was compressed it only put .9 GB in each. If you change the segment size to 4 GB, AVI_IO will create 21 files. And it will end up only putting 1.8 GB in each. You'll still only get 55 minutes!

You'll probably have to split you project into two. Capture half, process the video, delete all the HuffYUV files, capture the second half, process that half, delete the HuffYUV files.

[The_Doman]

AVI_IO was set 2048kb for file size and in reality it was giving me .9GB segments.

That's really strange.., why would that happen?
All segments should be equally sized, except the last one.
Maybe capture with another codec to see if it behaves the same?
Try the well known (pegasus)MJPeg codec for example.

[junkmalle]

AVI_IO was set 2048kb for file size and in reality it was giving me .9GB segments.

That's really strange.., why would that happen?
All segments should be equally sized, except the last one.
Maybe capture with another codec to see if it behaves the same?
Try the well known (pegasus)MJPeg codec for example.

AVI_IO counts the bytes before compression. It doesn't even know that HuffYUV is compressing them. So it thinks it's created 2048 MB files when in reality they're only half that size.

[The_Doman]

It doesn't even know that HuffYUV is compressing them. So it thinks it's created 2048 MB files when in reality they're only half that size.

Did you ever tried it yourself??

When capturing with MJPEG or Huffy,
Avi_io just writes the splitted segments to the maximum specified size.

I am using that AVI_io now for about 5 years, I know how it works...

[junkmalle]

It doesn't even know that HuffYUV is compressing them. So it thinks it's created 2048 MB files when in reality they're only half that size.

Did you ever tried it yourself??

Yes, many times. It (v 3.24, paid for) did exactly what I described every time I used it with HuffYUV -- which was most of the time I used AVI_IO.

I haven't used AVI_IO in quite a while -- so I fired it up and saved with HuffYUV v 2.2.0. I asked for 500 MB files and got a series of 250-300 MB files. Curiously, with the "no recompression" setting I got 665 MB files.

[The_Doman]

so I fired it up and saved with HuffYUV

Yeah, I did the same overhere, just to see what's going on here.

Directory of L:\Huffy
27-04-2005 04:48 2.121.184.584 capture.00.avi
27-04-2005 04:48 2.122.118.472 capture.01.avi
27-04-2005 04:48 2.124.080.904 capture.02.avi

Directory of L:\MJPEG
04-03-2005 20:03 2.124.562.952 capture.00.avi
04-03-2005 20:03 2.123.395.208 capture.01.avi
04-03-2005 20:03 2.124.329.032 capture.02.avi

Avi_io segment size 2048MB:
Playtime ~4 Min each Huffy segment.
Playtime ~12Min each MJPEG segment.

That is how it has always worked for me.

[junkmalle]

I uninstaled HuffYUV v2.2.0 which is listed as a beta at the HuffYUV page here. I then installed v2.1.1.

I then captured with AVI_IO set to 500 MB segments. Once again I got ~350 MB files; too small. To be sure there wasn't just an issues with smaller sizes I switched to 2048 MB segments. This time the files came out the right size. So I went back to 500 MB segments -- and the files came out the right size! I tried a few other sizes and the resulting files turned out the correct size.

So this may be an problem with v2.2.0? Later today I'll switch back to 2.2.0 to verify...