Just_user

I think so - if the RAW processor is further improved, then Affinity Photo will only win. Personally - I don't see the need to copy all Adobe tools - who needs Adobe - go for it. As for Affinity Photo, you can simply develop its achievements. After all, any product is valuable for its originality, and not for copying other people's instruments... The main thing I'm afraid of is that Affinity Photo will not turn into a niche product in which you can only process photo models, "mutilating" the human appearance beyond recognition...😂 Well, this is philosophizing 🙂

I'm also impressed by the panorama capabilities in Affinity Photo, and especially by the often smart behavior of the "Impaint Missing Area" tool. But, let me disagree that I want too much ... From my point of view, Lightroom is far from ideal and is not the most advanced program for processing RAW files. And if AI is used in Affinity Photo to create panoramas and good panoramas, then why can't this AI be improved? Moreover, in the same LR this task (to bring "extreme light levels" to an acceptable level in RAW images when merging panoramas) was solved almost 10 years ago... Yes, the processing of "extreme light levels" is not a frequent task, but I dare to hope that it is not so rare either. You can look at other similar programs (which process RAW images) - after all, AI has begun to be introduced almost everywhere. Yes, It is not perfect, it often makes mistakes - but "the road will be mastered by the one who walks", And if Affinity Photo started using AI even earlier, then honor and praise be to them. And I want to believe that efforts in this direction will continue, and the possibilities will improve...

Thanks for the replies and advice.. Of course, I understand that Affinity Photo and Lightroom are different programs and their purpose is different. I just want to hope that developers will read this topic and be able to improve the processing of RAW files when creating panoramas in Affinity Photo. Or, if this is not included in their plans - place an explanation in online -help that gluing panoramas gives good results only FOR PROCESSED and PREPARED jpeg or tiff files. I'm not creating a new topic so as not to clog this thread of the forum.

Thanks for an answer ! 🙂 I agree that using NOT RAW files, but let's say "developed" RAW in tiff - will significantly improve the quality. But, unfortunately, this lengthens the processing process and, ultimately increases the time to create a panorama. For comparison, I tried to make a panorama from JPEG files taken on a Xiaomi MiLite smartphone with a resolution of 4000x3000 (6.4 MP) in HDR mode - in this case, the panorama looks much better and there are no such dips in bright lights ... Answering your questions: - I always shoot panoramas with a fixed AEL (i.e. fixed exposure), - I didn’t try to shoot with manual exposure - I’m afraid that if there are areas with different illumination (sky and objects) - the finished panorama will be even more non-uniform in illumination, - I tried to shoot in HDR mode on the camera, but there the output is an already processed JPEG in which part of the information is often already lost. - I don't know, to be honest, what do you mean by the words -- "hdr (RGB/32)" It just frustrates me that LR processes RAW files quickly and well and creates a good panorama, but Affinity Photo CANNOT do it as quickly and efficiently - but requires additional processing ...

I often make panoramas from a series of shots. Sometimes the pictures are taken in backlight. And when creating a panorama from such pictures, I encountered the fact that Affinity Photo unsuccessfully processes areas with bright areas and their neighbors. That is, Affinity Photo actually "fills" very bright areas with white and fades to darker areas makes it not smooth, but outlined with a Cyan color fill (as seen in the example below). For example, I tried to make a panorama from such pictures in Adobe Lightroom 6.14 (last standalone version) LR handles such areas much more naturally and "gentle". For example, I apply a panorama created in Affinity Photo, Lightroom and a photo of the central fragment, where the sun is in the frame. All shooting was done on a Sony RX10 M4 camera in RAW format. And in Affinity Photo I upload exactly the pictures in this format (raw). These may not be the best shots from a technical point of view, but they are frustrating and alarming, how Affinity Photo handles bright areas. And, I must say that, in general, in Affinity Photo, the panorama turns out to be more dark than the original shots - this can be seen from the histograms. I would like to believe that such an unsuccessful processing algorithm can be corrected in the future. Especially when dealing with bright areas... N.B. Affinity Photo's version is 1.10.4.1198 This is panorama created in Affinity Photo. This is panorama created in Adobe Lightroom 6.14. This is photo of the central fragment (RAW).

I also join the question. I have a Sony RX10 IV camera (with embed lens correction profile) but Affinity photo only shows the "Sony RX10III & compatible profile" for it. Although the camera itself began to be produced back in 2017. Question for programmers - please add profiles ...

Thanks for an answers....... I do agree - it is so . And I agree that experienced Affinity users are aware of this. But the point is that a beginner can lose many important files during such an operation - until he gets used to not press the SAVE button. And such newcomers and such losses will be enough ... That’s why I am asking to prevent losses and not to “spoil the impression” of a good program. 🙂

I'm a novice in using Affinity Photo. Earlier I've been using Photoshop, Photoshop Elements and Lightroom. An now I 'm trying to migrate to Affinity... But 1 thing got me into trouble. When I wanted to save just an open jpg file, I chose the "SAVE" option. And after that, my source file was immediately overwritten - WITHOUT any warning. Please - add an option that would prompt you to overwrite the existing file before saving. Let it be possible to enable or disable it - it does not matter. The main thing is that the user is warned in advance ... Thank. Yours faithfully, Anatoly P.S. excuse me for my english...