Oh, does it actually stop 3 mins from end? Have you viewed the actual rendered file? Is it in fact short the 3 mins? - Apologies if you've dome this and regard this as a stupid question . . .

Grazie

18:50 is probably when it hits 4GB in size. If you're using FAT32 (older versions of windows) then files on your hard drive are limited to 4GB. When you say "recording", what do you mean exactly? Are you trying to capture this film? If so, then VidCap is breaking your file at this point and starting another file to get around the 4GB limitation. Look for another file on your hard drive with exactly the same file name but an extra "01" appended to the end. This should be the other three minutes of your capture. Simply drag this file to the timeline after the first one and butt it up to the end of the first.

This same process applies to rendering as well. If your output file reaches 4GB then additional files are created to hold the rest. VidCap will print these to tape in order seamlessly simply by specifying the first filename.

the film has been completely edited. I have a 40g hard drive, 256 ram, 733 processor and 98SE.

when I rendered it to the avi format for NTSC i am shut down at 18:50.

(Look for another file on your hard drive with exactly the same file name but an extra "01" appended to the end). --this i sort of don't understand. Extra file?

thanks

mf

> --this i sort of don't understand. Extra file?

The problem is that Windows 98SE cannot write more than 4GB to a single file regardless of how much free disk space you have. It is a limitation of the FAT32 file system. Your 22-minute film will take more than 4GB to write to disk. That’s why it’s stopping before the end of the film.

To get around this 4GB limitation, VideoFactory will create a second file to hold another 4GB of video and use the same name as the original file but append a “01” to it. If it needs more than 8GB it will create another file and append “02” to the name and so on until it has rendered the entire project. This is why Chienworks said to look for another AVI file with the same name as the one you created but with a “01” added to the name. This will have the rest of your video on it.

> any suggestions to fix this problem?

This is not a VideoFactory problem, its an operating system problem. The only way to fix this (instead of the multiple file workaround) is to upgrade to an operating system that supports files greater that 4GB like Windows 2000, or Windows XP and use the NTFS filesystem.

~jr

I'm still running WinME - hopefully soon to have a bespoke video systrem purely for my Vegas4 work - and it works well. VF and Vegas "chain" the bigger than 4gb files in an orderly fasion, and in the way that has been described here. It does work.

However, you appear to be saying you do all video work on the C: drive. Is this correct? DO you have a separate video drive to do this work? - Maybe, just maybe, your C: drive is getting a tad overloaded. C: drive needs plenty of space to thrash about with disk cache stuff. Have a "loaded" C: drive could work against you. Could you report back and tell us how much "space" you have on your C: drive?

You may need to create some free real estate for the "bigger" AVI files to be created and chained. - It's not just the size of the files that has to be contended with here. It is also the information for the pc to manage the creation of large such files. I've found with my 32gb C: drive - now down to 11gb "free" space - if I go further down to say 6gb free space, I can run into operational errors. What may be being reported back to you is an "over-read" on the space availablle to you - yeah?

If space is a problem I would consider emlpoying a separate video drive, just for your VF work - seriously! - Leave all your programmes on C: - including VF and any graphics packages - and use this "extra" drive to do the massive work of laying down video files etc etc. - there's been plenty of references to the pros and cons of separate video drives here and on the Vegas forum. It appears that the opinion of those that do editing on a reguklar basis that having a separate video drive is both essential and provides for better stability in the functioning of NLE activity. - Personally, having a laptop, I've grown my kit to now have the following firewire externals: 1x60gb; 1x80gb AND 2x120gb !! - Appart from anything else it does provide me with the option to DO all the work for a single project in one neat place; confirm the project's functioning by PTT; allow me to adjust and confirm final FINAL PTT - and then allow me to "delete everything relating to that one project. It's neat and tidy. It's also ready to take the next project - no need for defrag, as there is nothing to defrag.

I suppose the point I'm making here is that eventually, you may want to expand beyond your present C: - which in turn maybe giving grief at present, maybe due to the lack of real estate - having invested in some externals, or for you maybe able to utilise a spare bay to put in that video drive - you will be able to still use these extra drives when you finally upgrade to XP or so on.

FInally, you shouldn't get this annoying issue - I don't, and I'm running a derivative of Win98se, WinME. FIle chainning works fine. If you can in the future upgrade to XP - but it does work well on WinME.

As JR says, "This is not a VideoFactory problem, its an operating system problem." - well, almost JR. It's an operating system "obstruction" or "issue". It's not IMHO a problem, it's the way it is with FAT32, which creates "problems" for NLErs - like us!!

Oh, just another thought - Have you had any success in the past with >20mins clips?

Best regards,

Grazie

> It's an operating system "obstruction"

Is that like an obstruction of justice? Can we hold Microsoft in contempt of court? Sorry, I’m just feeling silly tonight. ;-)

~jr

"Sorry, I’m just feeling silly tonight. - Errmmmm.... not with MS! MS are a truly great company and have provided me with fabulous opportunities over the past 15 years. I can't speak highly enough about thier organisation - IMHO - of course!

Best regards,

Grazie