Yes so far very mediocre performance with 17PM in ProRaw48 mode, much worse comparing to my 16PM or even my old 15PM…
Yes i notice that when i zoom in ProRaw48 photos. I need to try the 24mp mode…I feel like my 17PM camera is blurry 80% of the time. Anyone else?
Read where?I feel like I recently read that they are indeed using lenses that may have defects and using software processing to deal with it.
Well what this guy apparently forgot or didn't know that the 4x has a minimum focus difference in order for the camera to work properly. The 16 pro max 5x camera has a minimum focus distance of 4.5 feet (give or take) and if you are too close, the 1x camera takes over. Same onnl the 17 pro, there is a minimum focus distance. I don't know what it is because I don't have that phone. The Halide app will tell you in settings. As he was taking a photo of his shoes, im sure he didn't meet that minimum and the 1x camera took over. The 1x camera has a minimum of 8 inches. So take that in mind.
Watch this, says more on the issue as well, 48mp photos are hardly a thing
Interesting... I figured the 1x & .5x were the same of the length of years. That's why I didn't upgrade this year from the 16 pro max, I got the Galaxy s25 ultra instead. Full control over the camera which is what I wanted using expert raw. Amazing camera quality.View attachment 2559589
Hardware wise, not much of an upgrade over the last 4 years.
However, instead of updating the firmware for the camera department, Apple cleverly excuses itself for NOT BEING ABLE TO DO SO "because it is baked into the pipeline" which is BS to me to be honest.
iPhone 11 was the first iPhone having night mode and AI photo in general, there is no way it can improve a lot after seven generations, may be like 1% to few % every year now.
Are these crops zoomed in around 600%? The 17 pro is definitely soft. Does the quality improve if the camera is manually focused using a third party app?To me the clarity and the definition, not the sharpness; are much better on my 16PM with Raw and ProRaw files.
17PM suffers from softness and blurriness, witch is not good. Im having at least 30% less quality and information. (Images above {16PM vs 17PM})
And i tested at least 200 photos in ProRaw format.
(Tested 2 personal units as well some from stores).
Got contacted today and the assistant told me that this a now a well known problem. He wasn’t sure if the next 26.0.1 will resolve this.
However i will be contacted again soon.
Yes maximum zoom.Are these crops zoomed in around 600%? The 17 pro is definitely soft. Does the quality improve if the camera is manually focused using a third party app?
I did notice in the reviews of 17P against 16P that the tele photos were somewhat softer. However it looked more like 16 was slightly over processing, in your example that's very clear that 17P just lacks clarity altogether...To me the clarity and the definition, not the sharpness; are much better on my 16PM with Raw and ProRaw files.
17PM suffers from softness and blurriness, witch is not good. Im having at least 30% less quality and information. (Images above {16PM vs 17PM})
And i tested at least 200 photos in ProRaw format.
(Tested 2 personal units as well some from stores).
Got contacted today and the assistant told me that this a now a well known problem. He wasn’t sure if the next 26.0.1 will resolve this.
However i will be contacted again soon.
However this looks to me more like a sensor/lens issue, I assume half the image looks hazy like this when zoomed in to maximum? I had the same issue with a couple 16 Pro Max units. My 17 PM doesn’t exhibit this - it does look softer in some areas and less crisp vs 15 PM, but not out of focus like your samples showTo me the clarity and the definition, not the sharpness; are much better on my 16PM with Raw and ProRaw files.
17PM suffers from softness and blurriness, witch is not good. Im having at least 30% less quality and information. (Images above {16PM vs 17PM})
And i tested at least 200 photos in ProRaw format.
(Tested 2 personal units as well some from stores).
Got contacted today and the assistant told me that this a now a well known problem. He wasn’t sure if the next 26.0.1 will resolve this.
However i will be contacted again soon.