-
Posts
1,291 -
Joined
Posts posted by Lee_T
-
-
Hi Keyonarenee,
Could you please try launching the app whilst holding down control and selecting "reset brushes" on the following window, then hit "clear" at the bottom.
Lee
-
Hi MmmMaarten,
I've not been able to recreate this, could you possibly supply a file and full recipe to recreate this issue?
Lee
-
Hi albertkinng,
Is this on a local, cloud or external drive?
Lee
-
Hi serena.bosca,
One method to achieve this would be to convert the image to a black and white image, then overlay a fill of your chosen Pantone colour with Screen overlay mode enabled.
Lee
-
Hi Pixero,
I've logged this as a bug for the devs to look into.
An additional note regarding your selection issues which can be a little fiddly on iOS in general, you can navigate the cursor by holding the screen space bar for a second then dragging for more precise cursor control.
Lee
-
Hi Demys,
Could you please post your OCIO config files for us to take a look.
Lee
-
Hi cajhin,
Looking at your original question, you might find it's better to use the ellipse tool to draw your circle (you can use the transform tool to size it precisely), add a gaussian blur to the shape, then rasterise it. Once done, you can clip the photo to this shape, and use Clip to canvas with the circle layer to crop the document to the circle area as below:
Q2. Snap to pixel selection bounds will allow you to snap to an invisible box around your selection area, this includes the crop tool as shown here:
You are correct with Q3 that export selection area will export the selected layer only (not pixel selections).
Q5. It's always possible to rasterise/re-rasterise a layer.
Q7. This is a known issue.
Lee
-
Hi icounter,
What happens when you click file > New? Do you get any errors?
Lee
-
-
Hi Meneliki,
I do not believe this to be a general issue for v1, but we can take a look at why this is happening to yourself.
Could you please check for a crash report using the following instructions.
Lee
-
-
-
Hi MatsF,
Do you have reveal enabled on the context toolbar?
Lee
-
Hi Villebon,
Could you demonstrate the issue you are having with images or a video?
Lee
-
-
As it's not unique to those images, could you please take a few different images to test with and send us a problem file.
Also a couple of questions, are you using Apple's RAW engine or ours, and which camera are you using?
https://www.dropbox.com/request/YsTcHY3EYPlvEqfHo413
Lee
-
Any backup from either iTunes or iCloud, check to see if you have iCloud backing up enabled, unfortunately it's unlikely you will recover the documents any other way.
I would advise some kind of regular backup procedure for the future for sure, something automatic like iCloud is ideal as it's completely hands off and you don't need to remember to do this.
Lee
-
Could you please try and save just a simple basic document with some text and some basic images to try and isolate if this is your content or the application/some OS rights problem causing the issue.
Lee
-
Hi Tom Soel,
Could you please send a small sample of the document for us to take a look at?
https://www.dropbox.com/request/bONA1WFhGFqBQIM9ErIO
Lee
-
Hi Ipadprouser2,
Is it possible to show a comparison of the same shot with settings and the histogram visible? These appear to be two different exposures and without the context it's impossible to see what's going on.
Even better would be a copy of the files you are editing:
https://www.dropbox.com/request/u5wwUq0oLoIvhXQJhHzY
Lee
-
If you are able and would like, we can take a look at your document directly (or a sample of) with a description of how to recreate your issue.
https://www.dropbox.com/request/XJT8BccjKBMDHXFrq3tf
Lee
-
43 minutes ago, Affinity Rat said:
While it is working now that I allocated more ram, it is remarkable slow compared to my iPad, disk speed hardly used, ram usage creeps up slowly, cpu never >80%, I would say ipad is faster on large asset files. This surprized me.
Of note though… after loading a large asset file then deleting it ram is Not recovered, after loading large asset file my ram usage goes up to my limit 28gb, if I subsequently delete the category ram stays at 28 gb so if I load another large file the app will crash, looks like no ram left for 2nd file because ram not released and available after category deletion.
Lesson learned after using a large asset file, delete the category, save and restart app to recover ram.
The RAM used is low priority, and can be written over by the operating system as required, unused RAM is wasted RAM. As your software has no idea of your intentions, it would not know that you do not need to use these assets again, so the best way to operate is to hold these in RAM which is much faster than pulling again from disk into RAM. If you do not use these again, and you have no spare RAM, the software (and any software on your computer, can overwrite these files.
It's a common misconception that free RAM is a good thing. Recovering RAM will invariably slow things down as things that do need to be cached in RAM will once again need to pull from the slower physical drive.
Lee
-
7 minutes ago, 413x said:
Ah, hey @Lee_T , my bad presuming that the 32bit was the problem. I admit that it’s a very unconventional way to process the photos. I knew that i am not doing something right but i didn’t expected to break the apps 😁
Thanks, i will check it later.
In fairness, in 16bit this issue doesn't appear so the 32 bit nature of the image certainly has something to do with it.
Lee
-
It appears the layer causing the issue is the duplicate of the original layer at 44% opacity set to Colour Burn overlay mode.
Disabling this appears to resolve the issue, but I'll pass on the file to the devs to have a look at why this happening.
Lee

Text background is white not transparent
in Affinity on Desktop Questions (macOS and Windows)
Posted
Hi Dasher,
On the Character Panel, select the right side colour, then select the "no colour" option at the top right of the colour panel popup.
Lee