v_kyr

See related ... file ~lock~ site:forum.affinity.serif.com

Well a 5DMk2 is an older model, so it should be nowadays long time supported everywhere. - I recall having once shooting with that Canon model (a long time ago) in a studio portrait session, got quite good & pleasing results. Had to use then that cam since the studios lighting system and flash trigger were explicitely synced to/on that cam.

Which sort of software? - Usually the Canon printer driver for your printer should handle that in conjunction with APh. The printer driver is either way reused from APh. Further what macOS & APh version do you use and which Canon printer model?

Well I can't tell for Canon RAWs as I'm more a Nikonian and no Canonista. But one probably better test this with some theme related Nikon Z8 he* NEFs then here (maybe from here). BTW Nikon NEFs can be also taken in HLG, aka "Hybrid Log-Gamma (HLG)" technology which is a High Dynamic Range (HDR) standard that allows photographs with a wider range of tones, minimizing loss of detail in highlights and shadows. And AFAI recall, an HLG-powered NEF uses BT.2020 Color Space and different tone curves, which I'm not sure if it's all then treaded correctly by the DNG Converter. - Thus I said that one has to generally check/test here, if Z8 he* NEFs with certain applied settings will also result (in)to appropriate converted DNGs.

Well as this functionality was just added recently, via the firmware 2.00 update, you will probably have to use the lastest Nikon NX Studio 1.6.0 version actually, in order to make any use out of it. Nikon releases the upgraded firmware version 2.00 for the Nikon Z 8 full-frame mirrorless camera Pixel Shift Shooting (Z8) Pixel Shift Shooting (Zf) Other than that you would have to stack images in APh accordingly in order to get higher resolution results. - See also ...

Prioritization is always a tricky topic and I think one have to differentiate between bugs and features, even though a lot of them are often also related. Personally I think, that everything which proves to always crash the apps and/or leaves them in some/an instable state, has the overal highest priority. Followed by critical mostly used functions then, which don't really do what they are inteded to do and thus are useless to faulty (so not working correctly) in their current state. In terms of new features, it will be probably what can be done relatively fast, on top of the already available base/foundation. Everything else more complex is probably pushed further back, because there are also many errors to be first cleaned up that are interdependent and therefore can generate side effects and new errors if not fixed first.

For that sample it should be easy with pretty all selection tools. - However I gave "Select sample color" a try here, even I mostly use the "Flood Selection Tool" and "Selection Brush Tool" under v1 ... screencast_selcolor.mp4

Yes that should work, as the latest Adobe DNG Converter versions do support to deal with high efficiency compressed NEFs from Nikon Z8/Z9/Zf cams. - Though that's then of course always an extra step to make/take in order to get files reused in APh and one has to see how APh then interprets those DNGs. Meaning here, that one has to setup the Adobe DNG Converter conversion settings in a manner, that the resulting DNGs then look initially as default nearly Ok when reopening in APh afterwards.

Most of them will fail here for that image and will remove the middle gray area parts too. Even those who claim to remove checker parts, as far as they just urge from colors and not also from repeated pattern structures.

Well, reminds me somehow to visual tab stops in ADe v1 for frame text ... ... which were showable in Apub v1 for frame text, but not in ADe/APh v1. And on a closer inspection I then once saw that the capability was there but not directly obviously activatable. That's all probably marketing wise stripped down (disabled), so people have to use & buy the other apps of the Affinity suite too, in order to be able to make real use of any shareable option then.

See theme related ... Affinity Photo's used Libraw library doesn't support yet Nikon high efficiency compressed NEFs from Nikon Z8/Z9/(Zf) cams. And it probably never will when depending only on Libraw here, as Nikon high efficiency compressed NEFs do use a third-party RAW encoder/decoder from intoPIX called TicoRaw. This in turn means, that a software RAW converter vendor has to use Nikon's own SDK or alternatively the TicoRaw SDK in order to be able to decode high efficiency compressed Nikon NEF files. Actually, Nikon Z8/Z9/Zf cam users will have to shoot RAW in lossless (uncompressed) NEF/RAW mode, in order to be able to make any use out of their NEFs in APh.

Your only chance is to exchange stuff in some file format which both v2 + v1 apps can deal with, as PDF. - But even here it depends also highly on used features, as v2 offers more tools & capabilities, so things v1 apps don't support.

It will always depend on what one does and through on the tools. Here's a last years test for Firefly (in german, use a translater for other languages). Generative Fill – Die Adobe KI im Test Though to be fair, the AI tools also do get better and better over time, as they learn too to some degree. - I sometimes play with several online AI tools like these here (there are some different purpose AI tools to select from there) in order to see how they evolve.

So far I can't see any rasterization (base64 uuencoding) in that SVG file. - BTW you may want to SVG export that with "flatten transforms" and "Add Line breaks" in order to get rid of unnecessary transforms, so you also can better inspect that in some editor then too. Further use a webbrowser to preview the generated SVG result not APh. Or instead of a webbrowser use a tool like Gapplin to preview the generated/exported SVG result.

As that's a v2 ADe file can't open it for inspection here with a v1 app. - Thus just a hint here, inspect the generated exported SVG inside a text editor, in order to see what portion of it (that drawing) has been rasterized. Then check in ADe if some layer uses a blend mode (like erase) or some adjustment made, which yields to rasterization on export.

Well, this is probably too much fiddle and complicated for many people. - It would be better to have a user friendly switchable mode that then doesn't overlap shapes when aligning. screencast_colcircles.mp4 circles_capture.mp4

See also this tutorial ...

See related ...

No not really, but you can use third-party tracers/vectorizers therefor and reuse their vectorized SVG/PDF output in any of the Affinity apps. - See also ...

I assume here you will deal with the scanned JPG/PNG image, thus not with patterns as plain vectors? The easiest way to do that in Affinity apps is probably to build some own bitmap/pixel style out of your scanned image. As you can use these to fill some unstroked shape (rectangle, ellipse, ... etc.) in a scaled repeated manner if wanted, via adjusting the fill size handles. See related ... Styles Styles Panel ...

Many programs create sub processes which do some threaded work for the main program. It's often used to isolate tasks like multiple file loading/opening, so that if one of the instances fails or crashes, the rest are still running and can continue or recover. - For example some web browsers use sub processes for each of the tabs, as this isolates each tab so that something in one tab cannot snoop on the other tabs. Further, you can use some Sysinternals tools to inspect what for handles (open files etc.) some running process has/uses. - See therefor ... Process Explorer Handle

That's an already known issue, escpecially when used in conjunction with external monitors.

Well, if you clip the lines to the circle/donut, or instead make a compound of the whole (donut + lines) the lines can still be moved, resized etc. (when selected inside the clipping/compound groupings) if their layers aren't locked. - A geom add here for the donut + lines probably didn't worked, if your lines are plain strokes which haven't been expanded as strokes (...at least for ADe v1 it would behave like that here often). - Further why a donut instead of an ellipse?

First for macOS there is already APh v1.10.8, though it may doesn't change much for selections here. I tend to use for quick background selections (around a main subject) instead the Flood Selection Tool instead, with a lower top setup "tolerance" setting, let's say about 16-20%. Then zooming in and inspecting the whole image selection, possibly adding or removing parts (+/- if needed) from that initial selection then via the Selection Brush Tool. When you open the brightness/contrast adjustment panel on your background image (without applying the adjustment setting, so delete to close not apply it) and lower brightness, you can see how uneven that background color pixelwise really is... ...which is not that obvious in it's initial bright shown form. - Thus one has to inspect made selections carefully, or work on a B&W silhoutte like copy of such an image's background layer, in order to get some more exact and finer grade off all wanted selection, which you then can reuse on/for the main background layer. Overall meaning here, that taking a sampled color for the selection isn't such a good way here for such images with uneven colored backgrounds (see above screenshots).

Basically it helps more if you would name which concrete Affinity app here and if a v1 or v2 one. - However try to reset the app to it's defaults, for a v2 one try out ... ... for a v1 one do it this described way ...