[thewildrover]

To be more accurate, it’s actually the adjustment sliders that are slowing down, they start to experience lag, which gradually gets worse with each image (once the effect starts), until it becomes almost unusable, until the point the lag starts, the adjusters operate perfectly well. Simply closing the app doesn’t do anything, but a Force Quit resets it, and I can continue editing a similar amount of images before it starts again.

[thewildrover]

Hi Nik,

Thank you so much for the update. The Levels issues do seem to be, both the weird black setting, and the crash if attempting to adjust using Auto Enhance.

I have just tried a batch Auto Enhance, and initially did 57 images without a problem, and then 53 images, which crashed RP. I did a Force Quit and tried again, and it was fine that time.

FWIW, I have also noticed that RP does slow down a lot after editing 20 or so images, when I find that Force Quitting and relaunching sets it back to normal speed for a while. This is quite a regular pattern. However, it’s not a deal breaker, and RP is superb at what it does in general.

I’m just posting here in case any others might have the same issue.

(2020 iPad Pro 12.9″ 512GB)

Cheers

Andy

[thewildrover]

Thanks, yes, all working fine now.

[thewildrover]

Thanks Nik, that’s excellent news. I don’t mind waiting for the release though.

Best regards

Andy.

[thewildrover]

I forgot to add the original Raw, which I’ve now done.

Cheers

Andy

[thewildrover]

Hi Nik,

Thank you for spotting this, apologies for not using the correct support channel.

I’ve uploaded a set of images showing the processes I’ve used in an image that gets the wacky settings in levels, also showing some screenshots of the original, and other editing methods. On the auto enhanced image using levels, if I try to adjust the levels manually, Raw Power just crashes. All other methods work fine.

Cheers,

Andy.

[thewildrover]

Hi Nik,

Just another update, with regard to specifically the crash when using Levels in Auto Enhance, it does seem to be just the Levels module that’s causing this. I’ve done some trials using Curves instead, and I get no silly all dark settings appearing in the curves module, and I get no crashes if I try to amend the settings in the curves module.

I don’t get any crashes if I edit manually and use the Levels module.

Cheers

Andy.

[thewildrover]

Thanks Nik, I have the same problem here on my iPad too. Glad to see you’re sorting it.

Cheers

Andy

[thewildrover]

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.

• This reply was modified 3 years, 8 months ago by thewildrover.

[thewildrover]

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.

[thewildrover]

Thank you for clarifying that Nik, that’s very helpful.

[thewildrover]

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

[thewildrover]

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

[thewildrover]

Halide is working on my iPad Pro here! Or is it just a Raw Power+Halide on the iPad restriction?

[thewildrover]

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
Andy

[Author]

Posts