Jump to content


  • Content Count

  • Joined

  • Last visited

About Delineated

  • Rank

Recent Profile Visitors

559 profile views
  1. Yes, pretty much every SVG file that you can find anywhere will not render correctly in Affinity Designer after it has been optimised with SVGO v1.3 or above but will render correctly in all common web browsers and other software following SVG specifications. A workaround in the meantime until this bug is fixed by the Affinity developers - if needing to edit an SVG file in Affinity that has already been run through SVGO - just open the SVG in a web browser like Chrome, then "Print to PDF" (Ctrl+P on Windows), then save the page to PDF and open it with Affinity to extract the vector graphic from the PDF which will then be correctly formatted.
  2. I'm also on a MacBook Pro with a 4K external screen. This is indeed a pretty serious issue, how's the beta with the fix coming along?
  3. Yes, the workaround suggested by @dublbutted works. Thanks.
  4. AD 1.6.1 and AP 1.6.7 on macOS High Sierra 10.13.3 When I click on the "Fonts" select/dropdown menu in the top left corner when I'm using the Artistic/Frame Text tools nothing happens - the drawer that usually shows all fonts doesn't even open - but a beachball appears until infinity and then I have to force quit the app. What I tried to do that didn't solve the crash: 1. Resetting all preferences by holding Ctrl when opening both apps. 2. Completely deleting and reinstalling both apps. 3. Using Font Book, disabling all "User" fonts and also validating all "Computer" fonts. I've been using AD and AP for a while with no issues for a long time. The only recent change that I can think of which could be possibly triggering this is that I updated Pages/Keynote/Numbers to the latest versions that were released yesterday (7.0, 8.0 and 5.0 respectively) and since then I'm getting the Affinity crashes (but the Apple iWork apps work all fine). Could the updates be a coincidence or is there a relevance? How can I troubleshoot further?
  5. Just bumping this. Every other graphics editor that I've ever worked in has supported shorthand hex, here's for hoping that Affinity would finally be able to do this in 2018?
  6. So it's not a bug, but it's a feature? If so, I still think that the UI/UX in that scenario can be improved - i.e disregard the extra metadata by default, but have a warning dialog upon opening the file that says something like "This file contains non-standard metadata, please press OK if you want to display it". Just a suggestion...
  7. OK, this bug has nothing to do with a batch job. Just by opening one of the affected original images in Affinity, you can see what's going on - there is some sort of a weird path added as a mask to the jpeg, probably on purpose when the original photographer was retouching the image to fix overexposed windows/light in whatever software they're using for that. This is strange, as I thought that a JPG should mostly contain raw pixel data, and not masks/paths?
  8. Affinity Photo 1.6.6 macOS High Sierra 10.13.1 After adding a bunch of images of the same photo session to a batch job in order to resize them, Affinity Photo corrupts/destroys some images by adding solid white almost throughout the whole image, while other images are OK. Attached is an archive containing the same 4 images - before and after a batch resize. The 2 get corrupted every time after a batch job, while the other 2 are OK. Affinity Batch Bug.zip
  9. I have an SVG which contains a gradient with 2 stops (darker blue to lighter blue) that I created with Affinity Designer that I later optimised with SVGO for smaller size for web use. However, after re-opening the optimised SVG in Affinity Designer, the gradient doesn't show - the entire curve appears as filled with only the first colour stop. However, when clicking on the curve, the fill settings show the correct gradient with both stops. The gradient in the optimised SVG shows up fine in all web browsers and a few other graphics editors. Attached is the file. Thanks mountain.svg
  10. The Batch Job feature in Affinity Photo is great, but one crucial feature that's missing is the ability to select multiple folders and subfolders and all the images inside automatically being added to the list. The whole idea of the Batch Job is to save time from manual labour, and sometimes having to go through tens of folders and subfolders and manually selecting all image files to be batch processed is a very manual and time consuming process. Thanks
  11. Hi Sean, Indeed it is the EXIF information that's the culprit in both liquify issue #1 (pinch/punch mixup) and liquify issue #2 (twirl/pinch mixup). I took 2 images with the front iPhone camera - one landscape and one portrait. The landscape image triggers issue #1 and the portrait image triggers issue #2. After removing the EXIF metadata of the images with ImageOptim - the images change their rotation/orientation from the originals and Liquify in Affinity works as expected. Attached is an archive containing videos showing how to reproduce the issues and also the original photos as well as the photos with the removed metadata. Thank you. Affinity_Liquify_EXIF_Bug.zip
  12. Hi Sean, I'll need to do a little more investigating as the issue can't be reproduced with every image - I tried a bunch from the internet and none seem to show the issue. I think the issue may be related to images taken with an iPhone, specifically my iPhone 7's front (selfie) camera as most of my selfies manage to trigger the issue every single time, however I'd prefer not to upload my personal photos. I think the iPhone may be incorrectly rotating/flipping the images somehow when using the front camera which could be contributing to the issue. However, while testing, I managed to find a separate issue with some images where the Pinch/Punch tools aren't reversed, but instead the Twirl/Pinch tools are mixed - i.e when using Twirl it applies the Pinch effect and the other way around in the preview, but this one actually saves exactly how it displays in the preview after clicking "Apply" - so it's not reversing the effect after applying like the original issue that I described. I'll update the topic once I have more time to test and more data.
  13. When inside the Liquify Persona and using the Pinch or Punch tool - the effect is correctly applied while inside the Liquify Persona, but as soon as the changes are applied – the effect is reversed as if the opposite tool was used instead – if something in the preview was "pinched", after applying the effect the result would become "punched" and vice-versa. Affinity Photo 1.5.2 on Mac, but has been happening for quite a while, possibly since many versions ago.
  14. Hi, I remember seeing this requested once or twice and I've even requested this myself 2 years ago and I thought it would've been simple to implement. Can we please have support for shorthand 3 character "hex" colour values like in CSS that combine 2 duplicate characters into 1 - i.e white can be #FFF instead of the more verbose #FFFFFF, yellow – #FC0 instead of #FFCC00, #333 for dark grey instead of #333333 etc. Currently, only #000 for black accidentally works, but none of the other shorthand values do. Thanks.
  • 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.