Skip to main content
Z
zade1
Participating Frequently
November 6, 2024

I identified a bug in Camera Raw

  • November 6, 2024
  • 2 replies
  • 177 views

I  was promised that this bug would be fixed in the next release of Camera Raw!! There has been a new release of Camera Raw BUT THE BUG HAS NOT BEEN REMEDIED.  I have waited since June 11th to get this remedied as I can process and print my files the way they appear in Camera Raw! Here is the bug reference they sent me Sept 17th. PS-139111

2 replies

D Fosse
Community Expert
D FosseCommunity Expert
Community Expert
November 6, 2024

OK. There are two possible explanations for this:

 

One, if there is a lot of sensor noise, and/or dense star fields (also technically noise), you absolutely need to view at 100%. At any other zoom ratio, different screen resampling algorithms will influence the result. 100% represents one image pixel by exactly one physical screen pixel.

 

If that's not it, your monitor profile is bad, or not the correct one loaded by one of the applications. A defective monitor profile can often affect color managed applications differently. In fact, that's a red flag for a bad profile.

 

Since the conversion into the monitor profile is executed in the GPU, it could also be a GPU driver bug. But that happens more rarely. Usually it's the profile. Are you using a calibrator to make your monitor profile?

 

If you show a side by side screenshot - at 100% view! - that might give some clues.

Z
zade1Author
Participating Frequently
November 6, 2024
Adobe tech has had the raw data and came up with the same results on
their end.
D Fosse
Community Expert
D FosseCommunity Expert
Community Expert
November 6, 2024

What bug? No unknown links please.

Z
zade1Author
Participating Frequently
November 6, 2024
That is not an unknown link - it is the link Adobe sent to me
identifying the bug.  Basically I process aurora images in Camera Raw
and when I open them in PS, the vibrancy of the stars and aurora are
diminished.  Cannot save or print that which I processed.  Just spoke to
Adobe and they said, must to my dismay after all this time, the
engineering team is still working on this bug.
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices