Google Pixel camera consistently blurring out The North Face logo (opens in new tab)

Odd. My Pixel 6 is really quite a good camera. The stock app on GrapheneOS is great when you just want to take a quick photo, and OpenCamera is full featured and very useful when you want to tweak the settings and fiddle around with various options.

I never have anything weird.

The iPhone always messed up the colors of the PNW for me. It was one of the reasons why I finally took the leap and got an SLR style body before I moved there.

I have no issue using e.g. AI-assisted patch and heal tools in Photoshop and Lightroom. I have control over the use of the statistical priors there. But I don’t want the camera taking the pictures for me.

I’ve had the same experience. Switched to the pixel 6, had it for a year, bought the iPhone 15 Pro. I make a hell of a lot less than a lot of the commenters here, so the decision to do so was incredibly costly. I made it, in part, because I take a lot of photos.

At its best, the Pixel produces phenomenal photos. At its worst, they are horrendous. The iPhone consistently does well. With the Pixel I was getting disgusting over-sharpening, to the point I would screenshot photos as a few seconds after taking them. If I didn't screenshot, I would watch in dismay as the post-processing ruined it. The lens flare was frequently awful — lines that swept across the entire image. When I complained, the community said I should leverage this flaw in an artistic way. The video was awful, and the microphone was noisy. A few of my photos have had inexplicable black squares. Occasionally the camera lagged or crashed. My iPhone camera has messed up, but not like the pixel does.

I don’t know why everyone seems to think it’s better. Maybe somehow mine was defective, but I could find posts to corroborate every issue I had.

Do those phones do this even on alternative photo apps?

Weird, last 3-4 phones I owned were Pixels, never ever had a single issue.

> It's an interesting observation, but I couldn't replicate this by taking a photo of a Google Images search for "north face logo"

Low-level artifacts for screen photos are different, so whatever neural net messes things up here, acts differently.

I didn’t think much either until I saw this photo he shared in the comments:

https://www.reddit.com/media?url=https%3A%2F%2Fpreview.redd....

Seems to be more than a one off odd photo and an artifact of something the pixel does re: image processing.

I wouldn't expect this to be a very good test as I'd think the camera could easily tell the difference between taking a picture of a screen and taking a picture of a jacket.

On the other hand, another user tried on a black North Face coat and it didn't happen I wonder if the red is the connecting link between the two.

Could it be a classic LED flicker in this case? Assuming the dashboard backlight is powered by LED lights.

I recall one where people didn't have enough upvotes or something and were basically outcast, close enough?

It could be dismissed under Daubert. You'd need an expert witness to show that the camera in question does not provide evidence in a way that follows well established scientific methods, or doesn't have a known error rate. The judge is then the gate keeper and can choose if it's suitable. For a camera that applies a bunch of random hacks that the engineering team pulled out of thin air, it seems possible.