Prints Display Wrong Date When Printed
tracked
Salbug
When capturing a print, the preview displays the correct date. However, after printing, the world object version shows an incorrect date. Notably, the file version remains accurate, as demonstrated in the screenshot below.
Image was captured and printed at
2024-12-15_03-45-56
CT.Log In
Usemame
- I took a print on 2025-01-01:
(from the metadata)
<xmp:CreateDate>2026-01-01T23:09:31.1942695+09:00</xmp:CreateDate>
- Found I forgot to add the message so I edited it right away after the automated print. I also downloaded it today so I can post it on SNS, only found the time was altered:
<xmp:CreateDate>2026-01-02T08:09:47.0000000+09:00</xmp:CreateDate>
(
Now my new year print is less worthily :<)
My assumption, issue is the print-message system, it added the timezone when applying the messages*- To test the assumption, I deleted one of my 64 prints and took a new print, it should be 1904, the metadata of the automated save to the print was correct:
<xmp:CreateDate>2026-01-04T19:04:02.5828570+09:00</xmp:CreateDate>
- I want to process to download the new print manually to check the metadata, but instantly found the automated print was already in the wrong displayed date(of tomorrow):2026-01-05
- Downloaded the print, the metadata suggest it's "NOW+my timezone(+9)":
<xmp:CreateDate>2026-01-05T04:04:03.0000000+09:00</xmp:CreateDate>
- Edited the photo and download from the UI, no change:
<xmp:CreateDate>2026-01-05T04:04:03.0000000+09:00</xmp:CreateDate>
- Print and then download the edited print, no change:
<xmp:CreateDate>2026-01-05T04:04:03.0000000+09:00</xmp:CreateDate>
Conclusion: It's not the add-message system, it's the print processing, there's a bug, when server process the print, it will add the timezone right away
StormRel
marked this post as
tracked
Salbug
The discrepancy is still there sadly. Taken at exactly 00:00 on 29.1.2025
Salbug
Making another canny as I just realized another bug in these images as well.