I recently edited the filename (and the filename
only) of a fair number of videos using MediaMonkey's "Properties" GUI. When files are renamed in Windows, the file's modification date (date stamp / time stamp) remains unchanged. When you rename them from MediaMonkey, however, their date/time stamps
do apparently get changed. This is a problem for people who use date/time comparisons in their backup or synchronization software.
I use FreeFileSync with the date/time/size-comparison option. FreeFileSync can recognize when a file has only been moved or renamed. If nothing else about the file has changed, FreeFileSync simply changes the pathname of the corresponding file on the target end of the backup or sync.
If the file's date/time stamp has changed, however,
FreeFileSync recopies the entire file from scratch. In my particular case, if I had renamed my files from Windows Explorer or a bulk-renaming utility, I would have been facing a
five-second backup job. Renaming them from within MediaMonkey unnecessarily turned that five-second backup job into a
three-hour backup job. And since I back up to two external drives, for redundancy, that translates to an unnecessary
six hours of backing up. (Well ... six hours less ten seconds.
)
In conclusion, if the only thing about a file that is changed from within MediaMonkey is the file's pathname or filename, MediaMonkey should
NOT update the file's "date modified" record.
I recently edited the filename (and the filename [i]only[/i]) of a fair number of videos using MediaMonkey's "Properties" GUI. When files are renamed in Windows, the file's modification date (date stamp / time stamp) remains unchanged. When you rename them from MediaMonkey, however, their date/time stamps [i]do[/i] apparently get changed. This is a problem for people who use date/time comparisons in their backup or synchronization software.
I use FreeFileSync with the date/time/size-comparison option. FreeFileSync can recognize when a file has only been moved or renamed. If nothing else about the file has changed, FreeFileSync simply changes the pathname of the corresponding file on the target end of the backup or sync. [i]If the file's date/time stamp has changed,[/i] however, [i]FreeFileSync recopies the entire file from scratch.[/i] In my particular case, if I had renamed my files from Windows Explorer or a bulk-renaming utility, I would have been facing a [i]five-second backup job.[/i] Renaming them from within MediaMonkey unnecessarily turned that five-second backup job into a [i]three-hour backup job.[/i] And since I back up to two external drives, for redundancy, that translates to an unnecessary [i]six[/i] hours of backing up. (Well ... six hours less ten seconds.;-))
In conclusion, if the only thing about a file that is changed from within MediaMonkey is the file's pathname or filename, MediaMonkey should [i]NOT[/i] update the file's "date modified" record.