Your plugin truly works imsanely well :), except for this one issue that it seems some other users have encountered also.
There is a support post titled "Detecting wrong image size," for instance:
And that issue is that, at least in our experience, Imsanity disregards whatever Max width/height dimensions have been entered on the Imsanity Settings or WordPress Media Settings pages.
In this case ALL images are sized to 533x300, no matter what.
In the case of the above user experiencing a similar issue you suggested that Imsanity may have been using the WordPress meta-data found in the the "posts" table. But that doesn't seem to be the case here.
Doing a query on the entire MySQL database finds only ONE image with the above dimensions: 533x300. No other images have that dimension. Additionally, querying the entire database (all tables and fields) shows no evidence of even the width dimension of 533 showing up anywhere. And, doing a search of ALL of the default WordPress files as well as our theme files (*.php, *.css, etc.) also does not show the width 533 being specified anywhere.
Imsanity seems to be the best and is the one we'd like to use. Testing this with a couple of other resize plugins yields similar results: One also resizes to 533x300, while the other resizes to a width of 169px (where it's getting the 169 width from? have no idea either).
These plugins are obviously either pulling those dimensions from somewhere, or (more likely since full searches do not find those dimensions anywhere) calculating those dimensions, based upon some criteria specified either by the plugin or WordPress.
This would seem to defeat the purpose of having an Imsanity Settings page, if Imsanity ignores the settings on that page? Shouldn't the Imsanity Settings page dictate and/or override any other dimensions?
Again, the above dimensions (primarily 533x300) are NOT in any of the images in the Media Library or that are being newly uploaded, except for one. So EXIF data seems unlikely to be what's causing this.
This is with the latest stable version of WordPress, 3.6.1 and the latest version of your plugin 2.2.3.
If you can suggest a workaround or fix that would be great, and greatly appreciated!