[Please describe your issue here. Try to include logs (Help → Logging) and add screenshots if necessary.]
After installing 2 updates today, I opened a 96dpi image and used Autopilot to enhance the image.
After processing, the resulting image resolution was scaled 3.6x but when I checked info for it in Photos it showed 1 dpi for resolution. Also looked at Windows file properties and it showed resolution at 1 dpi as well. Others images previously processed with Autopilot retained the original resolution so I was expecting to see 96dpi. I viewed the 1dpi file in several pieces of software but the viewer I use mostly is Windows Image Viewer which could not open it. So, is 1dpi vs 96 dpi a bug?
your image does not have dots per inch because it is not printed to paper. your image has a fix pixel size wide and tall so it is all fine with your image.
Incorrect or missing metadata might indicate a couple of possible problems that I know of. The filename or the folder path for saving might contain characters that mess up the metadata writing process, or the folder being written to is a Dropbox, Google Drive or OneDrive folder (or similar service).
Are you able to reproduce this behavior? We are working on some fixes for bugs in resolution so I would recommend trying again in the next release and this should be fixed.
This problem occurred twice today.
Yesterday I worked with a couple files and did not have this issue.
So it seems to me that the updates caused it.
I’m sure another update will clear it up though.
If you can share the files, please send them to me so I can verify the behavior.
You can securely submit your image(s) to my Dropbox using the link below. Please be sure to send me a note to let me know you sent something. Dropbox File Request
There is a new build comin which may have a fix. I would like to test it to see if it’s still an issue there.
Generally the resolution should not be changing. At minimum, it should be preserved and it’s valid that seeing metadata change without user input is concerning so it’s still a bug even if it does not usually affect the image itself.
