Tweet
Are there any new posters here that are successfully moving (reasonably) high res images (6000x4000) from their DSLR to an iPad, resizing them to the 1280 width limit, and being able to upload them to the site? If so, I’d love to know your workflow…
(Before anyone asks, I know the difference between cropping and resizing, and the distinction of file size vs. image size. I understand about the ‘lossy’ file JPG format with variable resolution qualities, and that once quality has been lost via compression, you ain’t gonna be getting it back again - but what I am not clear about is where and when in my workflow, such losses might be occurring, and how or even IF I can do anything about them!)
So here is my workflow…
I am taking 6000x4000 raw NEF images off my Nikon D7200, and putting them onto my iPad via the Nikon WMU tool - this could possibly be my first mistake, as I think they may be saved with a JPEG file extension, rather than JPG, and it looks like the uploader may not like that. I move the images at ‘Original Size’, so in theory, no compression there, though I expect the simple act of converting from NEF to JPG at the iPad end of the move is imposing some unwanted compression…
After some cropping in the iPad native Photos app, let’s say I end up with a 3891x2326px image (9MP) that is a 1.9MB file size. Now I use a resize app called ReSizer, which allows me to set the image width to 1280, and maintains the aspect ratio to automatically set the height to 765 in this case (which is just short of 1MP). The tool also claims to be maintaining 100% quality, but the resulting file is only around the 100KB mark (I have tried a couple of different image resizing apps with similar results), and so fails the prerequisite MINIMUM file size constraint as well.
if anyone has a workflow that successfully allows Nikon NEF files to be converted, cropped, and resized via an iPad, AND results in an image size that conforms to the 1280 width constraint but is still big enough to meet the 250KB file size constraint, please put me out of my misery.
MTIA
Graham
(Before anyone asks, I know the difference between cropping and resizing, and the distinction of file size vs. image size. I understand about the ‘lossy’ file JPG format with variable resolution qualities, and that once quality has been lost via compression, you ain’t gonna be getting it back again - but what I am not clear about is where and when in my workflow, such losses might be occurring, and how or even IF I can do anything about them!)
So here is my workflow…
I am taking 6000x4000 raw NEF images off my Nikon D7200, and putting them onto my iPad via the Nikon WMU tool - this could possibly be my first mistake, as I think they may be saved with a JPEG file extension, rather than JPG, and it looks like the uploader may not like that. I move the images at ‘Original Size’, so in theory, no compression there, though I expect the simple act of converting from NEF to JPG at the iPad end of the move is imposing some unwanted compression…
After some cropping in the iPad native Photos app, let’s say I end up with a 3891x2326px image (9MP) that is a 1.9MB file size. Now I use a resize app called ReSizer, which allows me to set the image width to 1280, and maintains the aspect ratio to automatically set the height to 765 in this case (which is just short of 1MP). The tool also claims to be maintaining 100% quality, but the resulting file is only around the 100KB mark (I have tried a couple of different image resizing apps with similar results), and so fails the prerequisite MINIMUM file size constraint as well.
if anyone has a workflow that successfully allows Nikon NEF files to be converted, cropped, and resized via an iPad, AND results in an image size that conforms to the 1280 width constraint but is still big enough to meet the 250KB file size constraint, please put me out of my misery.
MTIA
Graham
Comment