Hacker News Reader

Comment by somishere | Hacker News Reader

Very Interesting project! esp. when compared to the swathe of junky or overly complex photogrammetry tools out there from a few years back (but mostly still polluting the app store)

I've only recently been trying out poly.cam which is probably the best example of a user friendly workflow ... but it's knowingly priced. Have you guys got a pricing model in mind? Also do you have any documentation around best practices/results, etc?

Anyway sounds like things are going to pick up again quickly with apple's new APIs. Good luck - exciting times ahead!

View on HN

As far as best practices, Apple has some documentation on how to use their photogrammetry pipeline:

https://developer.apple.com/documentation/realitykit/capturi...

Hey Nobbis, I've just requested an invite to your SDK competitor to Apple and others. What you've done looks great and I have a few questions:

  - Does your solution have the same photogrammetry requirements as the Apple/others?

  - Is there a reason you're only supporting iOS at this time? Is that because you're using an iOS framework, or because you're relying on a file format (say HEIC)?

  - How long until you guys open up the API?

Keep up the good work!

Thanks for the tip!

I'm making a "how-to" video now. I've yet to do the voiceover, but here are the raw slides: https://files.littlebird.com.au/take-great-shots-cXH2CM.m4v

The TL;DR is:

  - Avoid thin objects
  - Avoid reflective objects
  - Avoid transparent objects
  - Avoid objects that deform
  - Hardshadows are not good, use soft lighting
  - Your photos should have a crisp focus and be well lit (across the object) 
  - Things work best when the background has a solid colour
  - Make the object take up the full frame (more data for the algorithm)
  - Make sure to get shots from all sides

Reply on news.ycombinator.com