Affinity colour profiles and SVG

[Display]

Hello,
Question about colour profiles - have I setup Affinity wrong or is it behaving as expected?

Affinity Colour Settings:
RGB Colour Profile: Adobe RGB (1998)
✔ Convert opened files to working space
SVG file in question: https://upload.wikimedia.org/wikipedia/commons/6/6e/Home_Assistant_Logo.svg

What I expect to happen: Opening an SVG from the internet (sRGB IEC61966-2.1) it should appear as it does online.
What actually happens: It opens unsaturated


Left: AdobeRGB converted Import          |               Right: sRGB SVG in a browser

If I want the SVG to look exactly like the browser view AND keep working in AdobeRGB, I need to:
• Change Affinity RGB Colour Profile  from Adobe RGB (1998) to sRGB IEC61966-2.1
• Open the SVG 
• Copy SVG
• Set Affinity RGB Colour Profile back to Adobe RGB (1998)
• Paste SVG

That can't be the correct workflow for AdobeRGB, surely?
Edit: Did some tests just now and it doesn't seem to be happening for PNG/JPG/PSD...

tl;dr
What is the correct setup for opening sRGB SVG files and have it look correct in Affinity while using AdobeRGB profile?

Thanks for any advice!

[v_kyr]

SVG is a vector format for the web. According to its specification, usually all SVG colors are in the sRGB color space. - Though SVG content can specify an alternate color specification using an ICC profile [ICC42] as described in Specifying paint. If ICC-based colors are provided and the SVG user agent supports ICC color, then the ICC-based color takes precedence over the sRGB color specification; otherwise, the RGB fallback colors must be used. Note that, in this specification, color interpolation occurs in an RGB color space even if an ICC-based color specification is provided (see ‘color-interpolation’).

So overall the easiest and usual way to deal with a color space in SVG is to use the default sRGB color space for it instead of AdobeRGB. - Further the AdobeRGB color gamut is much wider and contains colors the sRGB color gamut can't showup ...

... and beside that the common lowest denominator (standard) for different screen devices and the Web is sRGB.

[Display]

I normally work in AdobeRGB - the larger gamut makes it much easier to paint with or design colourways!
When done, I export it out and crush the profile to sRGB so it looks the same as when I was working with it.

So if I'm working on a painting/texture in AdobeRGB and I want to bring in some SVG logos/decal designs, I can't have them be colour accurate unless I switch back/forth to sRGB?

This doesn't appear to be a problem with (sRGB) PNG/JPGs being imported into AdobeRGB working space.

I'm trying to understand why it doesn't work as expected - since AdobeRGB can contain everything that sRGB can offer, whenever I bring in any filetype that's sRGB (and I've set Affinity to Convert to Working Space), surely it should display it correctly in the AdobeRGB space?
Why would it be pale/desaturated for SVGs? Is it perhaps a bug?

[walt.farrell]

9 minutes ago, Display said:

When done, I export it out and crush the profile to sRGB so it looks the same as when I was working with it.

Sorry, but I don't understand that. 

If you work in a larger color space, then "crush" to a smaller space, isn't it almost guaranteed to not look the same as when you worked on it?

[Display]

22 minutes ago, walt.farrell said:

If you work in a larger color space, then "crush" to a smaller space, isn't it almost guaranteed to not look the same as when you worked on it?

It would be the equivalent of working in AdobeRGB, then exporting it as to CMYK/Web with Perceptual/Relative Colourimetric - it gets it to looking as close as possible to the working space. Working in AdobeRGB just gives me more flexibility.
If I didn't crush it to a smaller profile on export, it would look washed out on sRGB devices/applications

 

[Display]

Okay been testing different combinations and I think I've got it working how I'd expect it to... but I'm a little more confused than before !

Set Affinity preferences RGB Colour Profile to: sRGB IEC61966-2.1

Make sure new documents are set to AdobeRGB:

Now when I open an SVG, it looks correct (since its sRGB/non-managed)
AND Affinity continues to respect AdobeRGB ICC embedded documents too!

I would have thought if I wanted to work in AdobeRGB, setting it in the preferences would enable that??
Maybe Affinity is using those profiles for internal colour conversions or... something?
I don't know, just happy its working reliably now 🙃
 

[v_kyr]

BTW, your above initial referenced SVG contains just an embedded base64 bitmap image, so is far away from being plain SVG vectors here, in case the latter was your overall intention to use that as an SVG format file here.

[Display]

!! You're right, it appears to be a mixture of raster and vectors 
I thought the drop shadow might be raster with everything else as curves, but it it looks like it's a random combination.
Looking at the vector colours, they are accurate - it's the raster areas that are being weird.

I think what threw me was intitally opening it in Illustrator and it looked fine, then opened it in Designer and it looked completely washed out.
Kinda strange that Affinity would treat the SVG raster data differently from JPG/PNG? Still feels like a bug to me.
Guess it's just something I need to be aware of when opening SVG with raster elements 😅

[v_kyr]

When you generate such SVG things with Affinity software, mostly all FX effect things (except one or two) will yield commonly to a rasterization/bitmap generation of those. Affinity's SVG parser & generator have their limitations and do only support a bare minimum subset of the SVG spec here.