Portrait AI issues (v2021)
Sometimes, when I use Portrait AI, the adjustments are not saved, even when I click done. Not sure if this has been raised before or whether it should be reported to support.
It happened twice with this image, in which I had to select the face I wanted to work on myself. Note the red line under the thumbnail. No idea what that means!
-
Got it, thanks. I'll let you know what happens.
0 -
Cool. Good deal. You're always a good resource Brian. Crack the whip on the devs man. LOL!
Let's get this program fully into it's rightful state of excellence. :-)
0 -
Which version are you running? I'm on 15.1.0.10148. On my Mac Mini M1 it works properly. I went straight to Portrait AI by pressing the I key from the Browser and it found the face. I reproduced your settings and only the eyes were affected exactly as expected. I'm not seeing the brightening on the cheeks your example is showing.Did you have to create the mask yourself or did you use the one the program generated?
0 -
I removed the face the program found and added one manually. It also worked properly.
0 -
I'm on 15.1.0.10148 as well. So when editing that photo, the program initially found the face. i mad all my desired settings. Then proceeded to go into Local Adjustments final enhancement on for the eyes to 'pop' the green a bit. Once I set it to my liking with the Local brush and pressed done to prepare for export I noticed that the editing done in Portrait AI was no longer represented (particularly anything related to the eyes).
So I went back into Portrait AI and noticed that the settings were still present but the desired results of those settings was not. I tried undoing and re-doing the settings, moving the eye ball markers, etc. None of those measures fixed the problem. So I deleted the face and manually set the face box to find the face. The detection that you are seeing in the example I posted in the thread is the result of being forced to set the face manually because after deleting the initially detected face, exiting Portrait AI and re-entering it a few times the program would no longer auto-detect it.
0 -
Your screen shot shows 2 Layers but you don't mention creating a 2nd Layer. Is it possible you made the Portrait AI change on the lower layer and the Adjustment Layer got added to the top layer?
0 -
I've tried replicating what you did and I'm still not having any problems. I did all the work on a single Layer and I was able to move back and forth between the Local Adjustment I added to try and bring up the eye's corneas, and the Portrait AI with its overall face edits.
0 -
No. I always initially make a copy of the original RAW file for editing purposes just as an extreme 'safe keeping' measure to keep the original RAW file unaltered.
0 -
That is completely unnecessary with Photo RAW. The RAW file is never touched, you can't even embed metadata changes to it. All your edits in ON1 are stored in its internal edits database and in the .on1 sidecar file. You can see this by making some edits to a RAW file, without adding a layer to create the matching .onphoto file, then going into the Finder and deleting the .on1 sidecar. When you return to Photo RAW you'll see the unedited original file. You can also check the file modified date in the Finder. The file's Modified data will always match the Created date.
0 -
I'm not surprised at your results at your successful results at all Brian as I don't experience issues with every file with Portrait AI. Everything will be working seemingly perfect, until all of a sudden it isn't and when I have the time to investigate the error I find problems like you see in the example I posted. It's very random, weird and extremely frustrating of course. But obviously it's a clear indication of a bug of some sort in the program it self to even produce a result like this since it's not even something I could create. And again my system is definitely not the problem. It's brand new, exceeds basic specs, no changes or updates have occurred nor are pending and all settings and drivers are in tip-top form. Also the previous 2 similar Portrait AI issues I had were experienced on a different machine (ASUS laptop) and the files were from a different camera using both Photo RAW 2020 and now Photo RAW 2021.. There's some type of glitch in Portrait AI.
0 -
Cool. Good to know. Pretty sure I've read that before, but probably preferred to retain my security blanket of sorts, since for my paid work I typically only edit the photos the client has chosen for delivery so I can't afford accidentals like corrupted files.
So in that same context, these files that experience these bugs while editing, I basically have to spend extra time in doing a complete reset & re-edit since they are the client's selection. Not productive and occasionally angering. Sux.
0 -
I return to the Browser frequently while editing. Basically anytime I've finished working on one piece and am ready to move to a new section. This way, if anything goes south for any reason, I can just Cancel the current editing session and jump right back in with the previous edits intact.
0 -
BTW, my bad fellas. I saw the topic heading, subject matter and having like experience contributed to the discussion and hopeful resolution without noticing that this occurrence is MAC in origin and I'm on PC. :-) Anyway hopefully all details are beneficial toward fixing these kinds of problems.
0 -
Hey Brian. One final very interesting weird observation. I just got in today and decided to power up & investigate the issue again. I began by doing a 'Delete Settings'. Loaded up PR 2021, browsed to the photo and it seems to be appearing accurately as I intended with the initial edit, pre-error. So I double clicked to enter 'Edit' and into Portrait AI mode. Photo actually does indeed appear as desired. Clicked the little blue button to bypass the Portrait AI settings for validation of the changes then clicked again to re-activate the settings and bam, the error was re-triggered. Shut down PR 2021, performed another Settings Delete, re-launched the program and long story shorter performed the exact same steps and the exact same end behavior occurred. Super weird bug. Crazy stuff.
0 -
That's the kind of stuff support needs to know about Sean. When you can reproduce a problem on demand giving the steps to them gives the engineers a better idea of where to look for the cause of the problem.
0 -
Guess I'll take one more shot at getting some action on this. Think I'll prepare to jump straight to the end this time and go ahead and make a screen recording in an attempt to bypass the days of preliminary "are you sure?" measures. We shall see. Have a good evening.
0 -
Give them the link to this thread too.
0 -
Yep. Will do.
0
Please sign in to leave a comment.
Comments
48 comments