Jump to content

robrecord

Members
  • Content count

    6
  • Joined

  • Last visited

About robrecord

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Preordered. Thankyou! I have a possible issue I need to report: I had a Designer document with 112 artboards that I needed to resize. in bulk. I thought, "that's a job for Publisher", so I opened the file in Publisher — it was a very recent (but previous) version of the beta. Publisher asked me if I wanted to convert artboards to pages and so I did. All went well. My file was already very large, at between 6–8Gb. (I've got some large embeds but made sure to use Symbols wherever possible). After working with it in Publisher, the file size rose to 11.5Gb. Then the beta version came along that included a manager for linked and embedded documents. I thought I could save some Gb by replacing embedded files with linked files. Despite this, the file size didn't change much. I saved perhaps under 1 Gb. After linking most of my embeds, there were a few that kept asking to be re-found. Even today I always get two images that ask to be re-linked, even though they have not been moved or modified. Over the course of the next few weeks of continuing to work on the document, now in Publisher, the file size ballooned to 16Gb. I assume that there is some redundant data in my file, erroneously added by the link/embed situation. Questions: 1. Will there be a way for me to slim down my file in a future version of Publisher? I need to share it with another designer. 2. Now that it's a Publisher file Is there a way to open it in Designer/Photo and be able to work on all the pages? Currently it only shows the page I was last on and I have no idea how to navigate to the others. 3. How can I stop these two files from always asking to be relinked? Many thanks!
  2. robrecord

    Mojave Batch processing not working

    Many thanks Dan, I appreciate the reply! Good to know it is in the pipeline.
  3. I disagree. I always install the new OS at public betas and have rarely had issues. I am taking a risk in installing a beta, but no-one should be shamed for installing a proper, tested release; especially when they did their homework about it. I agree Apple can be secretive when it comes to owning their bugs. I also have this issue (with batch processing) on Mojave and it seems to relate to the number of cores used when parallel processing. More than 8 images and the job chokes up. Can confirm the workaround is simply to turn off parallel processing. Further issues with slowness are solved for me by disabling Metal compute checkbox (but can select Metal in the dropdown). On Macbook Pro 2017 15 inch.
  4. robrecord

    New Batch Job Parallel Processing

    Hi Callum, I have this issue and my display preference is already set to Metal. Turning off parallel processing however, does work around the issue.
  5. I have an issue with batch processing in Affinity Photo 1.6.7 on Mojave 10.14.1, on Macbook Pro 2017 15 inch. The batch processing does not complete, appears to hang part way through. I have not succesfully been able to get any batch processing to work when the number of files is more then a few (say 3 or 4). I imagine the magic number is 8, based on the following: I am trying a simple operation to add a layer and save as JPG and PNG on 112 PNG files, it completes 8 then hangs while processing the next 8. 600% CPU for about 45 minutes so far. Memory is not inflated, not many disk read/writes. Screenshots and spindumps attached. EDIT: I can confirm this issue can be worked around by turning off parallel processing. The issue seems to relate to the number of cores used when parallel processing. More than 8 images and the job chokes up. Serif, can you acknowledge this please? Can you let me know if a supplemental update will be released that doesn't allow the user to run into this known issue? Also can I please have access to the 1.7 beta to see if this resolves the issue? Thanks. Spindump and Sample.zip
  6. I also have this issue on my Mac:
×