Re: [DCP-o-matic] Configre exporting folder for DCP-o-matic

I am recently more concerned about GUI complexity than anything else. We can't build all imaginable functions into DCP-o-matic to cater for anyones need. But I think it would be possible to extend the Auto-TMS upload function (which already supports SCP and FTP) with a simple file copy/move. It would use the same GUI/Prefs elements, but would allow a more or less automatic 'copy DCP to' function. That could cater for copy/move to Sync-folders, external drives, network paths, etc. with a minimal added GUI complexity. Maybe at some time it could be extended to allow an integrated ext2/3 disc writing (which Carl is already investigating into). - Carsten -----Original-Nachricht----- Betreff: Re: [DCP-o-matic] Configre exporting folder for DCP-o-matic Datum: 2020-02-28T17:01:18+0100 Von: "Markus Kalb via DCPomatic" <dcpomatic(a)carlh.net> An: "dcpomatic(a)carlh.net" <dcpomatic(a)carlh.net> Hi I second the "don't create" inside sync folders! But I can also understand why in some cases it is done.i think in most cases it might be done to do uploading while creating and therefor saving upload time in the end. But syncing both files in the end does not save time and also doubles upload volume. For that reason I usually block the upload of "video" when I don't wan't to hassle my encoding team with single dcp copy/move stuff. On the other hand quite some filmmakers still send us whole dcpomatic project dirs as dcp's this is not a fault with dcpomatic but with the understanding or not understanding of the filmmakers. Don't know if dcpomatic could or should do something to educate the filmmakers one more time using a popup when the encode is done? Maybe a popup that has a checkbox with don"t want this in the future anymore. _______________________________________________ DCPomatic mailing list DCPomatic(a)carlh.net http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic