Search the Community

AP 2.1.0 (Affinity store version) and AP 1.10.6 (Apple Mac store version) macOS 12.6.5 Colour managed rendering of a placed Image object requires a transformation of colour component values from the Image's colour space to the document colour space. However, the Affinity apps temporarily behave incorrectly with regard to that. Expected behaviour: The appearance of an Image object should not change when the hosting document's colour profile is changed by assignment (distinct from conversion) when the colours of the Image are within the gamut of the before and after document profiles. The software should immediately compute a transformation of values from the Image colour space to the new colour space of the document in order to preserve the appearance of the Image object. Actual behaviour: The appearance of an Image object does temporarily change when the hosting document's colour profile is changed by assignment (distinct from conversion), even when the colours of the Image are within the gamut of the before and after document profiles. The incorrect appearance persists until the document is saved and closed. When the document is re-opened, the Image gets rendered with the correct appearance. Suspicions (can be ignored by the developers, of course): When an Image is initially placed in a host document, the software immediately computes and caches a transform of the image's values from Image colour space to document colour space, and that cache is the source of values for subsequent computations involving the Image. When a document already containing an Image is opened, the aforementioned cache is rebuilt. When an Image hosting document's profile is changed by assignment, the software should immediately rebuild the aforementioned cache, but fails/neglects to do so. Simply reporting a bug. Not looking for any workarounds. Additionally, to be clear, there is no problem with profile conversions. The problem involves profile assignment.