Editing in FCP on an NTFS Drive

Question

Editing in FCP on an NTFS Drive

I'm about to receive 1 TB media on a drive formatted on NTFS shot on a Phantom HD camera. They will be in the form of .cine files. Will I be able to edit off of an NTFS drive in FCP if I keep the project on my own hard drive? How can I convert these .cine files into something that FCP can use. I know I have a glue-tools plug in but i'm not sure how to use it.

Thank you.

Message was edited by: Michael Heldman

G5 dual 2.7, Mac OS X (10.4.11)

Posted on May 29, 2008 12:51 PM

Reply

Answer 1

David S.

Level 7

20,636 points

May 29, 2008 12:59 PM in response to Michael Heldman

My understanding is that you cannot write to a NTFS drive.

Reply

Answer 2

Studio X

Level 7

27,229 points

May 29, 2008 2:17 PM in response to David S.

As David notes, you should be able to read from the drive, but you'll not be able to make any changes to files (e.g. rename a file).

I've no idea what kind of read/write speed you'll get if you use it as an external.

The simplest solution may be to copy the files to another drive (formatted as mac os extended) and save the ntsc formatted one as your backup.

Never worked with .cine footage so can't help you there.

Good luck.

x

Reply

Answer 3

May 29, 2008 3:23 PM in response to Michael Heldman

Hey Michael - hope all is well,

I've got no experience with the Phantom HD camera - you can check google - I found this: http://blogs.creativecow.net/node/505

Patrick

Reply

Answer 4

tallguy

Level 4

1,415 points

May 30, 2008 10:17 AM in response to Michael Heldman

http://www.paragon-software.com/home/ntfs-mac/

I have it on two macs here, no issues for quite a while. makes it easy to share with the 4 DS and the Avid. Also do exchanges with some 3D guys. we get 34 interface drives they run sata we run fw800

Reply

Answer 5

Jun 4, 2008 8:02 AM in response to Michael Heldman

My own experience tells that NTFS support is buggy in Mac OS (because there is no specification for NTFS filesystem format, so any filesystem drivers that implement NTFS support were implemented by trial and error and can misbehave in some cases).

Bugs can be seen as wrong data being read from the file located on NTFS volume. But the probability of bug can depend on how fragmented NTFS volume is; if you write files to a totally empty NTFS volume on Windows, files won't be fragmented so files will be read correctly.

So beware.

Reply