Forum Replies Created
-
Posts
-
Hi TN Args,
Thanks for confirming my issue too.
I’m still seeing this issue, but have ended up not using Auto Enhance much at all – almost never on a Raw images, and sometimes on JPEGs if they’re from an iPhone.
I have found that it doesn’t matter if I use Batch to apply Auto Enhance to a selection of images, or if I apply it individually using the button at the top of the adjustments panel.
I must admit I haven’t checked to see if this is the same when I turn off Levels in the preferences, and use Curves instead. For my own preference I use Levels, as I find I just get along with it better (and I prefer starting with the ‘Luminance’ setting). But when I have recently tried it, it does often go to that ‘crazy’ setting with all the points shoved over the the left side – that seems to happen on poorly exposed images, and then crashes as soon as I try to correct it. It doesn’t need to have done the crazy thing though, any time I adjust the Levels after Auto Enhance, it will crash.
But for now, this problem has actually made me work better manually, and I’ve found a good workflow that works for me without needing Auto Enhance.
Regards.
Hi again Nik,
Just an update on this one. Since I’ve been learning more about my workflow with editing in Raw Power, I have been doing most of my editing manually, and had little trouble overall, apart from the odd ‘quit’, it’s been fine.
Just recently I was experimenting with using the Auto Enhance function (clicking the magic wand icon), mostly to see whether I preferred curves or levels as a setting. I generally find I prefer to work with the Levels panel myself.
However, from that I have found that the crashing has been more frequent. After a little more editing, using different workflows, it does seem to be pretty frequent when trying to carry out further edits after using Auto Enhance. It doesn’t seem to matter what edit tool I use either, I can get the crash as I’m about to select almost any of the editing tools, although it does seem more frequent in the Levels panels.
Another pointer there, when using the Auto Enhance, some poorly exposed images can get unusual results in the Levels panel, i.e. the adjuster tags are all shifted to the left (blacks end) end of the scale, and it’s made the image completely blacked out. If I try to adjust one of those, it crashes almost every time. If I use the Levels panel’s own Auto adjust button, it does a better job of correcting the exposure, and I get no crashes (or at least very rarely – once every few hundred or so images).
If I go back to editing fully manually, then I also very rarely get a crash, similarly once every few hundred images or more.
Cheers
Andy.
Hi Nik,
Just an update on this. I’ve been using Raw Power for all my editing since migrating over to Photos on my iPad Pro in July last year. I’ve been working through my image collection to re-edit them all, so have been able to experiment a fair bit, and try different methods.
Overall, it’s proving to be a great decision, Raw Power is doing all I need for my initial processing, seems to have become more stable, and the editing results are giving me images I’m very happy with.
But going back to this query about activating the Raw Processing module, I’m still a little puzzled by the (seemingly) randomness of it, after some observations.
Initially I can see why it may, or may not need to be activated, but after doing a lot of editing, covering a few different cameras, I can see that it might be more useful to be able to activate it for all Raw images.
But, when looking at the sliders on each image (whether activated or not), it’s clear that the base settings can vary quite a bit from image to image. For example, the black point level is different between my Nikon DSLR (level 3.0) and images taken with an iPhone (level 9.0), I also note that the other settings may also vary, probably according to ISO adjustment etc. (all of them can appear at different values) – most usually Luma and Colour Noise can be different, as can Raw Sharpen, and sometimes Moire is different.
Now, I’m just curious, but is this a process that’s part of the Apple Raw Processing engine, that applies some settings according to camera data? or is it a Raw Power process that reads the data and sets accordingly?
In either case, are these actually still applied to the image if the module is not activated? The question there is do I only need to activate the module if I want to change any of those settings.
I had tried turning it on using a preset, so I could batch apply, but that only applies a fixed set of adjustments to all of them (which is actually how I first noticed this happening, as it highlighted the changed adjustment sliders).
And, thank you for an excellent app, it’s the main thing that’s made my switch to the iPad, and to Photos from Lightroom, possible, and almost pleasure.
Regards
Andy
Thanks for clarifying that Nik. Yes, I see that Halide hasn’t been optimised for the iPad (yet). I was only being a little pedantic that Halide does run on the iPad, and still takes good pictures if used, although I have to admit I don’t very often use the iPad to take photos anyway (it’s a bit cumbersome).
Would it be better (if at all possible) to contextually hide the button if Halide isn’t installed?
Best regards,
Andy
I’m seeing the camera button on the iOS version here too (iPhone 6s), it links to Halide here (which I also have installed). Isn’t that expected behaviour?
On my iPad Pro I’m not seeing the icon, so I’m guessing the link to Halide isn’t available or working on an iPad?
Both up to date.
Regards
AndyYou’re a bit of a star Nik :-).
I appreciate that iOS will be more restricted than the desktop OS, so I’m never expecting everything to be the same, I just mention things in case they can be achieved.
Cheers.
No worries, at least it’s not as badly iOS limited compared to the Adobe options 😉 (which is one reason why I’ve switched).
No, nothing there at all Erik, there is New, then a naming dialogue with ok and cancel, then that’s it, it’s created. In Edit, I only see a delete symbol or a move symbol. Nothing else.
To confirm, iPadOS 14, not desktop.
Looking at the documentation, it is there in the desktop version, but not mentioned for the iOS version.
For sure, camera default presets would be useful.
Cheers.
Andy
I’ll have a look in the documentation, but I can’t see anything that allows for any of that to happen? (IPadOS 14). There’s only the options for a New Preset, which only offers a name for it, or Edit, which only allows re-ordering or deleting. A far as I can see here anyway.
Cheers.
Just following on from your discussion about editing.
I’ve only just started using Raw Power in the last couple of months, since getting my iPad Pro, and deciding to switch to it as my primary computer device. I have owned RP for some time on the iMac, but didn’t find many occasions to use it. So, I have been experimenting a bit with it now, and the integration with Photos has meant I can now consider ditching Lightroom.
After some trying out of stuff, I have come to this as a current solution.
On my Nikon images (D5100 and now D5300), I’m liking the look that the Provia LUT gives. So, as you have done, I have made a preliminary preset as a starting point, which adds a little Raw sharpening for my budget ‘kit’ lenses. I haven’t worked back to older cameras as yet (I have Olympus, Fuji and Panasonic collected over the last few years). The Astia LUT works well on family wedding pictures.
I then apply Auto Enhance, and then work down and tweak as necessary. I prefer the look that the ‘Levels’ option gives, rather than Curves, which I found can sometimes result in a colour balance I don’t like, the Levels option seems to give more constantly neutral results.
I’m now able to edit images as fast as I did in Lightroom, with equally good, or better, results.
The Sharpen module is very deceiving too, for such a simple adjustment, it works brilliantly well for most images, and seems quite forgiving in how much you can apply.
The only thing I’d like to be able to do in a preset is to turn on the Raw module, without applying fixed settings, but allow it to apply any camera default settings it finds – such as the Luma and Chroma noise settings, which can change dependent on ISO).
Cheers.
It’s not so much the Pencil operation per se’, it’s the operation of a few of the sliders. Particularly Saturation and Vibrancy, the amount of effect applied does not very progressive, so only a very small amount of movement results in too much effect being applied. Actually, now I’ve just gone off and retested, it seems to the the ‘Basics’ panel that suffers with this most, all the rest are really nice and progressive, but the sliders in the ‘Basics’ panel do seem to apply effect quite aggressively. It means that it’s very difficult to get an accurate adjustment point if you only need to add a subtle effect.
All I meant was that this can be eased by using the slowdown technique, but shouldn’t be something I need to use for every adjustment on those sliders. The comment I was making is that the slowdown technique does seem fiddly to use when using a Pencil, as you say, the slide down then across, but I don’t mind that if I didn’t need to use it as much on those sliders. I think that’s maybe part of the nature of the Pencil operation, and me getting more practice using it to some extent.
If I may, sorry, while we’re talking about the Pencil, I also find the centre ‘decent’ position, that has a pause when you go near it, is also quite tricky when using the Pencil, it is too willing to grab the slider spot, and is then fiddly to get moving again (again, eased by using the slowdown technique).
Apart from that, this is an excellent photo app, and I thank you for the great work you’ve done to produce it.
Regards
Andy.
Oh, so stupid of me, I hadn’t spotted I’d replied in the MacOS group, doh. So sorry… this is actually when using iPadOS on an iPad Pro (2020 12.9” model).
I have found the way to slow down the sliders on iPadOS, but it seems fiddly to use with a Pencil, and shouldn’t that be used for fine control, rather than a workaround?
Cheers.
Interesting stuff. I was going to post a related query regarding the sliders, but this seems similar in context perhaps.
Having done quite a few edits now, I have been finding that some sliders seem to be a bit aggressive (perhaps too sensitive might be a better description).
Most are fine, and operate in an expected fashion. But some, particularly saturation and vibrancy, seem to need very fine control to get a sensible amount of effect applied – I’m often ending up at 0.08 or something similar. I wonder if they might need a reverse modifier to switch between slow/fast application of the effect.
I’ve also noticed that they can suffer with lag after editing about 20-30 images. Is this expected? A result of clogging up caches perhaps? If I force quit and relaunch it’s fine again for another 20-30 images. Again this seems to affect some sliders more than others.
Cheers.
