tariq

I've created a Body style for main body text. It is based on Base. I have created a Body_Bullet style for bullet point sections, based on Body. The idea is that Body_Bullet inherits everything from Body and only changes the tab spacing and indent for the bullet point and text start distance. The point of inheriting is that I change Body, I want Body_bullet to inherit those changes automatically. Sadly this isn't happening - I am surely doing something wrong. Changing the Font for Base does cause the font for Body_Bullet to change - so inheritance is working. But for "Leading Override" setting the Body_bullet to "No Change" doesn't seem to inherit the value set manually for Body. In the attached image you can see this see the setting. You can see the parent Body text (A) and the Body_Bullet text (B) which does inherit the typeface but not the leading. What am I doing wrong? Versions are all latest from App Store for Affinity apps and MacOS version.

Thanks - this is helpful. I am dreading dealing with Apple - they are a real barrier to fixing issues....

Attached are 2 video files recording using a smartphone (not screen recording software) so the recording is not interfering with the scenarios. They show: Affinity Photo painting on a 4K external display using DisplayPort - you can see the performance is bad Affinity Photo painting with CMD-Sfht-5 recording - you can see the performance is worse Krita latest - drawing on a 4K external display using DisplayPort - performance is not ideal, but better than Affinity Krita latest painting with CMD-Shift-5 recording - you can see he performance is worse This time drawing was done using a trackpad and not a Wacom tablet. Previous experiments show that the tracking of the pointer position is not the problem (Wacom disagnosti tool). Here we can see the screen showing the actual pointer keeping up with the the software app catching up to the pointer. My conclusions from this are: performance with a 4K display is worse than using the laptop display in all scenarios performance with Affinity is worse than Krita - which surprises me as Affinity uses native Apple toolkit vs Krita using 3rd party toolkits like Qt (I think) performance with the screen recorder is very poor and makes existing performance worse Before we conclude that this is the way it is .. I need to re-iterate that on previous versions of Affinity and MacOS I was able to have tolerable performance for both drawing and recording so something in the software (sam hardwire) has become worse. Thanks a.mp4 b.mp4

on twitter some have asked whether other apps suffer the issue too I don't have photoshop / gimp / Krita installed .. so I tried Preview with the painting pen (and 4k external display) the issue is there but not as bad this macthes my observation that this issue was not as bad, and jus about tolerable, with earlier combinations of previous Affinity Photo and previous MacOS versions

my latest experiment suggests it is not the Wacom tablet as it happens when using the touchpad

latest experiment without a Wacom tablet .. just using the trackpad on the MacBook Pro issue is still there - so this strongly suggests the issue is related to Affinity+Quicktime Records .. and not the Wacom tablet any suggestions? (my apologies for not having done this sooner)

the following observations may provide clues to the cause: latest software Affinity 1.7.2 and MacOS Mojave .. the issues are far worse than 2 years ago with High Sierra or whatever it was called and Affinity 1.4/5 screen recording with Quicktime makes it worse external display makes it worse you might say that I'm pushing the 2015 MBP 15" i7 computer too hard - but this was not a big issue on the same hardware, and indeed a weaker 13" 2015 MBP i5 where in buy very early work there was no problem at all! so the evidence points to a software issue not a hardware issue - but the question is where? is it the Wacom driver? affinity app? quicktime recorder?

fresh install of OS and minimal apps istalled (see below for versions) new video without external display shows issues persist (but not as bad as external display) - still unusable original video with external display: details: Wacom CTL480/s macOS 10.14.6 wacom driver 6.3.36-2 affinity 1.7.2 external display necea244uhd local laptop is MBP2015 15" i7

I really miss these features from else where: Interpolate - CorelDraw had it, as does Inkscape it seems: https://vid-sign.blogspot.com/2014/02/how-to-learn-interpolate-and-pattern.html Bitmap trace - from bitmap to vector drawing - incredibly useful. Illustrator has it.

The file I use is attached. The canvas is 3840x 2160. Separately, the display screen is set to "1920x1080" which is the "default for display" in the Preferences>Displays control panel. I actually set it to this, lower than the usual 4k resolution, when doing screen recordings. When I'm working normally I'm at 4k. Just to add the before 1.7.2 there were issues, but subjectively they seem to be worse with 1.7.2. In case someone is wondering why the image size does't match the 1080p screen resolution - it's an artefact of the way MacOS scaling works as I understand it ... graph_start.afphoto

hi @Cecil - what do you mean Wacom refuse to update the driver? I'm not an expert but I have seen several updates since Mojave including a few days ago. Is there a specific issue that affects Mojave that they're not fixing? If so would you be able to share some info as I'd like to chase Wacom too if that is the case.

just to mark a thread for anyone else who's having performance problems with Wacom tablets I previously posted a thread making a link to Quicktime screen recording - apparently the issue occurs without screen recording too - see bottom of that thread since the original post, Photo and Wacom software has updated but the issue persists

latest information: Wacom updated driver is now 6.3.36-2 Affinity Photo is now 1.7.2 MacOS is current with all latest updates installed I've observed the problem even without QuickTime screen recording . I noticed the fan on my 4-core i7 2015 MacBook Pro 15" goes crazy too. Attached is a simple brush making marks using the tablet - and the CPU consumption by Affinity Photo is huge! There is no quicktime or any other screen recording process running.

hi yes - Hardware acceleration is enabled - see pic below.

same - I've always had problems with parallels batch processing in Affinity Photo - with 1.7 and the previous versions. I have to switch off the "parallel processing" in the dialogue - which means the batch isn't run across the available cores (I guess) ..

I appreciate this is a more complex bug where the cause could be in either one of, or a combination of - Affinity, Wacom, QuickTime screen recording. I raised it here because I didn't have the issue with pre-1.7 Affinity software - which I agree isn't conclusive proof but a strong indicator.

Hi I've used Affinity Photo and Designer for over 2 years now. I regularly use the Quicktime scene recorder to make videos. Performance of the Wacom Tablet has never been amazing - high latency and low sampling rate - which makes the drawing experience less realistic. But it was tolerable. However - since Affinity went to v 1.7 performance has really dropped. It may have nothing to do with Affinity but I think it does. I've kept the OS updated at all times and no update has really caused a major performance drop elsewhere. I've kept up to date with Wacom drivers too. I get my Affinity from the Apple Store and update whenever it notifies me. Here's a recent video of poor performance and the Wacom diagnostics running: https://twitter.com/rzeta0/status/1155854116201095168 Here is a slightly older video taken a few months ago: https://twitter.com/rzeta0/status/1152993266519937024 Has anyone else had similar problems? I'm using a MacBook Pro 15" 2015 16G RAM and i7 processor .. so not a slow machine. The Wacom tablet is the Intuos Pen Small model number CTL-480. We also have a bigger Intuos Pro and that also has the same issues but not with other software. I have noticed the problem is much worse when scree recording than not - but this was not a problem before.

I'd like to test it again when anchored images/other content can reflow with the text looking at the changelog I can't see it - have I misread it?

CorelDraw just popped up with a Mac version. It has a bitmap to vector function (which was in their classic product 10+ years ago...) https://www.coreldraw.com/en/product/coreldraw/mac/ I really think Designer would benefit from this.

still waiting for reflowing embedded content like images .... it's really critical for any DTP workflow .. I know Affinity say it's on the to-do list but it should be a higher priority than some of the things on that changeling list ... let's put it plainly - DTP is not Designer with Pages - it's for working with documents of many pages .. changes to layout, styles, margins, boxes, .. will cause text to move .. and you want anchored content like diagrams to also move intelligently .. you don't want to do that manually for documents of more than 5 pages. that is pretty core.

Given how terrible the initial Affinity Publisher beta was .. and how it has drastically improved as a result of many people here doing testing, and providing suggestions, some of which will be critical to the success of the product (master pages, embedded images reflowing, etc) .. .. who agrees that Affinity should reward this in some way. I don't expect they'll pay a share of their profits .. even though the product would likely have been a flop without the advice provided by friends here... perhaps a discount or reimbursement scheme would be more realistic?

thanks! that's helpful (I'll add this as a suggestion as it should be quick)

ok - is there a recommended way of doing this with some accuracy?

thanks - I tried it and yes it does snap to edges .. but not the centre of the canvas .. is this possible? cutting out the centre is a very common use case

I often use the crop tool. It would be incredibly helpful if it could be aligned / snap to common objects and guides. For example: snapping to objects. snapping to edge aligning to centre of document That last one would be incredibly helpful. Currently cropping is entirely manual I believe.