Running Linux on a Mac (or PC) is very possible (some may say easy) with a
little research. Once you have that running, it's pretty easy to make
proper EXT2 drives and have a DCP that can be read by every DCP server on
the market. I have found it a huge time saver with added confidence.
Definitely worth the effort. My basic process is to create the DCP on a Mac
and copy it to an external drive (HFS works fine). Boot into Linux, create
the EXT2 DCP drive, copy the DCP folder to the new drive. Run DCP Inspect
for good measure, and I'm done.
-Parke
On Wed, Jul 15, 2020 at 11:57 AM Jim Dummett via DCPomatic <
dcpomatic(a)carlh.net> wrote:
Just to add one thought. I had no end of trouble with
Paragon NTFS + EXT
drivers on Mac.
In particular, I found it was a bad idea to encode the DCP in DCP-o-matic
direct to an NTFS/EXT drive - very often the DCP was corrupt.
Better to do what you're doing - encode on the Mac to a Mac-format drive
and then copy the DCP to NTFS drive after.
Jim
On 15/07/2020 12:50, Carsten Kurz via DCPomatic wrote:
I never had issues with hidden files. All DCI servers run Linux and are
aware of hidden files. It's just not 'pretty' if they go into a wide
distribution.
If you use a preformatted disc - use Mac OS disc utility to check wether
it is MBR or GUID/GPT formatted.
GUID/GPT can cause REAL issues with some servers - to the point that the
content vanishes from the disc. Make absolutely sure it uses an MBR
partition! If disc utility shows GUID - erase the disc and re-initialise
with the MBR option.
- Carsten
_______________________________________________
DCPomatic mailing
listDCPomatic@carlh.nethttp://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic
--
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Parke Gregg
Colorist/Editor/Project Finisher
Stuck On On
www.stuckonon.com
512.535.4760
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .