NotMyFault

For this task, Photo would be better suited, as the layer is a pixel / raster layer. unfortunately the red area includes anti-aliasing where hue and lightness can differ Possible options to get this done: use pixel based tool to make a selection, and fill with blue by fill tool or brush use HSL adjustment, select red colors, and adjust both hue and lightness to visually match the target color use a vector shape in target color, with blend mode „color“

Can you please upload an example document? which color format do you use, GREY/8 or RGB? Those do not match 1:1, and you need to use the matching color mode in color panel for the document color format. The info panel automatically converts between document and chosen color format, but for some cases the conversion is not accurate, e.g. CMYK info panel may ignore the document color profile, and use a default one.

It is stored in a hidden folder. just delete it after all Affinity apps are closed. Autosave files are another source for wasted disk space. Delete the files frequently.

The file is simply a surrogate for RAM. Affinity tries to mimic OS page file logic internally. If you have a document which requires more RAM than available in OS (virtual RAM, not physical), Affinity will use this file on disk as alternative. The App will become totally slow, and the PC will too as the disk IO will become saturated. Affinity Apps can use only 32 (or 64) GB RAM, even in case more RAM is installed. The only way to avoid is to keep the working document as small as possible: don’t use excessive DPI or document size convert large linked/embedded documents into smaller (e.g. by cropping, resizing, color format conversion etc) use file formats supporting lossless / lossy compression (e.g. avoid BMP) inspect file size in Ressource manage and finder/explorer split large documents into smaller parts

Sounds like color profile related issue. Which color profiles are you using in Photo documents, Display, and PC/Mac settings for Display? Most viewers will show the embedded JPG for RAW files which was generated in Camera, using all settings (like exposure, sharpness bias etc). Affinity ignores the embedded JPG, and presents the RAW data, interpreted using the „Development Assistant“ settings which can be totally different from Camera presets / embedded JPG. Unfortunately for most modern camera models, Affinity is unable to read „receipts“ or „camera profiles“ from RAW images, since those meta-data belong exposure / white balance is often encrypted, only available for SW vendors willing to pay some ransom license cost.

You can define your own keyboard shortcuts, please check if this function is available (not on my PC currently, cant check) https://affinity.help/photo2/en-US.lproj/pages/Workspace/customizingShortcuts.html

In Designer (not Photo) you can use Appearance panel to add multiple gradients. If Photo we might find an alternative approach to achieve the same effect. Is it correct that you add a kind of vignette by the process? You may use a vector shape and layer FX / blur or outline / shadow fo the same effect.

I would try to stitch only a few images covering that areas, and inspect those images for any potential issues: to they have same exposure settings / brightness in those areas? do you use RAW files for stitching? If yes, it is better to develop them (and save as tiff/16) before, to get the full RAW engine does any of the source images show defects (blurriness etc)? too long time span between shots could lead to e.g. clouds or other moving objects change too much enough overlap in images? how many images do you use to stitch one final image? when you talk about manual settings, does this refer to camera settings or stitching settings? it is best practice to have a fixed aperture setting at least during capture

Another similar report

Probably this bug

Would it be possible to add this as feature request? It has been asked for many times, and the explanation given in older posts about about some legacy Windows GDI restrictions falls short.

This is not too complicated. convert to lab mode have both layers aligned in one document (e.g. using new stack with alignment) use channels panel to create spare channel from high-res layer use channels panel to overwrite lab channel of of colorized image

Eine Frage zu deinem Workflow: können Pixelate Filter und Posterize Anpassung ggf. Den Vorgang automatisieren? Mir schein Du leitest von einen normalen Bild eine Version mit geringer Auflösung und reduzierter Farbpalette ab.

ich kann das Problem nicht nachvollziehen. Kannst Du auch die betroffene Datei hochladen? Eine mögliche Fehlerquelle: prüfe ob oberste Ebene „Raster“ zu 100% deckend in den Farbpixeln ist, und wirklich weiß. Dazu nur diese Ebene aktivieren, auf 100% setzen, und mit dem Channels panel bzw. Info Panel einige Pixel prüfen. Ich hatte Probleme wenn die Pixel selbst teilweise transparent sind.

Hi, can you upload the document, and provide a screen recording showing the full screen / window?

The tone map persona can be used. maximize local contrast, and play with black point. reduce saturation to zero. you may need to add a curves adjustment later.

Well, then please explain what is the difference between an export of the default full document slice and what you think a different continuous export should do.

time code 6:00, but you should view it from beginning

Continuous export does exactly this. It will export in background while you continue to edit.

Maybe this ? https://affinity.help/photo/en-US.lproj/pages/ExportPersona/exportPersona.html (Optional) On the Slices panel, select Continuous if you want to automatically re-export export areas if the document is subsequently changed. This option is only available if Export Slices (n) was selected above.

You can borrow an image frame from Publisher,. drop the raw files into them, they will scale to the frame size. image frame.afpub

I share this frustration in general. But on the other side, and this might be not understandable for you: some users less experienced with Affinity terms or forum software, might have actual difficulty to use use the search, or are in a desperate state looking for help. Affinity says all forum users should ignore posts which you simply don’t like (unless there are violating guidelines). And don’t forget this forum is a social network for humans, not a „cold“ database. There are people posting here to have social contacts, and the technical/factual part is actually less or not important at all. Have mercy with them.

There are older reports observing slow startup times for all Affinity apps due to loading all fonts. https://forum.affinity.serif.com/index.php?/search/&q=Slow startup fonts&quick=1&updated_after=any&sortby=newest&search_and_or=and

Yes, absolutely. I corrected a outdated link to avoid some future reader using it. Our post began to be redundant at the time we started to write them (before hitting submit), not at the time I corrected the link. The only other option would be to hide my post. As Walt already answered incl quotation of the wrong link, it would be a bad move as Walters reply with the wrong link would stay. It seems Walt has removed his replay in the meantime.

We posted at almost the exact time. My crystal ball cannot see if you have started to edit a new post before me. By chance you were a split second faster this time. No reason to call my answer redundant.