knipser

I noticed the same behavior in 2021 with version 1.10.4.1198. Like you I had set my color profiles to "ROMM RGB" for both RGB and "32bit RGB". A noticeable color cast was introduced in the exact same step as you described. I switched the "RGB Color Profile" back to "sRBG" and the issue is gone. Color profiles can always be good for surprises... This old discussion was a great help for locating the solution in the settings. 👍

For some strange reason it now creates ROMM files, but before it didn't... I will observe if this is a stable state now. The questions would be unnecessary in that case.

I'm creating a panorama in Affinity Photo (version 1.8.3 at the moment) from DNG files. These files are the native format of my Pentax K-3 II camera. The program will always create a panorama photo in RGBA/16 with the sRGB color profile. Therefore highlights and shadows are easily clipped and I'm wondering if I can make Affinity Photo to create a panorama photo with a wider color space. I have set the ROMM color profile for both RGB and RGB/32 photos in the settings (I'm on Windows 10 btw). It doesn't seem to have an impact on the panorama creation process, because I end up with an sRGB photo all the time. I know I could process my RAW photos before stitching, then export them as TIFF files with a color space of my choice. Then Affinity Photo would end up creating a panorama picture with the same color space. But I often want to see first, how well the stitching will work, before investing too much time into editing the photo. I would also prefer to stitch the DNGs in Affinity Photo, export the result as TIFF and import it into Lightroom for further management and editing (unless there are edits I need Affinity Photo for). Does anybody know, why Affinity Photo ignores the wider color space of DNG files when creating a panorama? Is this a defect?