Affinity Suite shows weird CMYK Colors vs Adobe on my Wide Gamut Display

[Duskstalker]

Hello,

im having issues with the cmyk color reproduction in affinity suite while adobe software (photoshop, illustrator, acrobat) shows quite accurate cmyk colors. of course its not the "real thing" as cmyk is cmyk, but you can quite easily pinpoint 100% cyan as such in adobe, and not even close in affinity. output colors (values) via pdf export are correct, but are apparently truncated down to srgb(?) for display output on my wide color gamut monitor (100% argb color space) which greatly shifts blue and green colors from the "real" cmyk colors that should and can be somewhat displayed in wide gamut, and adobe software does just that. in an affinity cmyk document 100% cyan looks like desaturated sky / baby blue, but if i create an argb instead of a cmyk document in affinity cyan begins popping, just like in acrobat, illustrator and photoshop, but these do it even within a cmyk document.

at this point i dont know what exactly is going on and im trying to make sense of it. are there some hidden settings for affinity to control display color space? did something break? did i screw up the monitor setup?
i have cross checked srgb vs srgb content with an old calibrated 8bit srgb monitor vs my wide gamut one and photos and web in itself looks very close in a color managed environment. i just never stumbled over this drastic difference in color rendition between affinity and adobe.

thats my setup:

win 10 1903
acer predator xb323U (10 bit, 100% argb) calibrated and profiled for srgb gamma response via displaycal + spyder5, but the monitor is not a professional display with hardware calibration support.
Adobe CS6
newest affinity suite

the files below are jpgs in argb, but maybe the upload to the board broke them - im also new to the wide gamut thing. anyway, the differences should be clearly visible in srgb, too!

the screenshots show how different apps display 100% cyan.
top left is affinity designer in an ECI 300% CMYK document and it looks awful - the color is just miles off.
bottom left is affinity designer in an argb document with 100% cyan and it looks ok.
top right is adobe illustrator in ECI 300% CMYK with 100% cyan and it looks good.
bottom right is adobe acrobat showing actual print files in ECI 300% CMYK with 100% cyan (file created in affinity) and color proofing shows something close to illustrator - in wide gamut its very close visually.

the 2nd screenshot shows the exact same, except for adobe acrobat having simulation profile switched from ECI 300% to srgb, and its the exact same color affinity designer shows.

in an srgb document with srgb color values illustrator and designer show the same colors.

i also included the first screenshot as pdf in argb in case the board dismissed the color profile or whatever. if you set the simulation profile to a wide gamut rgb (photo rgb, argb, you name it) on a wide gamut display you should see what i see.

is there a way to make affinity display what adobe displays? or has someone an idea what went wrong on my end, if that is not to be expected behavior?

thanks, looking forward to your input!

affinity cmyk1.pdf

[lacerto]

(...)

[Duskstalker]

this seems to check out, thanks for your insight. so it is indeed affinity related and not some weird software, OS or calibration issue on my side - which narrows down the way to a possible solution or work around or developer attention.

any ideas on how you cope with that? i dont know why this never stroke me working on an srgb monitor, but now the issue kinda sticks out like a sore thumb. i have alot of print stuff to do with exact color values in cmyk, so doing my work in argb and then exporting to cmyk is not exactly appealing.

its kinda unsettling to finally have a monitor capable of displaying close to real cmyk colors and then getting stuck in dreadful srgb translation in affinity - the affinity workflow kinda grew onto me vs the adobe suite.

i looked up setting files and registry entries, but the setting files really just contain what the in app preferences contain - so no easy switch to flick.

[lacerto]

(...)