Forum Replies Created
-
Posts
-
I have not spent any time looking at film simulations, so I don’t know how they might best be supported in the app. That said, I have received a number of requests for it, so it’s on the list for a future release, but I can’t promise anything right now.
Thanks for the question. This is an oversight. Let me look into it to see if there is a simple fix that could be made in the near term. My idea is to basically have folder default to a particular sort (either via preference or whatever the last one was), but I don’t know yet how difficult those would be.
Hi,
If you are using Photos, then you want to use the RAW Power Extension.
You access this within Photos’ Edit view. Click the “…” button and select RAW Power.
When you use the extension, editing information is stored inside the Photos library and edits are non-destructive.
Note: RAW Power will get access to the RAW, unless the image has already been edited (by Photos or by another extension)The “Edit With” feature of Photos converts the RAW to a TIFF and sends that instead. “Edit With” is intended for applications that don’t support RAWs.
Hi Dmitri,
1. I’m not sure why the file sizes would be so different. I do not know how Camera+ does its decode or its export, so it’s hard for me to know for sure. However, it is true that RAW Power TIFF images on iOS are floating point, so they may not compress as well as integer ones. I am working with Apple on a way to create 16-bit integer tiffs using their libraries.
RAW Power generates 16-bit integer PNGs so that is an alternative — they are also losslessly compressed.
2. Pixelmator is able to open 16-bit floating point TIFFs from RAW Power — I just tried it.
3. RAW Power does not have all the features that you listed (like healing or brushing), so it cannot fully replace applications for customers that need those features. It is possible to add many of those features to RAW Power and most of them are on my list for the future. However, there are a lot of features on the list, so I cannot make any promised about when those might appear.
Hi,
Sorry you are encountering the issue. There is a bug in Mac OS that can cause this. Please try the following:
Go into preferences and look for GPU Compatibility:
You want to choose “More compatible”.
Quit the app and reopen. Then try your export again.
The DNG is unedited, and does not have a standard color profile (its profile might be described as “camera profile”). The image that you sent does not have colors that push the limits of the sRGB gamut. As a result, there is no difference between the narrow gamut files and the wide gamut files. Generally, you need very saturated colors to get the benefits of wide gamut (your image has neutral colors for the most part). If you look at this page, you can see images that show the advantages of wide gamut. All use very saturated colors: WebKit samples
I ran some additional experiments, using RAW Power and also Photos. In both apps, if I export your photo unmodified to sRGB and P3, the images are the same. Only if I make a larger change (saturation + white balance) to push the colors, do I get different images.
If you want to do something similar to see the difference, then apply these two adjustments: White Balance = 10000, Saturation to 2.0. You will see the difference on export.
Hi,
I have looked into this usng the image that you provided (thank you for that).
– The image itself is narrow gamut in general, so there is no difference between sRGB, P3, etc.
– To generate an image that pushes the gamut (and tests this), I did this:
a) saturated it / adjusted brightness down
b) cranked up red in Curves
c) turned off gamut mapping <- important step because gamut map will try to bring colors back into gamut. Here is the image (I totally overdid it, but the goal was to ensure that different exported images showed different ranges of color):
If you create something similar in RAW Power and export it to sRGB and P3, you will see a distinct difference in the two images.
Sorry for the time it took to reply — most customers send bugs via support@gentlemencoders.com and I was remiss in checking this channel as well.
Hi, can you tell me more about where you see the file size? RAW Power for iOS shows pixel sizes, not file sizes.
The original is never modified, but when you edit an image, there is a full size JPEG created. Perhaps that is the size that you are seeing.
Thanks.–Nik
Yes, this is something I have planned for version 1.1. The tricky part is the workflow for this “export feature”.
There are two obvious places to put the UI:
1) In the Share Sheet
2) In the Edit UIIn the Share Sheet, there is already a save to Files, but as you point out, that will save a JPEG. I could add some extra choices, like Save TIFF to Files or something like that. It’s a little tricky because the original image may not be present, so the app would have to download the image and render (since you wouldn’t be in Edit at that point)
The Edit UI may be a better place for this – there could be an Export button or something that allowed you to export the image right from there. You could choose to save it normally into the library or not.
Or perhaps, it could be connected to the Done button -> by default it would save to the library, or perhaps a preference would prompt you, giving you choices of what to do, including “save to the library” or “save JPEG to Files” or “save TIFF to Files”. Or maybe even save as a new image in the library.
I’d like to avoid doing all of them, and I don’t want to make the UI very clunky. I’m interested in your (and other customers’) thoughts on this. Space in the UI is pretty limited right now, especially on a small screen iPhone.
Neither of those cameras gets lens correction through Apple’s RAW engine, so you will need to use DxO for that. To further your experiment, you can export an image from RAW Power (a JPEG) and import that into Photos. Then try DxO to see if it can correct the lens distortion from the JPEG. I am pretty sure that if that works, then it will also work the same way when you use the RAW Power extension.
Hi Tatami,
It is possible to use both extensions, but unfortunately, only the first one you use for an image will get the RAW. The second extension will get a JPEG generated by the first extension. So if you use DxO first for lens correction, you will not get access to the RAW Processing adjustment in RAW Power. If you use it the other way, then RAW Power will get the RAW and DxO will get a JPEG made by RAW Power.
I believe using RAW Power first is the best choice because DxO can perform lens correction on the JPEG created by RAW Power. Please note that RAW Power has built-in lens correction for some cameras, so depending on which camera you have, you may not need DxO. If you want to see if your camera gets lens correction, you can download the trial from our home page.
While extensions are generally non-destructive, this does not apply to sequences of extensions. Once you edit with a second extension, you cannot go back to the first extension and change your edits.
