1 Mar
2020
1 Mar
'20
8:01 p.m.
How about if you change the last modified date on the file?
On linux or mac, `touch -m j2c_xxx.mxf` would update the timestamp
without altering the file contents, so no problem with causing a
hash-check fail (obviously, substitute "xxx" for actual name of the file).
Maybe then Google Drive Sync would pick it up and sync it?
Jim
On 01/03/2020 14:35, Carsten Kurz via DCPomatic wrote:
Am 28.02.2020 um 15:10 schrieb audiovisual--- via DCPomatic:
Okay - I can reproduce that issue on my Mac with
my Gdrive app/folder
as well. The MXF in the video folder is immediately synced if GDRIVE
app is running during the conversion. All the files from the DCP
folder are synced - except that the hard linked video mxf file in the
DCP folder is left out. When I delete the video.mxf in the video
folder (or the whole video folder), the video file in the DCP folder
is not synced immediately. Obviously, GDRIVE does not detect the
unlinking of that file immediately. When I 'halt' and resume the
folder sync in the Grive app menu, still no sync. However, when I
quit and restart the GDRIVE app, the video file is immediately
recognised and synced. So, for now, not a very smart solution, but at
least a work around, and something to think about.
As a wrap-up - no matter how long I wait after deleting the video-mxf
in the video folder, the google client will not sync up the file from
the DCP folder. It simply doesn't recognize it as changed. Same when I
halt the client - even after multiple hours, no update. The only way
to force recognition of the unlinked video mxf file is to quit and
restart the Google drive app. Then the video-MXF from the DCP folder
is immediately synced.
- Carsten
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic