MikeFromMesa

Yes. I did that before I posted. If I run Photo under Rosetta it will then run some of my plugins, but not others, and those that do run do not run properly. I am not referring to the Nik plugins, which do run properly in Photo.
I had the same issue with another pixel editor (PhotoLine) but it allows the user to run the app version of the plugins and those run properly. I tried to find some way to run the apps under Photo, but can not find anything that works. I have not yet looked into scripting, and thought I would ask if anyone has done that before I spend the time and possibly redo someone else's efforts.

It seems fixed. At least I was not able to reproduce it when I tried. I will do some additional testing and post if I run into this issue again.
And yes, I have Metal set.
 

Yes. I think I see that now. I was looking for something unambiguous, like the words "Photo Persona" written somewhere on the display clearly enough for even me to not miss it, but I think I do see the graphic indication you are referring to.
Thank you.
 

Exactly how does someone determine what the current Persona is? I can find no visible indication of the current Persona state. The only thing I have been able to find is that clicking on the Affinity Photo command usually displays 4 Persona links and that the one that is missing is the one I am in, but that does not always work since sometimes there are no change links displayed.
What is the easiest way to determine what the current Persona is? And yes, I generally remember what I changed to, but that does not help if I got called away from editing and return 30 minutes later, and it does not help when an image is originally opened.
UPDATE:
Never mind. Got it figured out.
 
 

I downloaded and installed Affinity Photo 1.7.0.124 and checked to see if this version fixed the issue with AP crashing when changing from the Photo to the Develop personal. That problem was fixed, but when the user switches Photo -> Develop, then Develop -> Photo, then Photo -> Develop and again Develop -> Photo AP crashes. It does not matter if any changes were made or not. I have tried this now 3 times and have gotten 3 crashes. For me it made no difference if I made changes or not.
 
 
 

I downloaded the latest beta (1.7.0.123), loaded a jpg and clicked on the Develop Mode button. AP crashed, and has crashed every time I have repeated this sequence.

I see from the release description that it is possible for the user to choose between raw processing engines. I am sure that is right, but I can not find where to do that. I have checked the Preference settings and the visible icons on APB but can not find where I can choose or what my choices are. Could someone please clear this up for me?
 
Thank you.
 
UPDATE:
 
Never mind. Found it.

Well, of course. I do not understand why I did not think about that before posting the question.
 
Easy as pie. Thank you for reminding me.
 

I should have thought of the Zoom Tool but, of course, I forgot it was there as I had become used to using the Ctrl+ and Ctrl- keyboard shortcuts.
 
Thank you.

dpReview has reviewed AP and you can find the review here.

Thank you. That would be a big help.

Well then, if it is not happening to you with Beta 4 then it must be something on my system. Still, it does not happen with AP itself, only with the beta.
 
I think I am going to make a screen video of this to show the developers what is happening on my system at least. Perhaps that will help. It is very discouraging as it requires that I reboot my system. It does not happen when I open one jpg that way, but it happens every single time I open the same 14 jpgs using Finder or just try to open the same 14 jpgs with the Open command. Perhaps I will also try to open 14 different jpgs and see if the problem repeats itself.
 
Thanks for the post.

Got it. Found it. It works.
 
Thanks.

My mistake. I re-read your instructions and this time, when I did what you wrote, it worked. I am not sure why I misunderstood your post before, but I have it now.
 
Thanks for following up.

Yes. That is exactly what I wanted to do. I guess I need to sit down and go through the tutorials again because, after all this time using AP, I did not know what the Pen Tool did, or that it was what I needed.
 
Thank you very much for your post. Now I need to go back to some of those earlier photos and redo them.

I have been loading multiple files into AP simultaneously, adjusting them and writing them out individually. It occurred to me that AP has a batch function and I decided to try to set up a batch write for all of the files currently loaded (and adjusted) in AP. When I tried what I found was that the batch dialog box seemed dedicated to processing images that are on disc and not in memory and I could find no way to batch save all of the multiple images I currently had loaded into AP.
 
Is there any way to batch save multiple adjusted images? Or do I have to save them individually? I suppose I could create a macro but then I would still be stuck with applying the macro to each loaded image rather than issuing a simple batch-type command to process them all at once.
 
UPDATE:
 
Just to be clear, this would involve "saving" in the sense that an image would be written out in the requested format. That is, the image would be exported to whatever format is requested, given the acceptable format types for AP. In this case I was trying to export the images as psd files although I might have wanted to export them as jpgs.

The only time I have seen that is when I have accidentally selected the wrong layer. If an adjustment layer is selected the haze filter can not do anything because it has no data to work on. One of the continuing problems I have is that I sometimes forget that I have to select the image layer when I want to apply filters.
 
If your problem is different than that it is something I have not seen.

I found that it was easy to adjust highlights, md tones and shadows separately by creating multiple layers and adding the appropriate mask three of those layers. I have done this successfully manually and decided to record a macro to take care of the tedious work of creating, labeling and setting the masks for each of the 3 layers. However, during the process of recording the macro and when I tried to select the second layer, this happened:
 

 
Here is a closeup of the dialog box:
 

 
This never showed up when I did this work manually but shows up for every layer after the first when I am recoding a macro. In addition sometimes the dialog box does not even allow me to select any layer as no choices are enabled. Why am I seeing this when recording a macro but not when doing this manually? And is there any way for me to proceed and still have the macro work?
 
I have tried responding to the dialog box during the macro recording but when the macro is played back with a new image it does not work as expected. What am I doing wrong?

I used APB to create an HDR from 5 raw images and saved 2 versions of the resulting image, one without HDR adjustments and one with,as psd files to test and see how much extra dynamic range resulted from the merge. However when I tried to load these into some external (to APB) tools they would not load and I received the error message saying that the images had an unsupported bit depth and could not be loaded.
 
These images failed to load into Lightroom, Elements 12 (yes, very old) and On1 RAW. Can anyone please explain to me why these psd files have an unsupported bit depth? I also created tiff equivalents and those loaded properly. Only the psd files were a problem.
 
I can supply links to the files if anyone is interested.
 
UPDATE:
 
I have repeated this process with a second HDR image sequence and with each of the Preserve Accuracy, Preserve Editability and Final Cut settings on the psd dialog box. The same problem showed up with the new HDR sequence and with all three Perserve settings. I would have thought that Preserve Editability would have been more able to be loaded by other editors, but apparently not. 

This morning I added some plugins to the APB default plugin folder and restarted it. When it reopened I checked the list of recognized plugins and saw that the plugins I added did not show up, so they were not recognized as valid plugins. This made me curious as to why - that is, I am not asking why they do not work as I realize that there is still work to do on plugins, but why they were not even recognized as plugins. They are valid PS plugins and I expected them to show up in the list once I added them to the default plugin folder and restarted APB, but they did not.
 
Does APB keep a list of valid plugins and only recognize those? Or are there other criteria?

Congratulations on your success and welcome to the community!
 
I have been a long time panorama taker and used to use panorama-specific software (Panorama Studio 2) for my panos but a couple of tries with AP and I have given up using my old software and now only use Affinity Photo. Panorama Studio was very good, but so is the AP pano functionality. There is also related HDR and stacking functionality in AP as well and those are just as good - you might want to give them a try as well.

I think it is important to remember that Affinity Photo is a product in its own right. It was not designed to be a feature-for-feature replacement of Photoshop (although I use it that way since it has all of the functionality that I ever used in PS, except the plugins, plus some additional functionality) but to do the editing that its designers intended. 
 
As good as it is (and I think it is very good) it is not a super-set of PS functionality. For example, as I mentioned, it still does not handle most PS plugins well at all. Still, it is only a bit over a year old, so I am prepared to give it some time.
 
And one very big plus is this forum. I don't see the Adobe software engineers hanging around and responding to questions on the Adobe forums, but they do here, and they listen. One example is the existence of a Flatten command that will flatten all layers without producing a new stamped layer. That did not originally exist but was added at user requests on this forum.

I think it is important to remember that Affinity Photo is a product in its own right. It was not designed to be a feature-for-feature replacement of Photoshop (although I use it that way since it has all of the functionality that I ever used in PS, except the plugins, plus some additional functionality) but to do the editing that its designers intended. 
 
As good as it is (and I think it is very good) it is not a super-set of PS functionality. For example, as I mentioned, it still does not handle most PS plugins well at all. Still, it is only a bit over a year old, so I am prepared to give it some time.
 
And one very big plus is this forum. I don't see the Adobe software engineers hanging around and responding to questions on the Adobe forums, but they do here, and they listen. One example is the existence of a Flatten command that will flatten all layers without producing a new stamped layer. That did not originally exist but was added at user requests on this forum.

I think it is important to remember that Affinity Photo is a product in its own right. It was not designed to be a feature-for-feature replacement of Photoshop (although I use it that way since it has all of the functionality that I ever used in PS, except the plugins, plus some additional functionality) but to do the editing that its designers intended. 
 
As good as it is (and I think it is very good) it is not a super-set of PS functionality. For example, as I mentioned, it still does not handle most PS plugins well at all. Still, it is only a bit over a year old, so I am prepared to give it some time.
 
And one very big plus is this forum. I don't see the Adobe software engineers hanging around and responding to questions on the Adobe forums, but they do here, and they listen. One example is the existence of a Flatten command that will flatten all layers without producing a new stamped layer. That did not originally exist but was added at user requests on this forum.

You don't have to delete "layer by layer". You can select all you want to delete and then just delete them with one delete.
 
But there is no other way (yet) to flatten the layers. That issue has been raised with the developers (many times) and they have promised to implement something. Hopefully soon.