Issue 1:  When a new image is generated, the resolution information (ex. 300 dpi) is not always written to the new file. The ability of the app to write this information to the output file’s metadata is dependent upon the file types (.jpg, .png, etc.) of the input and output files.

In instances where the app is unable to read the input file’s resolution and/or write the resolution to the output file, this information is left blank in the output file’s metadata.  When the user’s operating system shows the file information, it will see that the resolution information is missing from the metadata and assign a default value — commonly 72 dpi or 96 dpi — resulting in the image appearing to have been reduced in resolution during processing.  This is not the case.  The app does not, under any circumstances, change the resolution of the image from input to output.  If a 300 dpi file is input, the outputted result will also be 300 dpi.

Issue 2:  I have received a report from one user of an issue that causes the buttons to be non-functional.  This is an exceptionally rare issue, but if you encounter it, please contact me so I can send you a modified version that has a temprorary fix to make it functional.  I hope to have a permanent fix for this issue in a future release.   Should be fixed in v2.10.

Issue 3:  There is an issue with the encoding/decoding of non-ASCII characters in filepaths on Windows installations.  In other words, if the filepath of an image you’re attempting to load or save contains non-English special characters (ä, ë, å, etc.), the image may fail to process.  The temporary workaround is to move the files to a folder whose filepath doesn’t contain any special characters.  I will have a fix for this issue in the next bug-fix release.  Should be fixed in v2.10.