@tapasinthesun I just found where the confusion came from, you shouldn't have seen ApertureValidationError but "At least 2 aperture values are required.".

The translation was fine in every language but missing in English. Thanks for your feedback I'll fix this in the upcoming update.

@tapasinthesun Interesting. The expected format is shown in the placeholder when the field is empty, so users are meant to follow that format when entering custom apertures.

I'll take a look and see if there's a cleaner way to handle this.

Anyways great feedbacks, and I appreciate you taking the time to share it before your trip. Have a fantastic time in the Sierra Nevada!

@tapasinthesun That's really interesting feedback, thank you.

I haven't received this request over the past year, but I suspect that's because most users don't have a collection of cameras and lenses as extensive as yours.

You're right that scrolling through dozens of lenses every time would become cumbersome. I'd love to explore this further and see how Frames could let users associate lenses with specific cameras, making lens selection much faster and more relevant.

@tapasinthesun Hey Rom, sorry to hear about the issues with MetaLog.

Here’s a 1-month free code if you want to try Frames:
https://apps.apple.com/redeem?ctx=offercodes&id=6744057317&code=FRAMES1MFREE

With this, you’ll also have access to the macOS app for metadata reintegration to your scans.

Would really love to hear your feedback after you’ve had some time with it, especially coming from your experience with MetaLog.