May 29, 2020 at 2:39 pm #70318CatasParticipant
Working on raw image, starting with “magic wand” as suggested, “Raw Processing” is not enabled on every image.
What this means?
Why “Raw Processing” is not enabled by default on any raw image when we are starting editing it?May 29, 2020 at 5:19 pm #70338
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).May 30, 2020 at 1:39 am #70381CatasParticipant
I was talking about untouched raw images. Most of the time Magic Wand are not enabling Raw Processing. Is this means that on that image Raw Power is starting working on embedded jpg?
Which is not what we’ll try to work on?
What’s happening when we’ll open an untouched raw image without enabling Raw Processing?
This is the specific case I’m trying to talk.
That’s why I think Raw Processing should be enabled by default when opening Adjust on untouched raw image, or can be invisible like Depth on untouched jpg image.
I’m very happy with the power of RawPower, but sometimes it is an little bit confusing for me.
Thank you NikJuly 6, 2020 at 10:36 am #75873
RAW Processing should always appear on any RAW image. If it doesn’t, then it’s a bug. Can you email me at firstname.lastname@example.org so we can work through this problem?August 1, 2020 at 8:49 am #87493
Hi, a kind of newbie to Raw Power here, I was also about to ask about this in a fresh article, but saw this one first.
I’m using a new iPad Pro, and working on migrating over from Lightroom to Photos + Raw Power, very impressed so far, but I have also noticed that it’s a bit random whether the Raw editing module is activated or not. It’s probably 50% of images not getting it applied using Auto Enhance (whether applied as a batch process, or individually).
iPadOS 13.6, iPad 12.9” 2020
Also happens the same on the MacOS version too (macOS 10.15.6, Raw Power v3.0.4).
Just thought I’d submit as a ‘me too’ effort.
AndyAugust 1, 2020 at 10:09 am #87542
Hi and welcome!
If you are asking why the RAW Processing adjustment is not affected by Auto Enhance, that is normal behavior. Auto Enhance examines the image for many characteristics, one of which is over exposure. When it detects that the image is overexposed (has many pixels that are greater than 1.0), then it uses features of the RAW Processing adjustment to correct the overexposure. However, for well exposed (or underexposed) images, it tends not to do anything with the RAW Processing adjustment. That said, it could be smarter about underexposure, and could move the black point slider – I’ll make a note of that.
–NikAugust 1, 2020 at 11:37 am #87620
Thanks for the reply Nik, sorry I think I misunderstood the original issue here.
Thank you for clarifying that though, I wasn’t sure if it should be enabled for all rows or not, but that makes sense. Adding a bit of black point adjustment would be certainly useful.
Generally though, I do find the Auto Enhance works pretty well, only a few extra tweaks needed most of the time. As you say though, it does seem to be underexposed images that need the most extra adjustments.
Andy.January 23, 2021 at 1:19 am #123956
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.
AndyJanuary 23, 2021 at 11:00 am #123959
Yes, this can be a bit confusing. RAW Processing is always “on,” using the default values.
The default values are not the same for every image. They come from Apple’s analysis of the camera and the image. Apple will adjust the black point, noise, and other settings as part of their attempt to make the image look good. If you want to change what they have done, you would move the sliders in RAW Processing. If you want to see the default decode, then you can uncheck the box.January 23, 2021 at 12:19 pm #123961
Thank you for clarifying that Nik, that’s very helpful.January 28, 2021 at 12:56 pm #123992
- You must be logged in to reply to this topic.