Forum Replies Created
-
Posts
-
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.
Hi David,
On iOS, the referenced folder system is intended for external drives rather than cloud-based services. iCloud files that are downloaded already do work, but it’s not the target workflow. The limitations are due to the way sidecars are managed in the app, which are not stored with the images – they are stored on device. That’s why changes do not propagate. The goal was to avoid requiring people to copy images to their devices as opposed to create multi-machine workflows. That is a larger, future effort.
As far as release notes go, they are available in the app. On iOS, you can find them in the menu on the main screen. On Mac, they are available in the Help menu. Today, I also added them to the support page: https://www.gentlemencoders.com/support/
I hope that helps.
Yes, I wrote on the thread earlier today that I think I have a fix for that. This week is WWDC so I’ve been busy with that. I will try to get a beta out with that fix. If any of you want to be on the beta, then email beta@gentlemencoders.com with your AppleID’s email address (that’s what Apple’s TestFlight uses to send out beta builds).
I am able to reproduce the problem with Auto Enhance with Levels. I’ll have to see what’s going on – probably just a mistake in mapping the parameters. When that happens, the controls end up on top of each other, which can create invalid positions, which might lead to a crash. The fix is a) map the points properly and b) clamp the levels controls so they cannot overlap.
By the way, it’s much faster to email me than to post here – I have many different things to check and the forums often get skipped. So, please use the forums for discussion and email for bugs: support@gentlemencoders.com
