Forum Replies Created
-
Posts
-
Hi Tim,
I can see that the way presets work may be confusing, especially if they work differently in each app. This is how they work in RAW Power:
1) the order doesn’t matter
2) it doesn’t matter if you apply them multiple times.That’s because presets are not much more than an automated way of setting up adjustments. The order that adjustments are applied is fixed (unlike Photoshop with its layers), so whether you apply A+B or B+A, you get the same result (there are some edge cases around automatic adjustments, but in general the order you apply presets is irrelevant).
All that really matters is the Add vs. Replace. Add will combine the preset with the existing adjustments, while Replace removes the existing adjustments in favor of the preset.
A history would provide insight into what operations were performed, that’s true. It’s something I have considered. History usually ends up containing an overwhelming amount of data, so it’s never been something I have found very useful in general (though it is useful on occasion).
However, history would not eliminate add vs. replace because those are different ways of applying presets.
RAW processing is available for any unadjusted RAW image. However, if the image was adjusted by Photos or Photos extension, then you will be editing the JPEG that was provided by that other editor. If it was edited with RAW Power, then you also will have access to RAW Processing. One way to tell the situation is to see if the app offers “Revert to Original” when you first open it. If so, then the image was previously edited (by some app, including RAW Power).
Catas: I know that the LUTs had that behavior before, where it would close the folder if you tapped on it again, but I think I fixed it in 3.0.3. Are you still seeing that issue with 3.0.3?
Yes, I have some ideas for adding that data to the edit interface. However, I dislike covering the picture with anything; I’ll probably put it above or atop the histogram.
Testing completed faster than I expected, so the 3.0.3 trial is now available on the downloads page
Hi. Sorry about the bug. It’s fixed in version 3.0.3 which just went out on the App Store. I’m in the process of getting the 3.0.3 trial finished and posted. Hopefully in a couple of days.
Talking about working on LUT’s, if I am tapping again the same Lut, preset, to disable it, to see the original image, this action will close the folder with that Lut. Will be nice to remain open until I am closing it or I am going to another adjustments.
Yes, I can see that. Instead of tapping on the name, you can also tap on the box next to the word “LUT” that will turn off the adjustment without closing the folder. It’s not as good as what you are asking for, but it’s still better than having the folder close.
Catas:
Since the latest major update of RawPower, with ability to work on files, I am using it more and more, although, still waiting to work directly on folders with images instead of adding them on application.
Do you mean organizing images in folders after you add them, or are you asking to work with folders that are stored on an external disk (“referenced” image, not copied)?
So now I’m trying to share some of my findings. Firstly since the 3.02 update, in “files one up view”, I am not able to see which images are raws and which are jpgs. All I can see is the sign of edited or linked images.
You are right. There is a bug where the grid is not showing the file type. I’ll make sure to fix it for the next release.
Another thing which I don’t like is when double tapping for zoom in and out, in both browsing and editing mode, images are going not so smooth, they are much more stepping.
Yes, I have seen something like this too. It was to fix a bug, but it made some things a little worse.
When working with Lut’s, we have two folders with adjustments when tapping on one adjustment second time that folder are going to be close which is odd.
I don’t quite understand what you mean. Do you want the LUT folder to remain open as you go from image to image?
At the end I would like to have an cancel edit button instead of denying of accepting changes when iOS are asking me. Not to talk that in files I am not asked about.
Some other people have asked about that. I was thinking of putting something in Tools to cancel editing. It’s hard to put it in the toolbar – there is no room on small screens (like an iPhone SE)
Last question about that: how to directly revert to the original?
You can revert to original two ways: One is to tap Reset in Tools or in the Edit menu. Another is to select the image in the grid and pick Revert to Original from the Batch button at the bottom.
Now talking about Halide camera button, can we have option to disable it from settings at least in iPad?
I guess, do you find it gets in your way?
That being said I would like to thank you very much for your great work.
You are welcome!
Right now, there isn’t a one-step way to add a tab of a different kind (File Browser if the current tab is Photos, or vice-versa). I’ll make a note. Once you have a tab open of that type, you can make more tabs directly. Hopefully this isn’t too much of an imposition – the app remembers all the tabs and windows.
It’s definitely possible to add something like that, but please note that you can access the Info tab while adjusting. Just tap Info and you can see all the metadata – this will not take you out of Edit mode.
Yes, I would like to add keyword support, but that’s currently impossible with the Photos library. Apple does not provide 3rd parties with any way to read, modify, or create keywords. I have made a formal request — maybe in the next OS. Don’t really know though.
There is no formal roadmap. I have a very large list of features and fixes that I review when preparing a release. I don’t publish anything because it changes a lot because of a) customer input b) new technologies Apple creates and c) how far behind I am 🙂
My goal is to move from large, infrequent releases to smaller, frequent releases.
In the case of keywords, there is no point even putting it on a roadmap because I can’t write the feature until Apple adds APIs to allow it.
Yes, it is under consideration. I am going to planning feature releases soon, but I don’t have any information to share at this point about content or dates. In the past, I have done very large releases which come out once a year (or longer). Going forward, I want to ship smaller releases that come out more frequently. Files sync is a popular request, but so is brushing and other large features as well.
