Jump to content
geeknurse

[AP] Processing of Pointer Device Events is Lagging or Drops Events

Recommended Posts

Hi all,

 

I am considering to replace the usual suspects (PS, Gimp, Pixelmator, …) with Affinity Photo.

 

During my evaluation, while creating sketches, I noticed that brush strokes begin with a noticeable straight part though I was drawing arcs of lines (see the video attached).

 

It seems that Affinity Photo does something time consuming when the first pointing device event is detected before it continues to process subsequent events. Perhaps it does something like copying the layer's contents for undo?

 

Interestingly, in a video posted regarding the delayed finalisation of vector strokes in AD, if you look closely at the strokes' beginnings, you can observe the same behaviour.

 

My set-up:

 

iMac (27-inch, Late 2013)

3,5 GHz Intel Core i7

32 GB 1600 MHz DDR3

NVIDIA GeForce GTX 780M 4096 MB

 

OS X 10.11.5 (15F34)

 

Wacom Intuos5 touch (driver 6.3.16-10)

 

Cheers,

geeknurse

Affinity Strokes.mov

Share this post


Link to post
Share on other sites

Hi geeknurse,

Welcome to the Affinity forum :)

I have managed to replicate this even without a Wacom tablet. I can simply do it with my mouse.

 

If I select a brush and start doing a quick circular motion and then press the mouse button to draw, the initial part of the line is straight, even though I'm going in a circular motion.

I will put this forward to development for their consideration but I do think an improvement needs to be made here. I'm surprised I haven't noticed it before so thank you for bringing it to my attention.

Chris. 

Share this post


Link to post
Share on other sites

You are welcome! :) And thank you very much for your short response time, you are awesome!

 

( In PS CS6 for OS X there's a bug regarding modifier key states and tool states which renders PS unusable. They didn't respond for over a year now. (-_- °) )

Share this post


Link to post
Share on other sites

Some additional information regarding this issue:
 

  • During my evaluation I labeled some sketches or added notes by writing in block letters using the brush tool and my tablet. The lag causes most of the letters to be barely readable since arcs or initial directions of lines are affected as described above. Furthermore, when strokes only take a short amount of time, which happens often when you write block letters, those strokes end up as single points as if the brush never had been moved. I think this is another important detail for the devs in order to identify the cause of this issue.

     
  • This seems to be related:

    https://forum.affinity.serif.com/index.php?/topic/20455-inpainting-brush-and-wacom/

    Though I doubt the OP's observation that the issue did not exist in Version 1.4.1 since this is the version I am using.

Share this post


Link to post
Share on other sites

Hi geeknurse,

 

Unfortunately there hasn't been any movement on this since I reported it. Both Designer and Photo suffer from this issue at the moment as well as the Windows version  :(

Share this post


Link to post
Share on other sites

Hi Chris,

 

This is …a bummer. (_ _  )

 

Essentially, this means that Affinity Photo cannot be used for painting or anything that requires natural strokes. I was so happy to have found the Affinity apps. Isn't the handling of pointing device events the foundation of a (pointing device based) graphics editor?

 

Anyway, thank you for replying. I will come back later this year and see if there's a fix.

Share this post


Link to post
Share on other sites

Hi geeknurse,

 

I'm sure this will get fixed soon enough. I'll see if I can bump the report and get some movement on it but I know the dev guys are incredibly busy at the moment.

Cheers.

Share this post


Link to post
Share on other sites

Hi Chris! :)

 

Half a year has passed. Did your developers have the opportunity to address this bug?

 

Seriously, though Affinity Photo has powerful tools and loads of configurations you cannot use it for drawing naturally. Photo editing, colour grading, composing—all that works fine since you do not rely on the stroke but on the final position of the pointer. But drawing (especially when hatchuring) and handwriting is not possible.

 

If you'd fix this bug which resides in the _foundation_ of this app then Affinity Photo would plainly be the most potential PS killer for a very attractive price!

 

Does Serif have any "official" opinion on this? Have others complained about this? Or do others not create concept art, drawings etc.? Do they workaround this by performing slow strokes? Am I not the target audience since I don't do photo editing?

 

Best,

Pierre

 

P.S.: I really think of creating a demo-app with a pipeline of cached pointer device events which then will be processed asynchronously just to show you guys that there is something wrong with the way our devs do it.

Share this post


Link to post
Share on other sites

Hi Pierre,

Nothing has changed as far as I can tell. I'm not entirely sure what else I can say/do at this moment. I believe there are some changes coming to 1.6 but I cannot confirm if this will be addressed as I simply do not know. 

The original bug report has been bumped numerous times by myself and other colleagues and I am confident that development are fully aware of the issue. 

People to mention this from time to time however it doesn't seem to be as often as it used to be so perhaps it has improved slightly over this time.

Share this post


Link to post
Share on other sites

Hi Chris,

 

I watched the Apple Keynote where Affinity Photo for iPad was demoed. It seemed to me that there was no lag at all. Granted, iOS and macOS have different event sources, but the event processing code should be ported easily to the Mac version of Affinity Photo. I may assume that the iOS and the macOS version share most of the graphic engine's code base?

 

I imagine the flow of event data to be like the following:

iOS:    [UIEvent] -translated-> [Affinity Pen State] -> [Pen State Processing] -> [Affinity Graphics Engine]
macOS:  [NSEvent] -translated-> [Affinity Pen State] -> [Pen State Processing] -> [Affinity Graphics Engine]

My guess is that the stage "Pen State Processing" is different in Affinity Photo for iOS and macOS.

 

Regards,

Pierre

Share this post


Link to post
Share on other sites

Hi Chris,

 

this issue seems to be resolved in version 1.6.6 of Affinity Photo. I am not able to replicate it anymore. :)

 

It took you quite some time but now I am very happy. I now can paint without having to adapt to the bugs of the tool in use. Great job! Affinity Photo > Ps! \o/

 

Cheers,

Pierre

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×