thomaso

What macOS are you using on your macbookair M1 (2020)? – For Sonoma there was a Serif note (Oct. 2023), though it may indicate an Affinity issue, not a general delay with other apps as you seem to experience – whereas this report (Apple developer forum, Nov. 2023) discusses a potential issue in Sonoma. Since you suspect for your setup security issues (and handling): do you have any third party app installed that may influence security handling, e.g. antivirus or auto-cleaning apps? The app EtraCheck can point you to potentially involved apps (including hidden background processes, e.g. run as "daemon"). EtreCheck reads + reports with comments only, it does not fix issues. Independent from the OS version there are various reports where it took time for a specific Affinity document to open, triggered by specific content, for instance here (corrupted linked resource) or here and here (cloud involved?) and a certain .EPS file that took about 30 minutes for various forum users to open (can't find via search).

But why does it add here "[in singular]" – isn't "shame" always singular, can there be "two shames"?

It is V2 only, right? While the OP wrote in the last response "At this stage I cannot use v2 of APh because it will not work on my existing OS." Do you know what area is selected with a cmd-opt thumbnail-click? It seems to result in a quite transparent selection (with highlights excepted). If I fill the black person in the centre with pink I get this: What is causing transparency in this selection method? – Filled with max. tolerance it still has transparency (and now affects the entire image, highlights included, while I would expect they remain excluded, independent of the fill tool tolerance): Whereas "Select > Tonal Range > Shadows" (“Selection from Layer Intensity” seems to be V2 only) causes this: ... and filled with pink in 8% tolerance is not transparent but locally limited as expected:

Me too. I also was confused by the use of 'shame' in a recent response that made me doubt about my German understandig of "shame" as "Schande", the user seemed to combine it with a friendly reaction, which let me search for alternative translations. A forum search appears surprising, too: It finds over 1300 uses, unlikely in the sense of "Schande" as "disgrace" or "infamy". To my ears, the above said something like, “Stupid, I didn’t notice that before.”

To me the thin black 'stroke' looks like the consequence of an imprecise pixel selection (or masking brush) applied to the foreground object, the black seems to be a leftover of the background in the previous/initial foreground image before cropping it. (sorry, I didn't download your .afphoto / have V1 only anyway) BTW, for screenshots it is always worth to show the Layers panel at least while empty or irrelevant panels (e.g. Macro, Adjustment) aren't helpful / don't deliver any wanted information.

While RGB offers rgb sliders only you get the Black option via the CMYK menu only. It doesn't mean to convert to cmyk but just edit with different aspects. The Curves Adjustment allows to affect/edit certain areas of the histogram selectively (while the Levels interface forces you to adjust the entire range from either side (dark or light) and also its gamma option affects an entire range. I recommend to watch tutorials for a.) Histogram and b.) Curves Adjustment, or "just play" with them to experience their affects. Note, if you switch in the Curves Adjustment panel an option in its left menu (RGB, CMYK, LAB) then your curve settings possibly done already will get reset (lost), while the right menu (red or alpha or black etc.) allows you to add/combine several curve adjustments. Plus note, in APhoto's Histogram panel you need to click the yellow warning triangle once it occurs, unfortunately APhoto doesn't auto-update its diagram continuously (and shows a static histogram in the Curves Adjustment panel). The pink circles above mark the areas in your photo that need to get maintained if you correct the underexposure. Compare the jackets in your result (on the left in my screenshot) with the pink area + the back of the olderly woman behind the pole. The yellow markers indicate my done settings (just because of unfortunately quite low contrast in the Affinity interface and the subtle position of the used nodes in the upper right corner of the panel). If you are in macOS you could also experience the Preview.app with its simple image editing options just to get more familiar with the meaning of Histogram and these separate Highlights/Shadow sliders (that work different to those in APhoto) + the centred slider(s) below Preview's Histogram.

"shame" ≠ Schande (German) but also might simply express "it's a pity" (= schade): "It's interesting how a pity that one can use a program for so long but never notice some things..."

Apart from this mask option (afaik since APh V2) the Level Adjustments appears to have the disadvantage that it just has the gamma option to influence mid tones between black and white selectively. Note the missing tones in the white jackets of the two people (in your result, too) and the missing sky in the presented Affinity examples above. Instead I'd prefer a Curves Adjustment with the option for individual nodes (use its picker tool if wanted). For your image it appears sufficient to edit the curve for 'Black' only (choose CMYK from the menu). Like so … (a V1 example without masking) … Honestly I'd prefer to have more sliders than currently available in APhoto / its Develop persona. The existing options lack in focussing on "Highlights" only and a "White" slider to affect specific areas of the histogram. To me it appears a lot easier to adjust e.g. underexposure this way than with the curve/node handling in APhoto whereas I am unable to achieve the same result when using the APhoto Develop persona sliders. -

Illustrator, e.g., does it both when exporting to vectors (e.g. PDF, SVG), (…) (…) expands the outline and then overlaps the "stroke" and "fill" parts. Visually the .ai example appears like a trapping result … an option which Affinity generally lacks. (= Über-/Unterfüllung, @NotMyFault) Ai versus AD: @lacerto, in your post the .ai.png appears twice (where the AD.png is expected as comparison). Can you delete one and reposition the AD.png from the post bottom to avoid confusion?

Your non-alpha png files confuse me: They are saved without the P3-Display profile and show the illustration quite subtle in sRGB. – Whereas if I export the original as 8-bit without Alpha + profile embedded this seems not to show the logo in Firefox (but in Safari, Preview and QuickLook with the expected intensity). Am I misunderstanding your approach? webkit-logo-P3-8bit-noAlpha&profile.png.zip

This reminds me to a recent thread: On mac one can edit an exceptions dictionary with a simple text editor. – Although it works different in Windows I wonder if the 100s of words may get added easier to one of the non-Affinity dictionary files (.dic)? …instead of numerous individual clicks to fill the words into the proprietary file types (.propcol).

You might like this square. – Just choose "Convert to Curves" to get 4 lines. – Or: choose "Geometry Add" to get 2 squares, invisible … ;•) square4lines.afdesign

To work with objects outside of artboard layers you can deactivate the Layers Panel option "Edit All Layers". This prevents from auto-moves into the artboard layer hierarchy but also may make the ticked option "Auto-scroll" temporarily not working any more.

Oh, this examples make Firefox in comparison to Safari indeed confusing and not reliable. Also to me on an AdobeRGB Monitor the webkit logo doesn't show any difference in Firefox but an obvious in Safari. The profile version of the PNG, Display P3, is 4.0.0., so this is not the culprit. Very strange appears your experience with Firefox after recompressing the PNG. I tried to export the PNG in Preview as PNG, JPG and TIF which all showed the logo-illustration in Safari like the original PNG but still did not appear in Firefox (and made me aware that Firefox doesn't open TIF). But apart from this PNG, also the JPGs of this test site don't show their full colour in Firefox, especially the two ProPhoto (Rose, Flowers) and the AdobeRGB (shoes) profiles appear to be 'ignored' by Firefox whereas it shows the difference for the JPGs with Display P3 profile quite like Safari does … which is strange again since the webkit-logo also uses this profile but fails in Firefox.

Do you still get this view – or was it fixed after your various trials / post updates? FWIW, I can't neither see a difference between Safari and Firefox nor a general over-saturation for images without embedded profile. Instead '"sRGB" shows the same, "colorshift" shows desaturated and "grayscale" shows darkend in both apps for images without embedded profiles compared to exports with profile embedded. Also the appearance in Preview looks like this to me. [default browser colour settings / internal monitor with x-rite profile, not "Display"] ZIP with 6 exported JPGs + 3 comparing screenshots in Safari, Firefox, Preview + 3 Profiles: Samples with and without profiles.zip Nevertheless, does your last post also indicate that the saturated appearance in this thread of @zuiui could be a matter of a possible Firefox issue or setting … while AD would show the 'true' colours? (Unfortunately we did not get that used file or the initial screenshots with their profiles embedded.)

Adding a seam allowance to a pattern, with unimportant particulars, makes me think of the Contour Tool: contour tool.m4v Another approach could add stroke(s) to the existing shapes via the Appearance Panel. Depending on the details it needs different workflows and settings. – Alternately you could use a (image) brush which has an offset from its centre.

I have no problems to accept that that tags would not help. But I have difficulties to ignore tags and prevent my eyes from getting attracted by them. Try this forum: https://forum.affinity.serif.com/index.php?/forum/114-frequently-asked-questions-about-v2-software/ Are you honestly able NOT to read tags, especially if the appear with this or more frequency? (And note, currently only two tags are displayed while others require separate clicks.)

If you read the context of the problems with corrupt files, you will see that I gave that as an example. It was clearly not meant for every post. As what was it meant then? Where / how could this questions be asked to achieve more efficiency / to avoid the need to get asked?

... plus your question for possibly involved external storage. Or was this example just written with the goal of in-efficiency in this thread?

I can follow your idea of efficiency but it appears weird with issues where a certain info results in the answer that there is no solution. Possibly wasted words in a thread don't matter, compared to the result. For this kind of issues I'd say, efficiency is to make it work, not to avoid its use. Otherwise indeed a bot could response if a thread gets created with certain keywords / info. If you would like to demand these info before thread creation because of efficiency, why not demanding more info like "Did you try a look in the Help for your keyword?". Actually the entire 'questions' forum is based on in-efficiency: Mostly the answer to a problem is quite clear once the conditions are made transparent, very seldom a workaround needs to get developed first. Many questions have already been asked and answered. The list of inefficiently repeated responses may get long and include for instance to show the document colour settings, the app performance settings, the export dialog settings … which, if done indeed, not only would fill the screen with screenshots but also wouldn't help if NO cloud was used and NO document got corrupted and NO colour issue occurred etc.

Ironically you choose an example which has no solution. If the cloud-info would be given with the thread creation, would the efficiency then be not to answer / ignore the tread because it's helpless anyway and the OP could have read the various warnings about using cloud storage? Or would regarding efficiency an entirely different workflow occur in case of a corrupt file after cloud storage use and let the Serif Bot answer: "Unfortunately your document can't …, When working with Affinity related files avoid external storage. A little bit of efficiency doesn't hurt."

Not that the sorting options available are representative of this forum, but I wouldn't have expected that most of page 1 of "Most Viewed" and "Most Replies" threads don't seem to refer to any specific app or platform (with the exception of the .msi installer ). Among the top of the most viewed threads are 3 with the same topic (image trace), while the apps they mention seem irrelevant (the feature is not present in any app). Also in 2 other most viewed threads a certain app is mentioned without relevance (V1-V2 compatibility / desktop icon). This makes me wonder what advantage would 'mandatory tags' cause in such "most" cases and what keywords do you have in mind that avoid unambiguous keyword assignment + lead to transcend mediocrity while they prevent you from threads in your forum's view that are not 'mac specific' but also ensure that those of your interest get displayed? – (click pics to enlarge) My personal view: • 3 or more tags displayed below every single thread would make it more difficult to my eyes to read / focus on the thread titles. • Tags concerning an app or platform don't appear relevant to me and/or may mislead if the app actually doesn't matter or more than the relevant apps are owned. • Tags that 'describe' a question or issue may be even more misleading, more than the already reduced quality of thread titles and descriptions of users who are not willing to think about a problem but just want it to disappear and get solved by the forum. • More effort for the moderators to make it run.

Probably because of another macOS version, yours also shows extra subheads like "Standard" and "Printjob" presets. Nevertheless, I assume you'll see a similar content like in my last screenshot above if you choose your "Edit Preset List…". Honestly I don't print in Affinity or other apps because of differing setups and consequences. For prints with certain conditions I prefer to export as PDF and print from Acrobat.

You simply ignore the common tools and commands in the 3 apps. If you want to know an answer for APh that was given already in an APub or AD thread it is neither irrelevant nor distraction but rather focussing. That turns the debate to one about statistics in the forum threads and posts. While various posts above mention their impression (feel) about how topics are related specifically to apps we don't have 'objective' numbers. But even if so, should subforums be divided according to the majority of topics/questions and thus increase their visibility, or does it make more sense to try not to push certain topics over others? What if a statistic would show that not an app related topic is mostly asked but rather one that concerns all apps? Should then that topic get a separate sub-forum with the idea it contains the most requested answer and thus is most useful for the entire community?

If it would be that simple there would be app separated forums. Note that your answer I responded to was your answer to a post about personas. And note that I mentioned an APhoto thread asking for the Text Frame panel in APhoto (which does offer text editing tools, too). Like Oufti, I work mainly in APub and do image editing if possible in the Photo Persona of APub. I use APhoto as standalone app only for tasks that can't be done in APub. Same for APub's AD-Persona and my use of AD as standalone app. If I want to use "Expand Stroke" in a drawing done with APub's pen tool why should I be forced to ask in an APub sub-forum if the answer is given in an AD sub-forum? If you now refer to Photo-context discussions it sounds like a request for a forum split by workflows or design-tasks, not by apps. Just like I kind of predicted in my previous post. And your reaction let me even assume, if the forums would be split by apps, users would request to get them merged to one with the same reason: to find related topics easier.