Output files cannot be played

[CrumCon]

i have used huffyuv when capturing my video from my camera, but everytime the files gets bigger then 5GB it cannot be played. i captured this one with birtualdub.
Media player crash when tried playing the file, even explorer crach here.

My final output file was about 9GB, it cannot be played on my pc no matter what.

But when capturing using AVI_IO (still using huffyuv).. the program splits the files into 3 pieces when capturing the videos each files about 4GB.. it plays smoothly

i have been using all version of huffyuv.. the result remain the same
Virtualdub1.5.10 i am using right now

help me guys

[macleod]

have you thought about using, say the picvideo codec? It will significantly decrease your filesize and wont affect quality that much.

When I first read your post, I was already typing "FAT32" limitation, but I am going to guess (escpecially that your specs are XP) that you are running NTFS, so that isnt the issue.........

Have you thought about using freevcr to do the cap. I am assuming that your cap is analog and not DV, right?

[CrumCon]

Yes it is analog, i will try the prog you suggest, i will report the result when im done.

[bunyip]

CrumCon:

It just depends on what you are using to play the file.
My analogue/Huffy captures are often 50-60gb, PowerDVD wont play anything over 4gb but WinDVD will happily play the 60gb file.

Just find a player that can handle the large file.

EDIT: Of course I'm assuming that the huffy files are only interim and you are converting these to something else at a later stage - eg DIVX or MPEG.

[CrumCon]

yes, thats true.. when im done i will convert the file to mpeg2.

But even tmgpenc cannot read the file..

not even videolan can play the file either

[bunyip]

OK - I'm getting the impression that it's not a file size issue but that the file is being corrupted somehow.
TMPGenc, explorer etc are not affected by file-size (although TMPGenc can be using the wrong plugin).
- Can you confirm that your system is NTFS.
- I would suggest that you also make sure that your disk is OK and do a full surface scan.
- I would then try another capture program, one that caps in a single file and see if the corruption is still there.
- Can you also list the characteristics of the captured file or does this crash aswell?