FCP5 export to WinXP if filesize over 2GB, break the file to 2GB parts

[Tim Wilson]

The 2 gig file limit is a problem with Windows… drives formated for PC’s cannot deal with file sizes larger than that. so my guess is that until this problem is addressed…

It was addressed in 1993, with the introduction of the NTFS formatting. (The N and T refer to the File System introduced in Windows NT.)

Although FAT32 disks are indeed limited to 2GB file sizes, the maximum file size on an NTFS formatted drive is 16TB minus 64KB.

That was true of the Mac OS as well until OS 10.4, when the maximum file size was raised to just under 8EB (exabytes), or around 8 million terabytes.

So, while it ain’t no 8 million TB, it isn’t 2 either.

BTW, you can read an NTFS volume on Mac easily enough, and now there are a couple of ways to write to one as well. One is MacFuse, a free tool developed by a Google engineer in his free time. The other is Paragon NTFS, which’ll set you back 30 simoleons, which is equivalent to $30 minus 5 cents.

PS. If the target drive is formatted FAT32, you’re hosed…but that’s not because of any inherent limits in Windows itself. You’d be limited to that same 2GB if you were writing from the Mac OS.

Moral of the story: unless it’s for a thumb drive or something similarly tiny, avoid FAT32 on either platform.

Tim Wilson, Creative Cow
My Cow Blog
Join my LinkedIn network

[Andras Csore]

As i write few years ago, the 2GB cant be a problem, because, manully works fine, other apps works fine…

>I CHECK the followings:
>1. If I export to local mac hdd (its export one 3GB .mov), >and copy with Finder to WinXP share everything is okay!
>
>2. If I export any movies from QuickTime PRO, with SAVE AS >function, its export one 3GB file to WinXP share fine!

So, the FCP still watch the export over SMB and break to 2gb…
Space Age – 2007… 🙁

I tr to find out some ini (pref) files, but cant find.
Anyway, now i use NAS where AFP protocol supported to workaround this 2GB…
Hmmm…