Ugly Hedgehog - Photography Forum
Home Active Topics Newest Pictures Search Login Register
Links and Resources
The pros and cons of shooting RAW versus JPEG
Page <<first <prev 8 of 14 next> last>>
Jul 15, 2021 08:32:46   #
Longshadow Loc: Audubon, PA, United States
 
johngault007 wrote:
But it's so much fun to randomly argue and keep him going, for no other reason then to make him over explain some random point.


Reply
Jul 15, 2021 08:41:17   #
JD750 Loc: SoCal
 
Longshadow wrote:
Like I can tell the difference without a big magnifying glass.

There's a question: I wonder how many people take a magnifying glass to a photo exhibit.


I can see the color difference in the images presented.

I do not pixel peep. I view an image from a normal viewing distance. That is me.

However there is a set of people who do pixel peep. That it how they derive enjoyment from an image. I once saw a man at a VanGogh exhibit walking up to inches away and using a magnifying glass to examine the painting. Ok. If that's how you like to view it then go ahead.

Reply
Jul 15, 2021 08:43:21   #
Longshadow Loc: Audubon, PA, United States
 
JD750 wrote:
...
...
However there is a set of people who do pixel peep. That it how they derive enjoyment from an image. I once saw a man at a VanGogh exhibit walking up to inches away and using a magnifying glass to examine the painting. Ok. If that's how you like to view it then go ahead.


Reply
 
 
Jul 15, 2021 08:52:54   #
Delderby Loc: Derby UK
 
JD750 wrote:
The information is there you just have to do the math. Say you have two numbers, 5 and 3 and you do math to get the average of 4. The information was there, you just had to extract it. Which took some energy. So it wasn’t free.
And it’s a one way process because given 4, you can’t say for sure what the original two numbers were.
And that is how an image file is created from a raw file.


But you'd get the same answer from 2 and 6. Where would that leave you?

Reply
Jul 15, 2021 09:00:46   #
BigDaddy Loc: Pittsburgh, PA
 
bonjac wrote:
I am afraid I am one of those poor souls shooting raw for the wrong reason. Can you steer me to a source that explains "production or developer format" and the form of those formats.
Thank you, Jack

Only if the reason you don't edit jpgs is the quality diminishes each time you edit.

Developers format is a proprietary format that some editors have so you can save your edited file in a loss-less format, and maintain your edits so they can be re-edited after reopening the file. File formats are denoted by file extensions, like .txt, .exe .com, .jpg, .png and so on.

The format for a Photoshop (including PSE) developer file is .PSD. In Affinity Photo it's .AFPhoto. In ACDSee it's .ACDC. Interestingly, Affinity Photo allows you to save in .PSD format if you want. As I said, these are proprietary formats so not sure how Affinity gets away with it, unless they license the code? You can actually open a PS .psd file in Affinity. Not sure if all the same stuff is preserved. Generally speaking you can only edit the files with the editor that created them. Many viewers will open various formats, particularly .PSD files but they will not preserve the edits, and they can't re-save in the developers format.

To use these when you save your file in the editor, you'll get a choice of formats to save in. All you need do is select one of the above if using any of the 3 editors I listed. Other editors I'm not familiar with, like Gimp, but they likely have a production format as well. Lighter weight editors, like FastStone don't.

DAGS on the extensions I listed and you should get more information on each type of format.

Reply
Jul 15, 2021 09:00:59   #
BebuLamar
 
Delderby wrote:
But you'd get the same answer from 2 and 6. Where would that leave you?


How do you know for sure it's the average? It's likely but not sure.

Reply
Jul 15, 2021 09:16:50   #
Ysarex Loc: St. Louis
 
Longshadow wrote:
Like I can tell the difference without a big magnifying glass.

There's a question: I wonder how many people take a magnifying glass to a photo exhibit.


You don't need a magnifying glass to see it in Davyboy's photo here: https://www.uglyhedgehog.com/t-308167-1.html#5179241 It's easy to see even in the thumbnail.

I did everything right to keep the degradation to a minimum editing that JPEG -- including choosing the right tools in PS. I could have edited it like Davyboy's squirrel but that wouldn't have been honest. I see that kind of damage all the time looking at photos on these various forums.

Reply
 
 
Jul 15, 2021 09:22:06   #
davyboy Loc: Anoka Mn.
 
Ysarex wrote:
You don't need a magnifying glass to see it in Davyboy's photo here: https://www.uglyhedgehog.com/t-308167-1.html#5179241 It's easy to see even in the thumbnail.

I did everything right to keep the degradation to a minimum editing that JPEG -- including choosing the right tools in PS. I could have edited it like Davyboy's squirrel but that wouldn't have been honest. I see that kind of damage all the time looking at photos on these various forums.


That’s funny that you chose that photo. It is an old photo but probably the most commented on.

Reply
Jul 15, 2021 09:31:50   #
Ysarex Loc: St. Louis
 
bonjac wrote:
I am afraid I am one of those poor souls shooting raw for the wrong reason. Can you steer me to a source that explains "production or developer format" and the form of those formats.

Thank you, Jack


Big Daddy was referring to the proprietary formats of the various editors such as Photoshop's PSD format.

If you're shooting and processing raw images you should pay attention to your overall raw workflow. It may not be entirely possible given what you have to accomplish but if you can work with a parametric raw processor and keep you editing confined to that application you can gain a couple advantages -- may or may not be meaningful to you. I process a lot of images and I value the goal of keeping my raw workflow 100% non-destructive and non-linearly re-editable. To do that you have to work parametrically and avoid using a raster editor like PS, Affinity, etc. as they will often add a destructive element to your work. NOTE: By destructive in this context I'm not referring to preserving the original image but rather to not introducing an edit into your image that would force you to redo your previous work. In that context for example Affinity Photo is a forced destructive editor in a raw workflow.

Another advantage to maintaining a parametric raw workflow is a huge saving in disk storage as those RGB image files like PSD and TFF and quite large.

Reply
Jul 15, 2021 09:33:42   #
srt101fan
 
JD750 wrote:
I can see the color difference in the images presented.

I do not pixel peep. I view an image from a normal viewing distance. That is me.

However there is a set of people who do pixel peep. That it how they derive enjoyment from an image. I once saw a man at a VanGogh exhibit walking up to inches away and using a magnifying glass to examine the painting. Ok. If that's how you like to view it then go ahead.


Nothing wrong with a closeup examination of Van Gogh's brush strokes. But if that"s the only way you look at the painting you are really missing out....

Reply
Jul 15, 2021 09:53:18   #
Longshadow Loc: Audubon, PA, United States
 
JD750 wrote:
I can see the color difference in the images presented.
...
...

But given only one image to view, there would be no difference.

Reply
 
 
Jul 16, 2021 08:21:05   #
BigDaddy Loc: Pittsburgh, PA
 
Longshadow wrote:
Jeeze, I have no idea what my monitor are in bits.
They display nicely. An HP and an Acer, 23/24 inches wide.

Your monitor and your printer are 8 bits. If they weren't, you, and your wallet would know, even if the pictures looked eerily the same....

Reply
Jul 16, 2021 08:30:21   #
Longshadow Loc: Audubon, PA, United States
 
BigDaddy wrote:
Your monitor and your printer are 8 bits. If they weren't, you, and your wallet would know, even if the pictures looked eerily the same....

Thanks.
To me they're monitors.

Reply
Jul 16, 2021 08:46:42   #
BigDaddy Loc: Pittsburgh, PA
 
davyboy wrote:
Never seen the damage could you show a photo of a jpeg with one edit and how bad this damage is. I can’t imagine

Your imagination is working great.
Jpg compression works by combining colors your eyes can't differentiate, then encoding them for compression. Most (all) camera's produce jpgs out of it's raw data, and if the raw data is good, the jpg will be good.

The more compression you use, the wider the variance will be combined. Also, each time you re-compress the same jpg, it will combine more data, and eventually you will be combining colors that actually can be distinguished by the human eye. For this reason you generally would not re-compress the same jpg file over itself. With low compression values, you can do this quite a few times w/o visible affects, but in general, it's a bad practice so keep your original original, and save complicated edits in a developers file format that is not compressed, and preserves your edits for further work.

Reply
Jul 16, 2021 12:04:56   #
Ysarex Loc: St. Louis
 
BigDaddy wrote:
Your imagination is working great.
Jpg compression works by combining colors your eyes can't differentiate, then encoding them for compression.

JPEG works by taking similar color pixels and making them the same color in order to create compressible redundancy. Human eyesight has no trouble differentiating the colors that the JPEG algorithm changes into the same color. JPEG succeeds by making many small changes at the pixel level which are swamped by the overall image resolution.
BigDaddy wrote:
Most (all) camera's produce jpgs out of it's raw data, and if the raw data is good, the jpg will be good.

No. The raw data can be good, even excellent and the JPEG can nonetheless completely suck. How good the JPEG is depends on the processing capability of the camera's software. Camera processing software often makes bad JPEGs from good raw data.

In fact most camera processing software will invariably make bad JPEGs from the best raw data. To get good JPEGs from the camera it's often necessary to compromise the raw data to a degree.
BigDaddy wrote:
The more compression you use, the wider the variance will be combined. Also, each time you re-compress the same jpg, it will combine more data, and eventually you will be combining colors that actually can be distinguished by the human eye.

As noted, human eyesight can distinguish the colors that the JPEG algorithm changes to same colors -- at all JPEG compression levels.
BigDaddy wrote:
For this reason you generally would not re-compress the same jpg file over itself. With low compression values, you can do this quite a few times w/o visible affects, but in general, it's a bad practice so keep your original original, and save complicated edits in a developers file format that is not compressed, and preserves your edits for further work.

This is a non-issue. Just don't repeatedly re-compress a JPEG. It's also a non-issue in that the damage done from re-compression is slight and much less than the damage done by making substantial changes to the tone/color of the image which can not be avoided. Minor to medium edits to JPEGs are successful for most people because the damage done is swamped in the resolution of the image and as such not normally visible.

Reply
Page <<first <prev 8 of 14 next> last>>
If you want to reply, then register here. Registration is free and your account is created instantly, so you can post right away.
Links and Resources
UglyHedgehog.com - Forum
Copyright 2011-2024 Ugly Hedgehog, Inc.