Forum Replies Created
-
Posts
-
Thanks!
First bis : in case of non supported cameras do you have any possibility to extend the comptatibility with RawBridge ?
I don’t know yet – I’m sure I can add new cameras, and I think we will get some of the improvements. Still needs investigation, but I’m hopeful.
Second : any possibilities of fine tuning on your side ? If yes what are the types of control ?
Most of the tuning controls are still available.
Third : any thoughts concerning the monochrom raws ?
No idea at all.
Last one : is it good ? ( comparing to Dxo’s )
No idea how it compares to DxO. I do see noticeable improvements in noise reduction with some high ISO Canon RAWs that I have.
Here is the list of cameras in the first developer beta (it’s small but the developer beta is only for a small set of people):
Canon EOS 1500D
Canon EOS 2000D
Canon EOS 5D Mark II
Canon EOS 5D Mark III
Canon EOS 5D Mark IV
Canon EOS 6D
Canon EOS 6D Mark II
Canon EOS R
Canon EOS R1
Canon EOS R5
Canon EOS R50
Canon EOS R5C
Canon EOS R6
Canon EOS R6 Mark II
Canon EOS R8
Canon EOS RP
Canon EOS Rebel T7
Canon R100
Fujifilm X-T5
Fujifilm X-T50
Leica D-Lux 8
Nikon D750
Nikon D850
Nikon Z 6 2
Nikon Z fc
Nikon Z50
Panasonic LUMIX DC-G100
Panasonic LUMIX DC-G110
Panasonic LUMIX DC-S5M2
Panasonic LUMIX DC-S5M2X
Sony Alpha ILCE-6100
Sony Alpha ILCE-6100A
Sony Alpha ILCE-6400
Sony Alpha ILCE-6400A
Sony Alpha ILCE-6700
Sony Alpha ILCE-7 II
Sony Alpha ILCE-7C
Sony Alpha ILCE-7C II
Sony Alpha ILCE-7M IV
Sony Alpha ILCE-7M3
Sony Alpha ILCE-7M4
Sony Alpha ILCE-7R III
Sony Alpha ILCE-7R III A
Sony Alpha ILCE-7R V
Sony Alpha ILCE-7S III
Sony Alpha ZV-E10No. That’s not what will happen. Apple has made RAW 9 an “opt-in” feature. That’s because it is much slower than the existing decoder, and because images can change appearance. They know what they are doing!
I haven’t decided on the details of how RAW 9 will work with Nitro (or RAW Power – I hope both apps will get that feature), but I will not change the decode of existing images without people agreeing to it.
I suppose it’s possible that other apps would just switch their customers to RAW 9, but I won’t.
First, RAW 9 only runs on OS 27, so Intel Macs are out of luck.
Overall, RAW 9 looks great and I will definitely enable it. But, it has higher resource requirements, including memory. That means that some iOS / iPadOS devices may not be good candidates to use RAW 9. Since RAW 9 changes the appearance of images, that complicates matters further, especially when using iCloud or other synching between devices that can run RAW 9, and those that cannot (e.g., Intel Macs). You don’t want to be in a position where you edit an image on one device and it looks different when you open it on another device.
The app doesn’t have an import module. Since an SD card is just a file system volume, people can use the Finder or Image Capture.
People have requested it, so it’s on the feature list for the future. Generally, that kind of import feature is less about copying, and more about dealing with metadata or copying them into specific folders, so it’s can be complex to implement.
Photomator has the same problems that Nitro has – it can open a file, but when it tries to access the folder, it sees no other images. Nitro treats the network share like any other directory – I wrote a test app that I gave to UGreen to show how my code works fine for local storage on iOS/macOS, on the Mac when talking to their NAS, but fails with iOS/NAS.
That’s certainly odd. The images are stored in the Finder and you add a keyword in Nitro but it’s not saved?
Is the XMP data you put in this post from the Nitro XMP sidecar file or is it from digikam or something else?Please try the following:
1. Open Nitro
2. Select a file that doesn’t have an XMP sidecar
3. Rate and add a keyword
4. Go to the next image to make sure it’s written out
5. Open the XMP sidecar in TextEdit or something – is the keyword present?I have heard of the fruit module, but if it only fixes the permissions issues, then it’s not going to solve this problem. What is interesting is that Files.app is able to see into the folders, but my app (using standard Apple calls, which *should* be what Files.app uses) doesn’t.
Thanks for clarifying that. I tried those steps but they did not work.
I think it’s because the Nitro problem isn’t one of permissions (read write vs. read only). It’s that the NAS is returning an empty list of files, period. Permissions wouldn’t explain that because the files would be visible but not openable.
Hi John,
Sorry to hear about this problem. I ran a quick test but was not able to reproduce the problem. This is what I did.
1. Put a CR2 on a flash drive
2. Edit that image in Nitro (on the flash drive). I turned it black and white.
3. Ejected the drive and inserted it into an iPad
4. Add the drive itself to Nitro.
5. Set the rating
6. Entered Edit – image was black and white.Based on your description, the only thing I can think of is that the app was not able to read the XMP file (or couldn’t find it), so it made a new one.
I suggest re-running your test by editing on the Mac, and then going to iOS, but go into Edit first to see if the image’s edits appear. If they do, set the rating or flag. Does that work?
If you unlock the sidebar, then it stays visible (but covers part of the grid). It’s basically waiting for you to pick a container or click in the grid. Then it will stay hidden until you press the sidebar button. When you press the sidebar button, it will appear again as before (covering part of the grid). When you click on a new container (or in the grid) it will hide itself again.
