Sync Interrupting With The Foundry Nuke Autosaving (Windows)

[VFXLegion]

Hi all, 

 

We have kind of a serious issue with Sync. Our working folders for our VFX compositing package write out a new autosave every 10-90 seconds. On Windows it appears that Sync 'locks' the file which makes the autosave throw and error to the user trying to work. 

 

Is there a way to tell Sync not to try syncing this file type/unique name identifier? Maybe not lock the file down while it is being read by Sync?

 

I'm not sure what the answer is, but it is making it difficult on the most useful feature of the software. 

 

Thanks.

 

[Firon]

Unfortunately on Windows, reading a file locks it and prevents writes.

 

You can add it to the syncignore list (using wildcards) to prevent it from being synced.

[VFXLegion]

Where is this magical syncignore list located? It's a very specific naming scheme, so it would be easy to ignore that file. 

Nevermind. Found it. Will report back after trying it. 

[denis4inet]

VFXLegion,

BitTorrent Sync open all files in shared mode (ShareMode: FILE_SHARE_READ | FILE_SHARE_WRITE | FILE_SHARE_DELETE), doesn't lock files. But, VFX compositing program open file in non-shared mode, when BtSync open file in shared mode (IMHO). This cause an ERROR_SHARING_VIOLATION in VFX program.

 

From msdn: http://msdn.microsoft.com/en-us/library/windows/desktop/aa363858%28v=vs.85%29.aspx

 

wShareMode [in]

The requested sharing mode of the file or device, which can be read, write, both, delete, all of these, or none (refer to the following table). Access requests to attributes or extended attributes are not affected by this flag.

If this parameter is zero and CreateFile succeeds, the file or device cannot be shared and cannot be opened again until the handle to the file or device is closed. For more information, see the Remarks section.

You cannot request a sharing mode that conflicts with the access mode that is specified in an existing request that has an open handle. CreateFile would fail and the GetLastError function would return ERROR_SHARING_VIOLATION.

 

You can test it using Procmon.exe utility with Path a filter (set to you shared folder).