Jump to content
You must now use your email address to sign in [click for more info] ×

Lee_T

Staff
  • Posts

    1,291
  • Joined

Posts posted by Lee_T

  1. 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:

    image.png

     

    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:

     

    image.png

     

    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

  2. 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

  3. 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

     

  4. 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

×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.