Forum Replies Created
-
AuthorPosts
-
Nik BhattKeymasterHave you tried the Build Thumbnails command?
Nik BhattKeymasterI can’t speak to alternative software for UGreen. As far as alternative NAS, I have been gotten Synology to work (I don’t remember the model), a Raspberry Pi (!) and a Mac mini. So, a range of devices will work.
Nik BhattKeymasterAuto Advance only works when you are in the viewer (showing a filmstrip on the bottom). It does not auto advance when showing the thumbnail grid. Is that what you are seeing?
Nik BhattKeymasterNo, there isn’t a way to do that. Media Types are auto-detected by Apple’s code and they cannot be changed. I cannot even change the media type programmatically.
Nik BhattKeymasterThere may be a way for you to configure the NAS to work, since we have examples that do work, but since I don’t know why it doesn’t work for UGreen and others, I don’t know what to tell you 🙁
Nik BhattKeymasterSome NAS are not compatible with Nitro on iOS. For example, UGreen doesn’t work. However, Synology works, as does something as basic as a Raspberry Pi. Unfortunately, I don’t know why UGreen and others don’t work. I have talked to UGreen. I have talked to Apple’s engineers. No one seems to know. The reason it doesn’t work is because Nitro reads entire folders, not individual files, and the NAS are not able to provide a list of files. On Mac, this is not an issue – it’s the way the iOS works.
Nik BhattKeymasterYours is the first complaint I have received about color or luminance masking. I would need more information, sample images, etc. to look into the issue. It is not a magic wand selector. In general, I view color and luminance masking as a quick starting point, where you use the eraser tool to remove areas you do not need.
Nik BhattKeymasterThe video description has an attachment for an image that you can download and use as a test target. The video also shows how to take images to use to train the lens corrector.
Yes, I’m looking into Lensfun.
Nik BhattKeymasterIf you take a sample image and follow the instructions, then it should create the necessary information to automatically correct images. It’s hard to tell based on your description what is not working. If you aren’t using the sample image approach (grid lines), then you can use a RAW+JPEG pair and try to match them, but that can be hard depending on how exact you want the correction. I’m hoping to add more lens profiles to the app in the future, but there is so much other stuff I have to do first…
Nik BhattKeymasterUnfortunately, Apple’s list includes all cameras they support, regardless of decoder version. They do not break out v9 separately and the v9 list remains quite small. I have a page on my own site which lists the v9 supported cameras: V9 Camera List
In addition, DNG files will work with v9, as long as the DNG is not linearized. ProRAW files are linearized, so they are not eligible for RAW v9.
October 10, 2026 at 7:31 am in reply to: Is Apple getting more serious about photography with macOS 27? #152218
Nik BhattKeymasterNo, that is a different thing. Are you using the purple and green fringe sliders? Those are designed to remove purple and green from high contrast edges but should not be affecting the overall image. of course, if you crank up the range slider, it can affect more of the image. You might try using a mask for the area you want to correct and use the CA sliders on the mask.
Nik BhattKeymasterYes, there is a plan to offer more flexible naming of sidecars. The reason that Nitro uses this _jpg.xmp is that Adobe never specified a standard for JPEG / TIFF / DNG for a separate sidecar. They require that the XMP data be written directly into the RAW. Many photographers I have talked to feel strongly that their original images should never be modified, which is in direct conflict with Adobe’s position. The problem with using .xmp for JPEGs is that it will cause data loss when shooting R+J. Both the RAW and JPEG would be sharing a single sidecar, but can have different metadata (e.g., different ratings or flags). Because ratings (for example) are in a standard location, there is no way to have one sidecar represent two independent files. While it is also true that one could “stack” the R+J images as a single entity, people do not always want that, so the solution doesn’t really handle all cases.
Nik BhattKeymasterApple’s decoder does not adjust brightness consistently in those cases. It does appear that they look at the DR settings. If you are exposing down, then yes, the image will look darker. Lightroom may be brightening the image to more closely match the JPEG; in general Apple does not attempt to match the JPEG.
October 9, 2026 at 5:23 pm in reply to: Is Apple getting more serious about photography with macOS 27? #152213
Nik BhattKeymasterLens Profiles are more complex than they may appear. Some cameras have lens data, but Apple cannot read it (Canon falls into this category – we have found some camera bodies write formats that are mish-mashs of known formats and Apple’s code can’t cope). I have filed bugs about this but no fixes so far.
In addition, sometimes the camera writes data Apple can read, but for a given lens, there isn’t data. This happens more often with telephoto lenses where there is little or no correction for distortion or vignetting.
In the future, I hope to have more lens correction functionality, but it will have to wait until I complete other tasks.
October 6, 2026 at 5:35 pm in reply to: Is Apple getting more serious about photography with macOS 27? #152201
Nik BhattKeymasterI’m happy that they have been investing energy in this area, whatever the motivation.
-
AuthorPosts
