Page 1 of 1

Possible Timestamping Bug

Posted: 25 Sep 2025 01:39
by phred
Using XY 28.00.0000 on Win 10

I've got nine mp3 files in a folder on a mapped NAS drive. I'm trying to change the Created, Modified, and Accessed dates. I've copied and pasted the timestamp from another file to any one of these nine and I get an "Timestamping failed" error. I've also tried manually typing the timestamp. The folder is not read-only. Nor is anything locking the file despite the error message.
2025-09-24_19-32-39.jpg
I'm able to change the timestamps on other files on the NAS.

I installed XY32 27.10 and changing the timestamps works as expected.

Re: Possible Timestamping Bug

Posted: 27 Sep 2025 18:37
by admin
"nine mp3 files"... is this relevant here? May I conclude that it works well with eight txt files?

Re: Possible Timestamping Bug

Posted: 27 Sep 2025 20:43
by phred
admin wrote: 27 Sep 2025 18:37 "nine mp3 files"... is this relevant here? May I conclude that it works well with eight txt files?
Good point. I discovered this went working with nine MP3s. I have now tested further and the issue happens with -all- MP3 files. It does not happen with .txt, .exe, . pdf, .zip, .jpg.

Re: Possible Timestamping Bug

Posted: 27 Sep 2025 20:46
by admin
Any preview on?

Re: Possible Timestamping Bug

Posted: 27 Sep 2025 20:49
by phred
No preview on. I just test with today's beta 28.00.0006 and the issue persists. I tried this beta because I saw the other user's timestamp issue was resolved with this beta.

Re: Possible Timestamping Bug

Posted: 28 Sep 2025 14:12
by admin
Cannot reproduce.

Re: Possible Timestamping Bug

Posted: 28 Sep 2025 15:16
by phred
admin wrote: 28 Sep 2025 14:12Cannot reproduce.
Hmmm ... sorry to hear that.

I dug a little deeper to no avail. Operating under the assumption the issue was files on a specific partition or drive, I tested again and the issue persists. I also tested with files on a portable USB drive and on a NAS. Same behavior.

Lastly (for today) I rolled back to an early 64bit beta: 27.00.0916 and still the same behavior.

Re: Possible Timestamping Bug

Posted: 28 Sep 2025 17:24
by admin
What if you rename the files (other extension)?

Re: Possible Timestamping Bug

Posted: 28 Sep 2025 17:54
by phred
I renamed test.mp3 to test.txt and I was able to change the date/time for created, modified, and accessed. I changed it back to test.mp3 and the error appeared.

The issue also exists on another Win10 PC with 28.00.0000 and 28.00.0006.

Re: Possible Timestamping Bug

Posted: 28 Sep 2025 18:05
by admin
Try mp4.

Re: Possible Timestamping Bug

Posted: 28 Sep 2025 19:42
by phred
Works as expected with .mp4

Re: Possible Timestamping Bug

Posted: 28 Sep 2025 19:48
by admin
Mystery.

Re: Possible Timestamping Bug

Posted: 28 Sep 2025 19:54
by phred
Ahhh c'mon. I thought you'd enjoy a good challenge. ;)

Re: Possible Timestamping Bug

Posted: 28 Sep 2025 19:58
by admin
I think you have a better chance of solving this. Something on your system is locking the MP3s.

Re: Possible Timestamping Bug

Posted: 28 Sep 2025 23:37
by phred
admin wrote: 28 Sep 2025 19:58 I think you have a better chance of solving this. Something on your system is locking the MP3s.
I'm not sure about the mp3s being locked. I'm able to change the file name on them. And the extension. Which I'm fairly certain I couldn't do if the file was locked. Also LockHunter shows that nothing is locking the file.

I've had Bulk Rename Utility for quite some time and never knew it could change the dates. It didn't change the mp3 files and it didn't throw any error. But it works on other files. Then I found Bulk File Changer and it was able to change the dates on the mp3 files. That still doesn't tell me what's causing the problem.

At this point I'm out of ideas, so for anyone following along, I'm looking for suggestions to try to track this down.