David in Яuislip

Did you convert it like this? Or export as a png, click More and change the Pixel format there Restart Photo and hope for the best I'm officially out of ideas, hopefully firstdefence will be back or another expert will pick this up. Good luck

I can select the channels ok so I think that the file is fine As a quick experiment what about changing to RGB 8 and see if it works then?

Both work here I'd check the Source setting. If it's showing Current Layer then a layer must be selected, not necessary for All layers

If you check the Layers panel I'll bet it says (Image) and is selected Then when you click on a colour a fill will be applied to it Easiest way is probably press V and click away from the image to deselect the layer Otherwise right click the layer and choose Rasterise You'll find a similar behaviour with placed images I consider it an idiosyncrasy rather than a bug!

Tab key toggles the clutter, any good?

View/ Show Tools

Not that I'm aware but what is worse is that this fx can't access previously saved gradients. For me it's useless and I hope it's a work in progress

If all of your cards are the same size then this may work although you'll need to build your own version as this is just an example for an 800 x 600px image Load the attached file, press V, then Replace image Now the fun starts, go into Export persona, select each slice in turn and replace fred, bill, and george with the filename without the extension Export slices, choose a directory and the images will be exported into sub-directories a1, a2, a3 Probably ok if you have a couple of dozen cards, if you have thousands I'd look for a more suitable approach Now if APhoto had it's own built in Javascript....... MultiSave.afphoto

Does this help? The fill layer doesn't play nicely but a rectangle to hold the gradient seems to work FWIW I redraw the shapes as curves in an attempt to get the file size down but more or less failed. I cannot understand 1.35MB for such a simple vector construction fill_effect_mask---.afphoto

Very true walt.farrell but we all work in our individual ways. Having clicked on one file in Explorer then the rest can be previewed with the down arrow On a personal note, I have had thumbnails turned off for years and prefer to scan a directory with Irfanview; the thumbnail cache just eats up disc space and I prefer to avoid that

Why not use the Preview pane ?

Part 2 Forget the Recolour layer Use a Colour Overlay fx on the layer and you can enter hex values RecolouringPart2.afphoto

These are my findings which looks similar to yours: 1. Rectangle, red, Gaussian blur, rasterised 2. Copy of 1, recoloured with Flood Fill Tool, perfect 3. Rectangle with gradient, opacity 100% on the right, 0% on the left 4. Copy of 3, rasterised, recoloured with New Adjustment Layer/ Recolour, perfect 5. Copy of 3, rasterised, recoloured with Flood Fill Tool,, rubbish If you need a specific color like #000096, I can only suggest setting that with the RGB Hex sliders, changing to the wheel and copying those HSL values into the Recolour adjustment dialog I've attached the .afphoto file for you to explore some more, good luck Recolouring.afphoto

Try this. Click on the Colour Panel on the right and ensure it's set to RGB Hex Using the Colour Picker Tool from Tools on the left, click around the image and notice that the hex values update and the Colour disc and Picked disc both update Now drag the picker from the Colour panel over the image. Notice that the Colour disc doesn't change but the Picked disc does. Click the Picked disc and the Colour disc and hex values will update

FWIW I can replicate that, however Rasterise & Trim doesn't cause the Transform shift Even weirder, if you place the Unsharp mask below the image then the shift doubles!

Funny you should mention that, it's ginormous

I have only one Korean font here but it works ok

I have just noticed this since switching to a 4K screen recently and it's driven me nuts. Affinity is properly exporting the file at the correct dimensions but the browser doesn't display it as you'd expect. There is a property called devicePixelRatio which the image dimensions must be divided by - at least in theory. Chrome reports 1.100000023841858 which doesn't work. Edge reports 1.25 which does. I've attached a quick, dirty html file which may help to explore further. I've hard coded the ratios but they'd need to be found for each particular browser by javascript then set the image rule accordingly BrowserImageError.htm

Here I opened a raw file, clicked develop with no adjustment. Went back to Develop persona and rotated it. Artefact in the corner. Rotation in the Photo persona works. To be honest I think that APhoto is poor for processing raw files compared with Photolab which is one of the best

Yes, the rotate button surprised me, I wish it worked the same as Photolab but hey ho... If you need to rotate the image then put the cursor outside of one of the corner points and it will change to a rotate arrow. Alternatively, with the cursor over the image, hold <ctrl> and you can use the spirit level to align horizontal or vertical. The corners are a pain, Photolab crops them automatically but you'll either do that yourself or try the attached macro which fills in the gaps, it's successful 9 times out of 10. If you see artifacts in the corners then they need to be erased before running the macro. Good luck dcInpaint-TransparentCorners.afmacro

On Windows 10 it's here %AppData%\Affinity\Photo\1.0\autosave

<ctrl><space> drag doesn’t zoom but <space><ctrl> drag does 🙂 although the action is somewhat different from Adobe Or hold <ctrl> and use the mouse scroll wheel

Not if it's intentionally done for performance reasons. There is no perfomance gain associated with a bloated file. It takes longer to read from disc and longer to parse And I suspect that at some point there would be enough "gas" space in the file that Affinity Photo will rewrite it and compact it down to the needed size. But that's only a guess, and not something I feel like experimenting with. That is, however, the way that .afphoto, .afdesign, and .afpub files work. And it's quite easy for me to believe that the other proprietary format files used by Affinity work the same way. The 'gas' shouldn't be there. I suspect that Serif has missed a trick, there is no point in converting a straight ascii LUT into a binary file if the maintenance turns into a problem. Regarding .afphoto file sizes they seem to be huge compared with the basic image size within so heavens knows what it contains. cf Adobe tiff format, a piece of genius then developed into .psd

Luck wished. Nice weekend

Makes no sense to me Walt, when stuff is removed from adjustments then the file should be rewritten properly. Leaving FF padding spaces is an error no matter how you look at it. I could add even more LUTS then remove them and I suspect that the file would keep growing in size which I suspect would increase the program loading time but that's a job for the Devs not me.