Re: [DCP-o-matic] DCP for Linux

On a Mac, I also used Macfuse and fuse2ext to format ext discs on a Mac (it's integrated into the standard OS X disc utility). However, it, too, defaults to inode size 256. I was successful to transfer DCPs to some servers using this method. It may be possible to hack some files to make it default to inode size 128. But - as a result, inode size 256 is also just 'mostly' compatible, and not compliant, just as NTFS. Coming from a Windows based DCP creation tool, NTFS is the safest way. Whenever I use ext2-drivers on Windows or Mac systems, I am extremely careful, and I prefer to use them for reading purposes only. I usually prefer to create the DCP directly onto the transport/ingest drive. That way the hashing/digest of e.g. DCP-o-matic directly onto the ingest media is a solid integrity check. In my case, that it usually a CRU slotted drive with an NTFS drive. Sorry, but at the current state of software, creating and writing to an ext-formatted disc is only compliant and safe from a Linux environment. You can't even do that easily from a GPARTED boot-medium, as it doesn't automount other drives. And getting into commandline to create mountpoints, etc. is nothing for the daily windows and mac user. That said, you may need to write to an ext-drive often, but the need to format/partition it comes up only once in a while. I agreee, ext2 IS the standard, but for most users (even Mac users), NTFS is the safer way. NOT mandating NTFS as a DCI/SMPTE standard, but I am absolutely sure NTFS support will remain in all future server and TMS software. - Carsten