Export SVG with Rasterize Nothing gives incorrect preview but...

[debraspicher]

I was testing "Rasterize Nothing" just to see how it would handle this file. This file has an Image Layer linking to a PNG tone in it. The rest are curves:

This is how it is setup:


When I go to Export and set "Rasterize Nothing", this is the preview...:

However, this is the output:

So I was wondering... where did the tone go? So I opened up the SVG in Affinity... and the layout is now as such:



So while the Export Preview shows the tone is meant to be included in the final result, it looks it just doesn't handle the mask (which would involve rasterization...?) I'm not real sure what the intended output is. I assume the raster would remain, because "Rasterize nothing" could theoretically allow for what is rasterized already to remain... so by disabling this option, it would mishandle the mask needed to finalize "intended" output since technically that involves rasterization against the mask itself? Not real sure what to say to that, whether it is intentional or not, but at least the preview is wrong.

By the way, If I change it from "Rasterize Nothing" to "Rasterize Unsupported", I do see the tone is properly clipped...

 

Edited to add files:

231214_jenni.afdesign jenni-rasterize-unsupported.svg 231214_jenni-rasterize-nothing.svg

[v_kyr]

28 minutes ago, debraspicher said:

So I was wondering... where did the tone go? So I opened up the SVG in Affinity... and the layout is now as such:

 

Which looks to be a wrong behavior here for a "Rasterize Nothing" SVG export setup, since the export should here then generate a SVG file without any containing raster/bitmap/image data at all.

28 minutes ago, debraspicher said:

This file has an Image Layer linking to a PNG tone in it.

I assume that for the export here in this case, the linking isn't handled and resolved correctly (not taken into account), for a SVG export setup as "Rasterize Nothing". Since if one exports with rasterize nothing, the resulting SVG file usually shouldn't contain SVG XML code wise any raster data.

[debraspicher]

8 hours ago, v_kyr said:

Which looks to be a wrong behavior here for a "Rasterize Nothing" SVG export setup, since the export should here then generate a SVG file without any containing raster/bitmap/image data at all.

I assume that for the export here in this case, the linking isn't handled and resolved correctly (not taken into account), for a SVG export setup as "Rasterize Nothing". Since if one exports with rasterize nothing, the resulting SVG file usually shouldn't contain SVG XML code wise any raster data.

That was what I originally expected it would do... but then after some thinking, I wondered if "Rasterize nothing" only applies when there are elements that *need* rasterizing. (I'm not familiar with what it does in other programs because I almost never use raster elements in an SVG). The only other option was "Rasterize Everything" beyond "Unsupported". So I didn't necessarily conclude that it meant to imply that it won't include Rasterized elements at all. Still, it's Serif, so we don't know what their intent was... I assumed it didn't work because the mask needed to be converted (rerasterized) against the image for it to apply.. but of course that includes rasterization... and in code, well, eliminating that one line of code for rasterize(), etc made sense to me for this edge case.

Out of boredom and because I like having fun... I rasterized the <Image> and moved the mask out of its special place and now we'll see what it does...

Export Preview:

And now I have another dog... and oh look, it's an <Image> again... and the mask is still a Rectangle.


jenni-rasterize-rasterize-nothing_rasterized-image-layer.svg
 

I know I'm going to be asked for files from mods, so I will attach the document for this and the other SVGs to the original post.

[v_kyr]

3 hours ago, debraspicher said:

That was what I originally expected it would do... but then after some thinking, I wondered if "Rasterize nothing" only applies when there are elements that *need* rasterizing. (I'm not familiar with what it does in other programs because I almost never use raster elements in an SVG). ...

Good point, don't know if it is meant that way in Affinity. - But on the other side, the so generated SVG output (of your above generated "jenni-rasterize-rasterize-nothing_rasterized-image-layer" SVG file) then still contains base64 uuencoded PNG image data which is just visual covered by the white rectangle. ...

So any third party SVG capable tool (prog, app) which expects plain SVG vector data will also have to load that pattern image data here contents wise together from the file. Thus I'm not sure that the whole is from the overall behavior to be expected SVG export result here for "Rasterize Nothing".

Further, when I reopen your above mentioned SVG output file in ADe v1 and switch over to export that again as an SVG file, I can see for a short moment ...

... that it first shows up "Some areas will be rasterized" which then changes/switches over to "Nothing will be rasterized", where the more panel afterwards shows ...

... and even when you change the whole to "Nothing" then ...

... the exported SVG file's code will contain the rasterized base64 uuencoded PNG image data, which is something I personally wouldn't expect here when using that "Nothing" export option.

In sum up I'm not sure if it is the right to be expected SVG export behavior here, as it looks more like some wrong exporting behavior here for me (... so probably a sort of recognition and export code generating bug).

[Callum]

Hi All,

I have logged this with our developers to be investigated further.

[debraspicher]

5 hours ago, Callum said:

Hi All,

I have logged this with our developers to be investigated further.

Happy Holidays, Callum.

[NotMyFault]

Bump. Still unfixed in V2.5 and beta V2.6