Olivier.A

The "develop" term comes from the analog film world. When you needed to "develop" you film using chemicals and masks. Depending of what chemicals, quantity and time, you would get different developed images. With digital, you have basically the same, but everything is done either in camera or on computer/phone/tablet. Let's say you set your camera to produce RAW+JPEG, you get 2 files on your card. As you mentioned, RAW is just data from the sensor. It can't be even displayed because they are just voltage of the sensor. JPEG is an RGB version of the image, and is coming from the RAW data too. What separate RAW from JPEG on the card, is that the camera processed all the numbers and converted then into RGB format, and added some process that nobody knows but the manufacturer. The image is not only converted but also processed. Then, it is saved in a quality loss format : jpeg. You can be really be happy with the result, as the camera manufacturer has a process that xou like. This is specifically the case for Fujifilm user who really like the different looks available. But each manufacturer has its own receipe. Sony jpegs are more cold / neutral, Canon jpegs more warm. Now, you may be not happy with what the camera do to the RAW file. Don't like the look for example, or you want to get your hand dirty and use the RAW to developp yourself, using all the tools available in Affinity Photo. Yes you are right, developing a RAW add complexcity, but gives you the opportunity to add you tweak during the process. In comparison, you could say, why do I need a raw meast, when I can eat a cooked piece of beef... you can choose the restaurant or chef you like to cook it for you. you might be pleased with the result, and you don't care about how it's been cooked, boiled, grilled etc... and that's toally fine. Now, you might want to have your raw meat and cook it yourself, the way you want. Yes, it add complexity because you have to find out how to cook this raw meat... If you let the camera manufacturer do the developement for you, along the process, some data have to be left out, and you can't decide which one. It's part of their process. If you decide to start with the raw, it's up to you to find out how to keep the details and make them hide or shine. You decide. Back of the piece of meat, either the chef or you decide what flavour you want to enhance when cooking. It's all in the process. You might want to trust your chef, or you can master the skill of enhancing the flavour you like.

From your screenshot, Affinity Photo has loaded the file IMG_4200.jpeg If it's a iPhone Pro Max RAW file you would have the file named IMG_4200.DNG You should check Camera settings on the phone if Apple ProRAW is switched on. When not : the camera produces jpeg. Affinity doesn't convert file format on the disk. Only when you use the export menu, and you select which format you like to save.

When creating a new stack image, the target document uses sRGB colour profile. Bit depth is correctly managed by the assistant. There should be an option to set the colour profile of the target document (like it is possible when going from Develop Persona to Photo Persona). My use case is I'm loading multiple RAW file (DNG) to the stack panel. I like to keep as much information as possible, but the resulting document always default to sRGB. The current workaround is to first convert all RAW file to DNG setting colour profile to my prefered profile (ROMM RGB), then stack TIFFs. that is an extra step ini the process. Regards,

You are may be right, stacking may be not support RAW files. And AP 2 is only using embeded jpegs instead. I think I found out ! It's in the prefs pane under the Colour tab: When "Convert open files to workspace" is UNchecked (which was at the beginning), Stacked photos are using sRGB color profile. (but why sRGB, when it's raw ?) When "Convert open files to workspace" is CHECKED, stacked photos are using ROMM RGB profile, that is set under the RVB colour profile above. This also means that any photos (RAWs as well as jpegs, tiffs, etc...) will now open with ROMM RGB profile. Which is fine with me

Hi, I use to develop photos using ROMM RGB colour space (and 16 bit depth). I've setup the develop assitant and prefs that way. I'm trying to get the same colourspace when using Stack photos. But once the stack is made I always get an sRGB / 16bits document. I guess 16 bits is coming from the develop assistant, but I can't find how to change the default target profile from sRGB to ROMM RGB. Any clue ? Thank you for your help

Hi, I thought about that too. Affinity may not be the reason, but I prefer to mention it just in case. MacOS might be the reason. The following question is what differs in the 2 files so that: - MacOS calls the right Affinity thumbnail function for the original DNG on both Ventura and Monterey, - MacOS doesn't call the right or same thumbnail function for the tagged one on Ventura, but finds it on Monterey. I'll do further test with or woithout Affinity and other applicatons. Thank you.

Hi @stokerg, Thank for the reply. I uploaded 2 files : original.dng and tagged.dng so you can compare. Let me know if you need more information. Regards

Hi, I've noticed that Affinity Photo 2.0 and now 2.1 (and I checked v2.1.1) is not able to create the preview icon and the quick preview on Mac M1, once a DNG raw file has been tagged (whatever the metadata change) by Adobe Bridge. This doesn't happens on Mac Intel. This is not a direct bug of Photo interface, but how Photo decode the embedded JPEG on M1 macs. I'm sure Bridge has it's part of responsability too. How to proceed: Take a RAW file in DNG format. Open Adobe Bridge (any version works) Add a star or add keyword in the file. Close Adobe Bridge Open a Finder on an M1 machine, you should get this preview "imacbookpro m1.f.jpg". If you quick preview (spacebar), you get Affinity Photo icon) Open the same image on a Intel machine, you should get this preview "imac intel.f.jpg" I can provide the DNG images. But each are 15MB, let me know how I can best share. Regards, iMac 2015, Monterey 12.6.6, Affinity Photo 2.1.0, Adobe Bridge 13.0 Macbook Pro 2020, Ventura 13.4, Affinity Photo 2.1.0, Adobe Bridge 13.0 Photo is the default application to open RAW files, Designer and Publisher are not installed.

Hi, I have used Photo v1 and v2, there is a mistranslation for the panel scope. The french word has not the meaning intended. I guess the translator didn't had the context of that word. The first use of scope means space, range.. And this is how the french translation "Étendues" is used. However the second meaning of scope defines the view display of a device. I suppose the meaning is the second one. Could the scope panel be renamed for example "Range" ? A better named for that panel has not direc translation of scope in this case and one should be consider an interpetation: "Vues" (plural), meaning Views / Viewers / Displays Hope this helps. Regards

I'm using Flick for ages and forgot they have a huge program of Creative commons library. The foundation : https://www.flickr.org/ The Library: https://www.flickr.com/commons These are mainly old public images, shared from library of institutions.

Getty bought last summer or so, Unsplash. They are since monetizing Unsplash API, as it is use in a lot of design software. Reason why it also disappered from Affinity Photo.

You can also have a try on Wikimedia commons (the asset site for all wikipedias) : https://commons.wikimedia.org/

The original question is : The question might be simple, but are layer order applied bottom to top in a group ? And we might have derived a bit. But from the previous posts, it seems the answer is yes when there is a pixel layer inside that group. To know how I should place layer so that I get expect results. Sometimes layer order can give different outcomes, and depending if they are applied top to bottom or the way around can change the image.

Just did the test, and it works as said ! Wow. The bottom group has it's own pixel layer (a crop of the bottom background layer). The pixel layer at the top is the same cropped pixel layer, with duplicated adjustment. Each cropped pixel payer are identical. The very bottom pixel layer is not affected at all.

It seems I can find a "rule", thanks to your test. Filter and adjustment layers are affecting the first pixel layer the find from the filter down. This determines which pixel layer has to be affected. Following your grouping, let's take your adjustment group. Which pixel layer has to be affected, take any of the live/adjustment layer, and go down until you find one pixel layer. In your case this is the background layer inside the live filter group. If there were no pixel layer, then go further down, and you'll find the background layer at the very bottom. Also, it seems that a group containing a pixel layer and adjustments are considered are a pixel layer by itself (that has adjustment, but basically a pixel layer. I'm pretty sure that not having a pixel layer in the live filter group, filter would affect background layer, and adjustment layer too. Or if you like, a group containing a pixel layer + adjustment and filter, is equivalent to a pixel layer containing the same adjustment layer and filter. Basically what @Pšenda said ( but differently) Wha do you think ?