4 ms·

1. The censors do not need to be physically 90 degree aligned to get depth data. And the the crop can be rotated so you do not need to hold the phone at a dutch

1. The censors do not need to be physically 90 degree aligned to get depth data. And the the crop can be rotated so you do not need to hold the phone at a dutch angle... 2. The censors are 24mp and 12mp, way way way above 1080p (2.1mp). A tilted crop sample will be no issue at all. Also you are using the term 'appeal to authority' wrong as I am not referencing an outside authority here, I am referencing myself. I'm sorry I've made you a bit angry here, but just calm it down a bit and think it through. The overlayed images of two cameras are slightly mis-aligned, but the overlapping data is more than enough to produce a 2.1mp image. This can work both in traditional stereoscopic or with 3D generated depth data. I think one thing that threw me though is the the advertising images for this are clearly deceptive. They show 3D generated video that can be viewed from multiple angles, when in actually HVEC is just stereoscopic.

dagmx 3y ago
I’m not angry so much as just annoyed with the glibness of “well you can just do this if you ignore the actual use as a product” Like, sure you can do any number of things if you don’t consider how it’s used at all or what the user experience is.
- tsunamifury 3y ago
  Worked for 10 years on hardware/software integration design with Apple and Google. I am not ignoring the actual use case, I think you just aren't exactly able to conceptualize how the application of how this works. You use the camera normally, the software does all the crop/rotation/overlapping augmentation -- just like the smooth zoom between cameras already does. User knows nothing. Only issue would be if crop overlaps lens positions can't be normalized. But we already did that with smooth zoom.
  - dagmx 3y ago
    Even if we throw out all the technical considerations, you’d still be asking the user to hold the phone diagonally to get the stereo alignment. If instead, you said “hold it normally and we crop/rotate for you” , you would now have two point of views at different heights, you’d have very uncomfortable depth perception. There’s not a solution here that would work with the 14 Pro camera layout unless you used the telephoto and then cropped the wide angle to match. In which case you now have the issue that your users are stuck in effectively a 70mm fov which isn’t very useful for most use. Again, I think you’re ignoring many aspects of the product design to try and say it’s possible.

dagmx 3y ago

I’m not angry so much as just annoyed with the glibness of “well you can just do this if you ignore the actual use as a product” Like, sure you can do any number of things if you don’t consider how it’s used at all or what the user experience is.

tsunamifury 3y ago
Worked for 10 years on hardware/software integration design with Apple and Google. I am not ignoring the actual use case, I think you just aren't exactly able to conceptualize how the application of how this works. You use the camera normally, the software does all the crop/rotation/overlapping augmentation -- just like the smooth zoom between cameras already does. User knows nothing. Only issue would be if crop overlaps lens positions can't be normalized. But we already did that with smooth zoom.
- dagmx 3y ago
  Even if we throw out all the technical considerations, you’d still be asking the user to hold the phone diagonally to get the stereo alignment. If instead, you said “hold it normally and we crop/rotate for you” , you would now have two point of views at different heights, you’d have very uncomfortable depth perception. There’s not a solution here that would work with the 14 Pro camera layout unless you used the telephoto and then cropped the wide angle to match. In which case you now have the issue that your users are stuck in effectively a 70mm fov which isn’t very useful for most use. Again, I think you’re ignoring many aspects of the product design to try and say it’s possible.