-
Final Cut Pro off of a Windows file server
I am finalizing some upgrade plans for our Final Cut suites at my company where we are the only Macs in the building. Up till now our Macs just ran off individual storage units – those being Medea RTR’s.
I have planned to continue using these units for individual storage with forthcoming MacPros, but our IT guy keeps suggesting that we just start editing off of a big Windows file server he has in our server room via a gigabit switch.
So far I’ve taken a thanks-but-no-thanks approach to this idea because I just can’t imagine it working right. I don’t know about the pure speed factor.. But we will be doing SD uncompressed 99.9% of the time and we only have CAT5 running to the suites. Even with the MacPro’s gig-E, I don’t think it will be fast enough. Most of our stuff is 30 second spots, but it typically involves many layers of compositing.
But I’d imagine there’d be other issues besides speed, such as filesystem issues. Off the top of my head, I’m thinking that once Final Cut on one machine captures to a file server running Windows, things will get all messed up since it doesn’t add any file extension to the file it creates. In my experience, subsequent attempts to access those files from the Windows server by a Final Cut station fail because it doesn’t know how to deal with it, unless you manually rename it with a .MOV extension.
Whenever we get into these discussions, I tend to be at a loss for succinct and concrete examples of why this is not practical… especially when discussing with someone that is not familiar with Macs. I’m wondering if someone would want to share with me some specific reasons or examples why FCP off of a Windows fileserver is a no-go.