Originally reported by 'mawi', but marked as No-bug.
Using latest build 2.42, I too am finding the file Modified date/time is not being updated when saving to FLAC files. Haven't tried any other types. This is regardless of the setting of the tick box in Tools -> Options -> Tags. Specifically I was amending the text in Album Artist using the Extended Tags editor.
This causes a problem for SqueezeBox, which I believe relies on the date/time file property for incremental rescans of the music library.
Further testing has revealed a subtle twist: the problem only occurs with files stored on my NAS. File modification timestamps will update ok on my WinXP machine. However, using dBpoweramp to modify the tags on the NAS files updates timestamps ok.
So, could it be something to do with Mp3tag working over a network share? (NAS is a QNAP TS109/II with Unix, if that's any help.)
I can confirm this behavior with a Netgear ReadyNAS Duo and mp3 tagging. Modification date and time is updated if file is on local drive; remains untouched if on remote drive. Interestingly, the folder containing the files does show a modification date and time corresponding to the time that the tags on files within the folder were updated.
EDIT: Seems to be working with v2.43.
EDIT: Maybe not. I can't figure out what causes the modification date and time sometimes to be modified. Most times it is not. I also use Picard; that is modifying the date and time correctly.
Just upgraded to the latest RAIDiator 4.1.6 firmware but the issue remains.
I tried using notepad to edit a text file on the NAS and the timestamp was updated properly. Do you still think its a NAS issue?
I just got a clue from MM forum to check the NAS and it uses the same date for created and modified time! Oops no further checking indicates this is wrong there are 2 different dates...
In Mp3tag, does this happen with a specific file type only (FLAC, MP3, MP4, ...)? If you cannot test this (e.g., you're only using one specific format) please let me know which of the supported ones you're using.
This looks like they have dedicated code for updating those timestamps and are not relying on the underlying filesystem to update the timestamps correctly.