You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SrcFileB matches configured tags so should be synced.
SyncFileA doesn't exist.
The current behaviour is to attempt to transcode SrcFileB to SyncFileB. This works fine, unless the following is also true:
SyncFileB already exists.
In this case, the application hangs (if transcoding) or fails to transcode (if copying).
This can happen if the "rename" event is actually an "overwrite" event. Since there's no distinction in the FileSystemWatcher between these two types of events, we need to deal with it ourselves. This has been seen to happen when Foobar changes a file's tags: it creates a new temporary file (SrcFileA in this case) and then renames that temporary file to the original file's name (SrcFileB), overwriting it.
The fix is to delete SyncFileB before attempting to copy/transcode SrcFileB, if it exists.
The text was updated successfully, but these errors were encountered:
…cation to hang.
If SrcFileA has been renamed to SrcFileB, SyncFileA doesn't exist, but
SyncFileB does exist, the application now deletes SyncFileB before
continuing.
Consider the following edge case:
The current behaviour is to attempt to transcode SrcFileB to SyncFileB. This works fine, unless the following is also true:
In this case, the application hangs (if transcoding) or fails to transcode (if copying).
This can happen if the "rename" event is actually an "overwrite" event. Since there's no distinction in the FileSystemWatcher between these two types of events, we need to deal with it ourselves. This has been seen to happen when Foobar changes a file's tags: it creates a new temporary file (SrcFileA in this case) and then renames that temporary file to the original file's name (SrcFileB), overwriting it.
The fix is to delete SyncFileB before attempting to copy/transcode SrcFileB, if it exists.
The text was updated successfully, but these errors were encountered: