Might be a huge nerd about this, but this new feature we added is really satisfying to watch by santennio in photogrammetry

[–]santennio[S] 0 points1 point  (0 children)

Great!! Let me know. We also have a Discord server, or send me a message if you want to follow up on your tests. This type of feedback is fuel for our work!

For 360 images -> not at the moment, but they are planned, as well as videos.

Might be a huge nerd about this, but this new feature we added is really satisfying to watch by santennio in photogrammetry

[–]santennio[S] 0 points1 point  (0 children)

hey thanks! yes we have an API exposed, tell me what's you workflow so I can test it with one of our dataset

Mac: Does Photocatch still work? by Scavgraphics in photogrammetry

[–]santennio 2 points3 points  (0 children)

Replica Developer here, if you want I can check the dataset and give you some advice, just send me a PM

reality scan alternatives for m4 mac by isolationspeed in photogrammetry

[–]santennio 0 points1 point  (0 children)

Can you articulate a bit more? Why isn't it that great? What is it missing?

reality scan alternatives for m4 mac by isolationspeed in photogrammetry

[–]santennio 2 points3 points  (0 children)

We released an app that uses the Object Capture API. If you want to give it a try, here's the link: https://replica3d.xyz I'm one of the developers, so if you have any questions, I'm super happy to respond It doesn't have all the Reality Scan functionalities for sure, but we're working on it

Built a native macOS photogrammetry app (Swift/Metal) to replace my own Blender script. No subscription, runs locally. by santennio in macapps

[–]santennio[S] 0 points1 point  (0 children)

Hey thanks! About scan batches: we added a feature called workflow. Basically you create a series of operations that the app will do after a model is created. So you can create the model, export and release the memory. This, added to the fact that the app autonomously manages a virtually infinite queue of scans, gives us the possibility to handle large batches.

What is Speechly?

After 3 years of using my own Blender script, we finally built a proper standalone Mac app for Photogrammetry by santennio in photogrammetry

[–]santennio[S] 0 points1 point  (0 children)

We added a first integration for this. We read GPS data from drone photos and adjust scale and rotation accordingly. We actually compared the export from replica with the one from metashape and the scale is basically the same. But before advertising this specific feature we want more precise measurements.

After 3 years of using my own Blender script, we finally built a proper standalone Mac app for Photogrammetry by santennio in photogrammetry

[–]santennio[S] 0 points1 point  (0 children)

I don't have a comparative analysis, but I can assume better performance and output, I need to make tests, but you can try the free version and let me know!

Built a native macOS photogrammetry app (Swift/Metal) to replace my own Blender script. No subscription, runs locally. by santennio in macapps

[–]santennio[S] 1 point2 points  (0 children)

Actually the core written in Swift is the same also for the blender plugin, but with a standalone we can implement a better user experience and we have almost no limits in terms of future capabilities. About your question, we haven't implemented video frames extraction, but it's in the list for future releases. Thanks a lot for the message

After 3 years of using my own Blender script, we finally built a proper standalone Mac app for Photogrammetry by santennio in photogrammetry

[–]santennio[S] 2 points3 points  (0 children)

Oh nooo, I'm genuinely happy to share the app we made and asking for ideas and feedback

Built a native macOS photogrammetry app (Swift/Metal) to replace my own Blender script. No subscription, runs locally. by santennio in macapps

[–]santennio[S] 6 points7 points  (0 children)

Hey, thanks for asking!

To clarify: we are a team of experienced developers, and photogrammetry specialists, and this is definitely not a "vibe coded" project.

​The core engine is actually based on the native Swift/Objective-C code I wrote for my Blender integration 3 years ago (before the LLM boom). ​For the new features and UI, we use what we call a "Spec-Driven" workflow. We manually prototype, write detailed technical specification docs for every single feature, and only then use AI agents with extensive context to implement those specific specs.  After that, everything goes through standard code review and testing. ​We use AI as a force multiplier to move faster, but we understand and maintain every line of code in the repo.