this post was submitted on 09 Dec 2025
22 points (100.0% liked)
Photography
6523 readers
455 users here now
A community to post about photography:
We allow a wide range of topics here including; your own images, technical questions, gear talk, photography blogs etc. Please be respectful and don't spam.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments

That's just how 360 cameras are. In this case, it's a 16.6MP camera that uses two sensors, each capturing a 180 degree field of view. So that's about 8/9MP per lens.
Your pixel 6 contains an 8MP sensor. I'm not sure what the field of view on the pixel. Lets say it's about 100 degrees for "wide" mode. Much less than that for photos of keyboards and computers.
So, for the 360 camera to give you the same field of view as your iphone, ultimately, you have to crop and deskew the original 180 degree image provided by one of the sensors. But that original image was only 8MP to begin with, so if you crop down to even 100 degrees, you've lost nearly have of your original pixel count, leaving you at 4MP. If you crop down even tighter, than that, your megapixel count goes down even more.
That's why 360 cameras look ass for anything other than wide cinematic shots. Once we start seeing 8K individual sensors on 360 cameras, for a total of 16K (132 MP), cropping will become far more viable. But of course, the downside with cramming lots of pixels in to a small sensor is that you get more noise. And at the moment we just don't have the manufacturing abilitity to make 16K look good on a 360 camera size sensor, at consumer friendly prices. And if you increase the size of the sensor, you increase the size of the camera, which is a deal breaker for an action cam.
I understand the physics of the situation, but I don't get why none of the reviewers have pointed out that strange pixel artifacting, which is really the thing I'm most bothered by. I can deal with a noisy, low quality image, but it just seems like there's some broken post-processing going on.