Forum Replies Created
-
Posts
-
I don’t know of any such issue. Copy Adjustments comes up immediately for me all the time. Copy Adjustments is only valid if you right click or select an image with adjustments. I’m not sure what could be happening on your machine. Perhaps other things are slow as well?
Copy Adjustments in Photos does not work with the Extension – that is a Photos-only feature. However, RAW Power automatically saves the last set of adjustments you used on an image as a synthesized “preset”. You can go to the next image you want to edit and use the preset menu to apply those those settings. So, in that way you can get the effect of Copy / Paste.
Since Halide uses the photo library, if you use iCloud Photos, then the images will get synced to your Mac and you can use RAW Power there (or Photos). iCloud will send the original RAW.
If you aren’t using iCloud Photos, then you can import them from your phone to the Mac. Photos will import the RAW as well. There will not be any conversion to JPEG as long as you use Photos to import the images (vs. using share or some other means).
If you start in RAW Power for iOS and then save as non-destructive, you can continue editing on the Mac with RAW Power. That will work when using iCloud, which will sync both the editing data and original image. If you don’t use iCloud, then it’s “possible” to import the editing data from iOS, but Photos is very unreliable in this regard (I have no idea if it even works with the latest OS – it’s that sketchy).
Hmm. You have found a bug in the trial mode. I didn’t see it in my testing – sorry about that. It works fine once the app is purchased. I’ll put in a fix for the trial case in the next release.
Yes, I agree that a gradient tool would be very useful. Thanks for your feedback and specific use case.
I put your suggestion on the Customer Requested Feature. I review that list before each new version to see what can be added.
When you use extensions, they save JPEGs into the photo library. When you ask Photos to export, it will just use that JPEG. It does not go back to the original + invoke the extension.
When you are using RAW Power as a standalone app, it is still writing a JPEG into the photo library. However, if you use RAW Power to export, it will generate new images from the original RAW. So, you get full fidelity. That, of course, is only true for images edited in RAW Power. If you edit an image in Photos (or any other editor that uses the photo library) and then export that image in RAW Power, it will use the JPEG because it has no way to invoke Photos to render the image from the original.
If you plan to use multiple editors through the Photo library, then you are inevitably going to be stuck with a JPEG at some point. If you want the highest quality then use RAW Power to edit the image (standalone), export a TIFF and then edit that in the other app. I suppose you could import the TIFF into Photos and then use a separate extension to edit (but again, you have a JPEG at the end).
Yes, it’s doable and some apps work that way. The problem is that the controls then cover the image (which can make it hard to make a precision adjustment) and usually the controls are hard to see because of the overlay.
It’s odd that the app would slow down – the way iOS works, there is no swap file that would lead to slowness the way one might see on the Mac. Perhaps the GPU is slowly getting overwhelmed.
The built-in Photos app now supports RAW images. However, all of the other behaviors are unchanged. I don’t believe anything has changed in iOS 15, but I haven’t looked into it deeply yet.
Apple has surfaced the container folder in Big Sur which is confusing because they only surface the Documents directory of the container.
However, the path should still work (I tried it on Big Sur myself just now): ~/Library/Containers/com.gentlemencoders.RAWPower
Please email support@gentlemencoders.com so I can help you directly.
The RAW Power data is stored in the app’s sandbox folder which is in your home directory. You can copy it to a new machine if you like. However, when you do that, you will need to use the Restore Edits feature of RAW Power to reassociate the edit data with the originals. RAW Power does not track the location of your originals – instead it uses the original’s file system inode (which is an integer). If you move the file around on your disk, RAW Power will still find it, but if you move it to another disk or computer, then it cannot track it automatically. That’s where the Restore Edits feature comes in. The folder is located at
~/Library/Containers/com.gentlemencoders.RAWPower/
-Nik
Yes. This is a bug in RAW Power. I’m working on a fix and hope to have it out next week. Sorry about the bug.
The app doesn’t have brushing. It’s been on the list for a while to do, and I even had a prototype at one point. Then I discovered a limitation with the Photo library that basically invalidated my entire implementation. So, I have to start over. I can’t make any promises for a brushing feature in RAW Power. I feel it’s important to say that so that people don’t make any buying decisions based on the possibility of that feature.
The app doesn’t have a healing or cloning tool. It’s something I’m looking into. If you need that function, then I suggest using the one in Photos or perhaps another extension with that ability.
For best results, I recommend doing the main editing in RAW Power and then heal / clone in the other extension. That way, you have access to the full RAW data for the main editing operation.
