Jump to content


  • Content Count

  • Joined

  • Last visited

  1. Huh. Thanks — I didn't think to do that. Appreciated 👍
  2. Hi @MEB I'm trying to use the measuring guides (as per https://affinity.help/designer/en-US.lproj/index.html?page=pages/DesignAids/measuring.html?title=Measuring guides), but when I have an object selected and press ⌘, it just copies the object, so instead of seeing the measuring guide I just get duplicate copies (see video). I have tried all sorts of combinations of other modifier keys, and nothing seems to help. And despite looking through pretty much all of the keybindings, I can't find anywhere to change this behaviour in the settings or anything like that — can you help?
  3. Thanks for this @Old Bruce, I really appreciate you taking the time. However, as my understanding goes (I just tested and can confirm it does act as follows) Replace Existing removes all masters from a page and replace with the selected master. This is a problem, because in some cases a page has multiple masters I don't want deleted. For example, multiple pages in my document have Masters A, C and F. I want them to have Masters A, C and D. If I understand you (and the documentation) correctly, the only way I can achieve this is by removing Master F, — either by deleting the m
  4. That does solve OP's problem (and mine, hence this response), but in a much more terminal manner than I would like. Is there no option to simply remove a specific master from all pages (or even better, a specific set of pages) without having to delete the master entirely? My use case is as follows: 1. I have two numbering and runner masters; one for left-hand pages and one for right-hand pages 2. However, there are a number of pages that don't need the master (i.e. content title pages) 3. When I have to export a sample of the manuscript for review, it needs page numbering. H
  5. I wish I could say there was some intentionality behind the decision, but that was just the colour space inherited from AfDesigner, which I assume came from an image I started with or something (or maybe it is default when starting a project). Interesting fact though (for me at least) — after rasterising the images, the project switched to RGB8 no problem (which seems to be in line with what @DWright said above).
  6. Thanks, I appreciate it. Now that you mention the colour space, I remembered another issue I encountered while working on this project. I tried to change the colour space to RGB8 (in hopes that that would shorten the export time), and CMKY (in preparation for a KDP-ready export) — both times I tried to switch Publisher hung completely. Could that also be related to the colour adjustments? Or is that a separate issue?
  7. Thanks for getting in touch @DWright. I'm busy uploading the document now (all the images should still be embedded). Just on thing — despite opening and saving the file in AfPub, it still an AfDesign file for some reason.
  8. Hi guys (@Jon P in particular) I'm trying to export a 81-page coffee-table style book. I created it in Designer, then imported it into Publisher to prepare for KDP publishing. I started the export process at ~ 01:50 this morning. I just checked on the progress (at 08:50) expecting to see a happy file and and the export is maybe a third complete (so, like 7 hours - see attached image). I was pretty sure that's not normal, and after reading this thread I'm convinced that something isn't happy. This is the first time I'm using Publisher so I'm sure there are things I could do to op
  9. @Sean P I've run into another issue that is probably related to the way Affinity handles multiple artboards. I'm trying to export my artboards (as pdf) to be able to recompile them for QA. But from when I set the name and press save until the files turned up in my folder, it took: Artboard 7: 55 seconds Artboard 8: 1m 25s Artboard 9: 1m 10s Artboard 10: 1m 17s (For the record, I tested exporting as .png and it took more or less the same amount of time). I don't even see the "exporting" bar until a second or two before it arrives in the folder, which means all that time (
  10. Huh. Now you got me wondering whether Affinity: just adds the size of the artboards and treats it as one big pixel layer adds the size of the artboards plus the spaces between and treats it as one big pixel layer processes each artboard as a unique pixel layer (and the sum of those pixel layers is what Sean mentioned). If it is the last one, it would be soooo useful for projects like mine if they could "freeze" processing on completed artboards to minimise resource use (Logic Pro has that functionality and it's awesome).
  11. Wowzers. Yeah, that sounds like quite a RAM-hungry process. Is there any way I can minimise the overall size? The following comes to mind, but you would know better than I: Drop the resolution to 72dpi (it's a brochure for a training, so as long as 72 won't bring in any visual artifacts it should be fine?) Make the gaps between the artboards smaller (I can unfortunately not decrease the number of artboards I'm using, although I assume that would be the first best option) Two related questions, if you don't mind: Apart from increasing the file size and eliminating th
  12. I've attached the screenshot — I hope this helps. I noticed that the DPI is 300, which feels a little higher than necessary. If I reduce it to 72, will it also reduce the project weight?
  13. Thanks for the reply @Sean P I'm afraid I'm not allowed to attach the document here, but I did consider that the issue is with the size of the document — I'm working on 66 artboards (of which only 12 are populated so far). The project file is 262MB (images embedded). (Yeah, this might be a project better suited to Publisher. But I don't have it just yet, so ¯\_(ツ)_/¯ ) I did test the same functionality in a new project later and it didn't hang, so it may just be that the issue is specific to the processing density of the fill / gradient tools? Also, I really need to figure out h
  14. I'm trying to create a blur gradient, so I: Duplicated a rasterised image Added ±65% gaussian blur to the top image Tried to use the fill tool to create a transparency gradient of the top image Every time I select the pixel image and pull the fill tool across it, the program hangs solid. I've tried: Restarting Affinity Restarting the laptop Not using the gaussian blur Changing the image Anyone have any idea why this is happening and how I can get around it? p.s. I'm not sure if this is the best way to achieve the affect I'm looking for, s
  15. Bump ;) Has there been any further progress on this, or are there any workarounds to this at the moment? I have multiple bars at 45° erasing sections of a layer to reveal the image below, I just want to be able to distribute them evenly. Is manually checking the distance the best/only way to get them equally distributed at the moment?
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.