TOPIC: truncated images - optimum size?

What is the optimum size for image submission? I see that a lot of resizing of images takes place [ thumbnails/platform-based sizes etc.] however I find that some of my images are being truncated in laptop/tablet view, both on the list and on the full-screen views, though at phone view the full screen is not truncated. This is a problem since the photos often have the important part of the image cut off. Do I need to ensure that all images are a standard size and if so what is it?
I'm really impressed with the extension, by the way.

I should add that i am aware of the 'media' tab of the dashboard which defines image sizes, but I can't see how this relates to the image truncation issues I'm having. I also notice that images are being manipulated by the upload process, so it seems that this is where my problem is arising?

Hey Pete,
Can I see screenshot. Original image, image on the site, expected result etc.

We generate thumbs for the list on the right and for single view. It would be stupid to output the original size of the image. However if we've generated a thumbnail for single view that is 1940px wide and your table/phone only have 1000px to show the image, then the gallery automatically resizes/adjust the image to fit.

Regards,
Daniel

the list-view image and the original image for location 'Church of St Peter and St Paul, Bleadon' are attached; the full screen image is at dropbox screenshots . The second image on this location has a similar problem. You will see that the image is such that losing the top part means that the important part [the bagpiper] is only partly visible.
For the location 'Broadchalke' I actually located the image on the server and replaced it with a resized one. The list image is as originally resized by the upload process and is truncated, but the full screen now shows my resized one in full. The original is too large to attach here [4MB]. I can see that it is a large file but my users are likely to submit such files direct from their phones, so this was a test of such large files.