[X] Sort by _FILE_MOD_DATE not always lists files in the exact correct order because it often messes up the time

[Zerow]

@ohrenkino

instead of

@Zerow

Value: _FILE_MOD_DATE
Field: _FILE_MOD_DATE
Sort by: _FILE_MOD_DATE

use
Value: _FILE_MOD_DATE
Field: _FILE_MOD_DATE
Sort by: _file_mod_datetime_raw

Like that you should get the correct results.

Yes, I did; so thank you

But I can only assume, that this is the answer to the problem- and that this will not happen again. If it will and I somehow take notice of it, I will get back to report this



But on the side note:

I had to use lower case

%_file_mod_datetime_raw%

becuase with capitals

%_FILE_MOD_DATETIME_RAW%

the Column did not work- I clicked it and nothing ever happened. So it seems that this is another manifestation of this already semi-fixed bug:

[F] _FILENAME is case-sensitive in column configuration

In the Column management window you can use both both "%_filename" and "%_FILENAME%" for "Value" and "Sort By", but if you use "%_FILENAME%" for "Field" then it gets blocked- you can no longer change the name of the file in the main window. But you can change the TITLE and then copy it to the _FILENAME with action. So at the same time it is blocked and it is not And also it does not matter if you put "%_FILENAME_EXT%" or "%_filename_ext%"- they both work the same 100%. So you can have a setting…

\

@ohrenkino

see also:
Exporting Tag and File Information – Mp3tag Documentation

So it is not a bug, just an example in difference between Unix Time and... time? [And that Unix Time thing is also why I keep stumbling upon that 1970 date when tempering with files creation date]

But if it not a bug, then why two files created with the same software [converter] within a span of less than an hour cannot be displayed in the correct order [with the %_file_mod_datetime% version]? It is not like between them "happened" thousands of leap seconds that coud somehow affect the saved time, right?