260
A bride to be discovers a reality bending mistake in Apple's computational photography
(appleinsider.com)
this post was submitted on 01 Dec 2023
260 points (82.2% liked)
Technology
63073 readers
5857 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
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
Did you look at the example in the article? It's clearly not milliseconds. It's several whole seconds.
You don't need a few whole seconds to put an arm down.
Edit: I should rephrase. I don't think computational photography algorithms would risk compositing photos that are whole seconds apart. In well lit environments, one photo only needs 1/100 seconds or less to expose properly. Using photos that are temporally too far apart risk objects moving too much in the frame, and thus fail to composite.
There's three different arm positions in a single picture. That doesn't happen in the blink of an eye.
The camera is taking many frames over a relatively long time to do this.
This is nothing at all like rolling shutter, and it's very obvious from looking at the example in the article.
Those arm positions occur over the course of a fluid motion in a single second. How long does it take for you to drop your hands to your side or raise them to clasped from the side? It doesn’t take me more than about half a second as a deliberate movement.