Skygod44
oversupply of characters
As many an ex-POTNer and current FoPFer know, I have no shame, don't possess an ego, and come here to share all: the great, the good, the bad, and in this case, the stupid! 
So, read on fair friends, and you can laugh at me as much as you like.
When I used to do pro work after switching to digital from film, like so many others I learned to import RAW files to Lightroom for editing, and then poured over the images in excruciating detail for my clients.
But as I pulled away from pro work from 2013 onwards, editing RAW files on a PC seemed like a lot of hard work with no real, tangible reward...
...so in recent years I've been editing on the fly, on a smartphone, often in my car next to where I've just taken photos.
Oh the JOYS of only considering the image as a whole, and not caring about pixel-peeping!!!
BUT (yes, here it come!) I zoomed in on a beautiful image on the rear screen on my new & shiny OM-3 last week, and then when editing the image on the larger screen of my smartphone, this thought crept into my head: "Nope! That's not as detailed as it should be
".
Now, I've always known that exporting an edited image ready for uploading to the 'net requires a choice being made as to the size/jpeg setting.
But after some digging on Tuesday, I discovered that editing software can, in some cases, choose to downsize files when importing from a camera without me, the user, being involved.
What an idiot I felt, I can tell you!
In fact, the automated width-to-height chosen wasn't too far off what images need to be reduced to, for FoPF...so it's not an unmitigated disaster.
But the true file size my camera produces is at least 10X bigger.
I think there's a high chance that some (many? all?
) of my images since using a smartphone for editing may be missing a certain je ne sais quoi, simply due to this error.
So, from now, when I'm shooting subjects with a lot of detail, I'll be certain to check the IMPORT file size first.
Lesson learned.
Cheers all,
Simon
So, read on fair friends, and you can laugh at me as much as you like.
When I used to do pro work after switching to digital from film, like so many others I learned to import RAW files to Lightroom for editing, and then poured over the images in excruciating detail for my clients.
But as I pulled away from pro work from 2013 onwards, editing RAW files on a PC seemed like a lot of hard work with no real, tangible reward...
...so in recent years I've been editing on the fly, on a smartphone, often in my car next to where I've just taken photos.
Oh the JOYS of only considering the image as a whole, and not caring about pixel-peeping!!!
BUT (yes, here it come!) I zoomed in on a beautiful image on the rear screen on my new & shiny OM-3 last week, and then when editing the image on the larger screen of my smartphone, this thought crept into my head: "Nope! That's not as detailed as it should be
".Now, I've always known that exporting an edited image ready for uploading to the 'net requires a choice being made as to the size/jpeg setting.
But after some digging on Tuesday, I discovered that editing software can, in some cases, choose to downsize files when importing from a camera without me, the user, being involved.
What an idiot I felt, I can tell you!
In fact, the automated width-to-height chosen wasn't too far off what images need to be reduced to, for FoPF...so it's not an unmitigated disaster.
But the true file size my camera produces is at least 10X bigger.
I think there's a high chance that some (many? all?
) of my images since using a smartphone for editing may be missing a certain je ne sais quoi, simply due to this error.So, from now, when I'm shooting subjects with a lot of detail, I'll be certain to check the IMPORT file size first.
Lesson learned.
Cheers all,
Simon
