Video Editing- FAT32 or NTFS?

[Floppyman]

Hi all,

I'm gonna be doing some video editing soon on my system. I will have 2 hdd's; one will be used for the OS (win2k) and program files, the other just for video capture. I'm thinking of using NTFS on the drive with the OS and program files, but what file system should I use on the capture drive? FAT 32 or NTFS? Thanks in advance.

P.S. If this is the wrong forum for this post, please tell me where to post this before locking the thread. Thank you.

 

[Nothinman]

There's NO good reason to use FAT32.

 

[AndyHui]

Please read the FAQ: FAT32 vs NTFS.

Asking OS related stuff in General Hardware usually gets locked by the mods these days.

 

[iCore]

Use NTFS. Fat32, if i'm correct, will have a file size limitation on your capture file. Also, if you format the drive with a good cluster size you'll have great performance and wont see any dropped frames.

 

[Dark1]

Originally posted by: iCore
Use NTFS. Fat32, if i'm correct, will have a file size limitation on your capture file. Also, if you format the drive with a good cluster size you'll have great performance and wont see any dropped frames.

I agree I use window 2000 and adobe Premiere and have had no problems using it on NTFS, plus there are even more advantages to use it as well. If you need to store large files (and high quality avi takes up a lot of room quickly, you can configure 2 large (160gb maxtors 7200) drives in either a hard ware raid configuration or through the use of dynamic disk software raid that is built into 2000. Possibly even a volume set that isn't raid but will make both of the hard drives seem as one large hard drive. I should remind you that you would need to keep a separate partition for the operating system.

 

[NickE]

iCore is right - FAT32 has a limit of 2GB for video files - NTFS has no such limit. Many systems e.g. Matrox, Pinnacle get around this by splitting a long capture into a series of 2GB files and then stitching them together via a list of pointers when you access the clip - this is transparent to the user but still not as good as having a single large file.