BofG

There's always the possibility that it's just black shapes drawn over the images and there's no actual clipping/masking being used.

For web use, you have to beware that some browsers don't do proper colour management. For the most consistent results you need the rgb data to be usable "as is" without relying on an icc profile. Non colour managed browsers assume sRGB, so you will need to convert your document to that colour space prior to export. It wouldn't hurt to also embed the sRGB profile at export. When converting the document it's best to work from a copy as it's a destructive process.

Agreed! There's a lot of inconsistency in the various colour panels that are scattered throughout the app.

Yes, I did waste ages looking for the "toggle button" mentioned in the help files. This has to be the most 'unique' toggle button ever to grace a UI

Affinity is just not very good at this. If you take the stroke off the rectangle, Affinity will generate a pure SVG using "fill-opacity". With the stroke in place it for some reason forgets how to do that and falls back to rasterising the object.

Well spotted. The W3 set out an algorithm for use of the rx/ry values: https://www.w3.org/TR/SVG11/shapes.html#RectElement but Affinity does it "it's own way".

Affinity is ignoring the "ry" property that sets the radius of the rectangle's corner(s). SVG is a very well documented. It is quite complex though, and a lot of programs create less than ideal output.

Yes. There's no cross licensing.

Well I don't have Photo so it wasn't a bad guess

The RAW preview will be 16bit, maybe you are developing to an 8bit image?

What kind of detail are you referring to? Is it loss in the shadows/highlights? Is it sharpness? Overall contrast?

Align centre with just one object selected makes it centre to the document. I've not tried it with a placed file but I would think it would be the same.

Have a Google for "svgomg", there's a tool online that will clean up your svg code pretty good.

If the black is 100% k in the source document, you just need to export to pdf keeping the same colour profile. Easiest way is to use the x1a preset and set the profile to "as document".

That is "directly print from Affinity", as you are using a RIP you don't have to worry - export to pdf/eps is fine. Grab the trial version and see how it goes.

Nope it's not that, you get all the pixels you ask for

I found that "feature" without realising I wonder what the idea behind those limits is? Clearly the program functions regardless, maybe memory concerns? Export to PDF has me confused, as according to the PDF spec, with < v1.6 files the user space is fixed at 1/72 inch and the size limit is 14,400 'units' x 14,400 'units'. That works out to 200 inch x 200 inch (5.08m x 5.08m). Yet I can happily export a larger file than that to v1.4/v1.5.

@Joachim_L Attached two files - both 25m x 25m, one pdf one the original .afdesign (just simple with two rectangles on there). This one gives a bit bigger rounding error in my CAM software (width given is +2.9mm, height is exact though). I'm on Windows, Designer v1.8.3.641 25m.pdf 25m.afdesign

This is the pdf opened back into Designer, shown in millimetres to three decimal places (I'm in the UK so decimal is "." not ","): If I open the same PDF in some CAM software, I get a reported size of 21,999.99mm. @Barc I don't see why it shouldn't work for you, it might depend on the limits of your RIP.

I just created a 22m x 22m file in Designer, exported it to PDF and read it back in. It worked fine.

None of the Affinity apps support sending CMYK data directly to a printer, everything is sent RGB (presumably it's sRGB but no one has answered me on that one). There are two possible ways around it - 1. export to pdf and print from a different app (e.g. adobe reader, yes really, the free reader app is superior at printing than the 'pro' Affinity suite), or 2. check your driver to see if it can force K-only blacks if that is all you need.

It can do unless you are resampling them at export. If the image is 300dpi, it's only that at "actual size", once you reduce it's dimensions you are increasing the effective dpi. Load your pdf back in to Publisher and check the image details to see what has happened to them.

The canvas is a fixed size because it would be nonsensical for it to expand/contract to always fit the contents. The canvas can contain multiple elements, and it's often desirable to use it to crop what is on there. I'm not sure which app you are using, but I know in Designer at least there is a way to not clip the display to the canvas, so you will still see what is outside of it, but it will still crop on output.

Rotating the image is different from rotating the canvas. When you start, the image and the canvas are the same size, hence the corners drop off the canvas. Increase the document size (aka canvas size) enough and you will see the corners again.

How long did you wait? I've noticed it can often take tens of seconds to update this label.