NotMyFault

You can use linked files in documents and assets, but you never share any settings (the home screen / settings) on iPad. As this thread is about default color profiles, to my knowledge you cannot share them. Except you use document template files - again a seperate topic as linked files are used, and not settings inside the app.

I could provide a procedural texture filter which generates RGB black from cmyk K only black, and leaves all other colors for Affinity default conversion. Assuming that the document color format is cmyk and jpg export is RGB.

Thanks for your reply - but I‘m confused- the jpeg is below thumbnail in size, and where can I find the description of the approach?

Depends on many factors like colour format and profile of document bitmap or vector layers in document Export format vector or bitmap, PDF, jpeg, png etc? what should happen with other colors, e.g rich black? Can you elaborate more what you try to achieve? Why can’t you use RGB black directly?

Well while the move tool is active you can resize the rectangle in all Affinity apps. if you want the child layers to be not impacted, select „lock children“.

Hi, as a lucky owner of a new Canon EOS R6 Mark II and RF 24-105 F4 i'm very disappointed with the RAW Persona results / image quality. I tried to get a reasonable match bewteen the RAW and the out of Camera JPG. If you compare both images (opnened in Photo, zommed 200%) and try to use most basic settings to get matching results, the quality in Photo is so much behind Canon JPG and DPP that it is effectively unusable. Whatever you try, the noise reduction in Photo leaves ugly dark spots, unless you try extreme settings which remove all details It is impossible to reach the same level of details. Photo is unable to provid the level of crispness the R6 is loved for Both combined: Photo gives ungly noise, and looses all clarity and microcontrast. The capture conditions of the test image are chosen to make this differences noticable. It is far less noticable in regular condition images (lower ISO). Side nodes: I had to raise exposure in Photo by ~0.4 to reach same brightness Camera uses "Digital Lens Correction" settings which increases sharpness based on Canons secret IP of its own lenses. Results may be less different for 3rd party lenses (i will try later with Sigma lens). High ISO Noise reduction is set to "low" for test image (if i rember it right) Image uses ISO 25.000 intentionally All settings in Photo are to best match settings in Camera Picture Profile is "Standard". Attached: Original RAW file Out of Camera JPG Scrennshot of both files opened in Photo, using Serif RAW on Windows PC 069A2634.CR3 069A2634.7z

That is extremly interesting. Do you have an example? Speaking specifically of iPad. On Desktop, some settings are actually shared - different story.

I never experienced something like that over several years of usage. Only in case you personal settings may get lost in case of new installation after deleting the app and settings, or upgrading from v1 to v2 which is a new install. Especially on iPad, the apps are isolated already by OS in sandboxes so it is impossible that other apps can change the config. Bit remember you may have multiple Photo apps installed (v1, v2, retail, beta) so you may use another instance - or even publisher in Photo persona.

In my view everything works as designed, and with reasonable design. You need to set the default color format and color profile in settings before opening a RAW file. Changing of color profiles after starting non-destructive edits with adjustment layers etc must be avoided. The only suitable way is to change corporate profile at export, for a rasterized export format. Changing color formats only for pure bitmap documents, but not for layer stacks with adjustments and filters (which depend on color format). Rare exceptions may be possible, but you must know what are you doing and what side effects will occur.

This is to be expected. adjustments do not get converted to give visual identical results when the color space or color profile is converted. most adjustment work „simplistically“ on color values, e.g. curves, levels etc. when you convert to a wide color profile, the color values in pixel layers change, so the relation between input / output will change. if you change color profile from rgb to cmyk or lab, some adjustments simply stop working e.g. invert gives useless results in cmyk.

You may try this. A simple channel mixer adjustment can do the trick to show areas exceeding given limits.

I spent a few hours testing lots of combinations, and documented my results in the forum. Your screenshots show that you did not follow the tutorial exactly, and deviated in many relevant aspects: tutorial says exactly two layers, pixel on bottom, mask on top. you used a group of vector shapes, and placed a rectangle with channels mixer below. This is not to blame you, just an observation and my conclusions. It is too time consuming for me to reverse engineer your edit steps and guesstimate your intentions. Please try it again on your own, following exactly the steps as described. From older discussions i know that many new Affinity users perceive this learning curve as too steep, and i understand this. If your time is worth more than 200 bucks per year for Adobe, make a wise decision.

The trigger condition is simple: If mask is full black: TGA export is broken (mask is ignored, export is fully opaque). If mask is not fully black, but is only non-black where the pixel area is black: The exported TGA does not allow to recover RGB pixels. all RGB values get zeroed out. You may have any number of black mask pixels but you need at least one single pixel which is both not black in RGB channels and not black in alpha channel. Then the exported TGA file can be fully recovered in RGB channels. Tested on Mac with Photo V2. You milage may vary on iPad or V1

not for TGA export on iPad and a fully black mask. It is a specific edge case.

To be precise: specifically if all / majority of pixels are alpha zero. I still need to figure out when it toggles from correct (as before) to unusable. This has not changed. V1 and V2 behave identical. I only never checked for this specific case before you raised the issue.