Raw files viewed without any editing

Maybe you should supply the source of that information because I don't believe you did that off the top of your head. Maybe your source is wrong. Maybe other sources will contradict your source.
I suggest reading the 1992 ACM paper that he linked.
Thanks but I don't see the link in the post.
 
Maybe you should supply the source of that information because I don't believe you did that off the top of your head. Maybe your source is wrong. Maybe other sources will contradict your source.
I suggest reading the 1992 ACM paper that he linked.
Thanks but I don't see the link in the post.
Before images were common on the internet: https://groups.google.com/g/comp.mail.maps/c/M0QhtyZfjmM/m/SbNT-FVRu6MJ has a portion of a map of all of the computers on the internet in 1988. My name is in this section at the link. Digital images were still not common, but work on the JPEG standard had begun.

By 1992, the primary use for JPEG was images.

Things change. Some of us are so old we remember some of the changes.
 
What I see with DXO PL7, default rendering.



3f0a2d81571f4b8aab694e927e8236dd.jpg
 
What I see with DXO PL7, default rendering.

3f0a2d81571f4b8aab694e927e8236dd.jpg
There's something badly wrong with that rendering — look at the posterisation of the sky. So your default preset is doing something strange.
 
What I see with DXO PL7, default rendering.

3f0a2d81571f4b8aab694e927e8236dd.jpg
There's something badly wrong with that rendering — look at the posterisation of the sky. So your default preset is doing something strange.
It appears that it's an over compressed JPG of 5 or less. Look at this image compressed at JPEG quality 12.



51af2250043d4fc39ff5935051ee77b4.jpg



--
Tom
 
What I see with DXO PL7, default rendering.

3f0a2d81571f4b8aab694e927e8236dd.jpg
There's something badly wrong with that rendering — look at the posterisation of the sky. So your default preset is doing something strange.
It appears that it's an over compressed JPG of 5 or less. Look at this image compressed at JPEG quality 12.

51af2250043d4fc39ff5935051ee77b4.jpg
Yes, I think you're right — the file is tiny (only 665KB, rather than 4MB+).
 
PhotoLab always applies a preset when opening a raw image.
Can you tell it not to?
I don't think so. But you could choose a do-almost-nothing preset (eg, optical corrections only). Or, I suppose you could create a preset that does nothing at all.
If you're allowing a preset to be applied, when it need not be, then the complaints being levelled against you are valid.
I want my custom preset to be applied automatically. That's why I created it. It's my zero-click option. The whole idea is to minimise the amount of manual editing that I need to do with the typical image.
I understand that but the issue that everyone seems to be having is that that's not what you asked them to do.
It's exactly what I asked them to do.
"So, let the program do its normal automatic processing to show the image,"

Quote from your opening post.

No mention of personal presets etc.
I was interested in what they see when they first open a raw image, and showed what I see when I open a raw image in various products that I use.
If you, or anyone, is applying a preset/action/call it what you will, then you're not seeing the raw as the app. modifies and displays it by default.
But I am.
But you're not.

You're seeing the raw adjusted to suit you.
It's what PhotoLab does by default for me. It might do something else by default for someone else. PhotoLab itself doesn't have a default
Above, you say that Photolab does open raws using a default preset and that you don't think it can be turned off.

Make your mind up.
— users choose the default settings they prefer. Indeed, as I showed in my first post in the thread, I use different default settings in PL7 to those I used in PL6.
As is usual, you're twisting the dialogue to promote your own views.

Next stage, I guess will be name calling. It usually works that way.


"It's good to be . . . . . . . . . Me!"
 

Keyboard shortcuts

Back
Top