TuneFUSION Discussions

[Spoon]

Re: TuneFUSION Discussions

Open TF settings page, click edit and retrieve the contents of both logs please (detailed and normal).

[mville]

Re: TuneFUSION Discussions

Further to my report on 09 Jan, where TuneFUSION re-synced 62,553 of 97,597 files, today TuneFUSION is re-syncing 65,754 of 97,597 files.

This is not workable for me. Previous to TuneFUSION, I was running FreeFileSync. This worked successfully for several years, without a single hitch, so I know it can be done.

.. problems may be connected to a reboot or possibly 2 reboots, close together, at the same time TuneFUSION is performing a scheduled re-sync (set to automatic, every 4 hours).

[mville]

Re: TuneFUSION Discussions

We need to check on this...

I have sent you a PM, with link to corrupted files.

[Spoon]

Re: TuneFUSION Discussions

We need to check on this...

[mville]

Re: TuneFUSION Discussions

The database tracks the source modified dates.

Thanks for the info.

I have checked all 62553 re-synced tracks. 1 re-synced file is corrupt. I have checked the modified date and time and it appears this file was re-syncing, just as I rebooted the source PC running TuneFUSION, so the sync did not complete.

I assume something like this: the TuneFUSION database is updated before each file sync is completed. This file did not complete due to the reboot, but is not re-synced after booting, as the database assumes it completed.

This also goes to explain the half dozen file corruptions that I mention in post no. 51, that have occurred over the past 4 months. I expect these files were re-syncing, when the source PC was rebooted (or sleeps/hibernates?).

[Spoon]

Re: TuneFUSION Discussions

The database tracks the source modified dates.

[mville]

Re: TuneFUSION Discussions

Modified date of the files (source vs destination).

The 62553 tracks have re-synced. If modified date is being used to determine re-sync, why aren't the source modified dates reflected in the destination files?

[mville]

Re: TuneFUSION Discussions

The modified date should be visible to Windows explorer.

The modified dates are visible in Windows File Explorer, so modified date is NOT what triggered the re-sync.

Another possibility is the location where the files are read from, it was removed from system, temporarily, TuneFUSION then removes these files from its watch list, and when it reappears they are re-added and resynced.

If the network location was not available, then why were only 62553 of the 97597 tracks, re-added and resynced?

Source Windows 10 PC is running TuneFUSION and has a local drive (D: drive) with the source flac/mp3 files. Destination Windows 10 PC is always on and also has a local drive (D: drive) with the destination flac/mp3 files and in Power Options >> Turn off hard disk after 20 minutes is set.

The source PC was booted at 11:17am, according to the event viewer system log. At 11:23am, TuneFUSION started re-syncing.

I can only assume that there is a delay before the network location is available to the system, when booting. In this short time most, but not all files (62553 of 97597) were re-added and resynced.

Maybe a delay needs adding to TunesFUSION in order to compensate for delays in Windows 10 bringing network locations online and also hard disk power management sleep/wake conditions.

[Spoon]

Re: TuneFUSION Discussions

The modified date should be visible to Windows explorer.

Another possibility is the location where the files are read from, it was removed from system, temporarily, TuneFUSION then removes these files from its watch list, and when it reappears they are re-added and resynced.

[mville]

Re: TuneFUSION Discussions

Does anyone have any thoughts on why the modified dates on my flacs (resident on a windows 10 pro 64-bit server pc), would have their modified dates change overnight?

So far I have looked at the following, for possible culprits:
Avast Free Anti-Virus
Task Scheduler
Disk Defragmenter
Foobar2000

I was wondering if there is any Windows 10 maintenance/housekeeping tasks, that might trigger a re-sync.

[mville]

Re: TuneFUSION Discussions

Odd. Can you see that the file dates actually did change overnight? Or is this an assumption you are making given what Spoon said above (regarding why they synched)?

No. According to file explorer, no modified dates were changed between the times shown in post no. 56.

Last flac edit, according to modified date was 05 January 2018, 18:29:35.

And yes, I am assuming there is something else related to modified date that is not available to the end user, according to what Spoon advised.

[garym]

Re: TuneFUSION Discussions

Does anyone have any thoughts on why the modified dates on my flacs (resident on a windows 10 pro 64-bit server pc), would have their modified dates change overnight?

Odd. Can you see that the file dates actually did change overnight? Or is this an assumption you are making given what Spoon said above (regarding why they synched)?

[mville]

Re: TuneFUSION Discussions

Modified date of the files (source vs destination).

Does anyone have any thoughts on why the modified dates on my flacs (resident on a windows 10 pro 64-bit server pc), would have their modified dates change overnight?

[Spoon]

Re: TuneFUSION Discussions

Modified date of the files (source vs destination).

[mville]

Re: TuneFUSION Discussions

Here are the last 2 entries from my TuneFUSION log:
Sync started on 09 January 2018, 01:44:26 to \\my network location
Library contains 97597 tracks, 0 tracks requiring syncing
Successfully completed in 1.1 seconds

Sync started on 09 January 2018, 11:23:00 to \\my network location
Library contains 97597 tracks, 62553 tracks requiring syncing

so, TuneFUSION is now re-syncing 62,553 files, for reasons I am not clear about as my library has not been edited recently.

What does TuneFUSION use to determine that a file needs to be re-synced?