-
Content Count
170 -
Joined
-
Last visited
About IndigoMoon
-
Rank
Advanced Member
Recent Profile Visitors
1,294 profile views
-
-
-
-
Metadata/EXIF Lens Identification
IndigoMoon replied to IndigoMoon's topic in Pre 1.9 beta thread archive
Hi Chris and Tom, first of all, thanks for that! Unfortunately the Lens field in EXIF is empty now (#532), instead of e.g. 24-70 mm. Btw in Detail the Lens Model and Lens is shown correctly as 24-70 mm. Another thing would be great, if you could keep the last tab in the manual lens correction (e.g. Favourites) instead of going back to All after a restart of Photo. Thanks to the QA and the Devs! -
-
Since I suspect that this has the same background as discussed in this thread Identification of Tamron lenses mounted to Canon bodies I would suggest to be more consistent in such cases: a. to enter only the neutral focal length like 24-70 mm instead of Sigma 24-70mm f/2,8 IF EX DG HSM or Tamron 24-70 mm f/2,8 Di VC USD or even in some cases an empty field b. to enter the manually selected lens profile after develop Btw a. is how Lightroom deals with such issues.
-
-
-
-
Text Types
IndigoMoon replied to AHARRIS22's topic in Affinity on Desktop Questions (Mac and Windows)
Ah okey, now I've got it! Thanks a lot for your help and the file! I've created the whole stack (echoes) of characters as one symbol, which couldn't work... -
-
Text Types
IndigoMoon replied to AHARRIS22's topic in Affinity on Desktop Questions (Mac and Windows)
Hi Garry, thanks for that, but it drives me crazy How do you achieve to change the characters including the echos?? For me it doesn't work. -
-
Thanks Tom! Yes, it's not a big deal to select manually the correct lens now. Additionally, it would be great, if I could define a standard lens for such cases. So, for the next time the right body/lens combination will be selected automatcally (similar to Lightroom). It's already fantastic to mark the correct lens as Favorites, but such a feature would be the cherry on the cake.
-
I did some further investigations, and it looks like, that this behaviour is somehow related to the pixel dimensions of the image and/or the resolution of the display (as @sat312 already pointed out). Hope you will get this fixed for the last Google version, even if DXO already did it for their version.