[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

[Chris Jones]

https://bugs.kde.org/show_bug.cgi?id=370237

--- Comment #18 from Chris Jones  ---
I can't notice the delay on the Surface Pro 4 now though.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

[Chris Jones]

https://bugs.kde.org/show_bug.cgi?id=370237

--- Comment #17 from Chris Jones  ---
(In reply to Bollebib from comment #16)
> @chrisjones 
> 
> incidently is it possible this issue occurs after using undo?

It happens regardless of whether there has been any undo.

Also I noticed it starts happening less than a second after the initial stroke
now (instead of the 1.5 seconds originally reported), and can occur any time
after that stroke.  Usually I get immediate strokes as long as they're within
around half a second of the previous one.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

[Bollebib]

https://bugs.kde.org/show_bug.cgi?id=370237

--- Comment #16 from Bollebib  ---
@chrisjones 

incidently is it possible this issue occurs after using undo?

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=370237

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

--- Comment #15 from Bug Janitor Service  ---
Thanks for your comment!

Automatically switching the status of this bug to REPORTED so that the KDE team
knows that the bug is ready to get confirmed.

In the future you may also do this yourself when providing needed information.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

[Chris Jones]

https://bugs.kde.org/show_bug.cgi?id=370237

--- Comment #14 from Chris Jones  ---
(In reply to Tymond from comment #13)
> .

I think this might be a different issue, since the pauses only occur at the
start of new strokes rather than mid-stroke.  Also it happens regardless of the
amount of RAM that's being used.

Incidentally I still have this problem in 4.3.0.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

[Tymond]

https://bugs.kde.org/show_bug.cgi?id=370237

Tymond  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #13 from Tymond  ---
.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

[Tymond]

https://bugs.kde.org/show_bug.cgi?id=370237

Tymond  changed:

   What|Removed |Added

 CC||tamtamy.tym...@gmail.com

--- Comment #12 from Tymond  ---
@Chris Jones, does bug 421376 sound similar? Do you think it's the same issue?

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

[Chris Jones]

https://bugs.kde.org/show_bug.cgi?id=370237

Chris Jones  changed:

   What|Removed |Added

 Status|RESOLVED|REPORTED
 Resolution|WORKSFORME  |---

--- Comment #11 from Chris Jones  ---
Requested info was provided in Comment 8.

Revisiting this issue in Krita 4.2.0, I find that on the desktop the latency is
at its worst when strokes are spaced apart by about 1 second, whereas it is
more sporadic and less frequent on the SP4.

Also I tested a more recent GPU (GTX 660) in the desktop, and the issue was not
improved at all.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

[Andrew Crouthamel]

https://bugs.kde.org/show_bug.cgi?id=370237

Andrew Crouthamel  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #10 from Andrew Crouthamel  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The
bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki
located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

[Andrew Crouthamel]

https://bugs.kde.org/show_bug.cgi?id=370237

Andrew Crouthamel  changed:

   What|Removed |Added

   Keywords||triaged

--- Comment #9 from Andrew Crouthamel  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days.
Please provide the requested information as soon as possible and set the bug
status as REPORTED. Due to regular bug tracker maintenance, if the bug is still
in NEEDSINFO status with no change in 30 days, the bug will be closed as
RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki
located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug
status as REPORTED so that the KDE team knows that the bug is ready to be
confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

[Chris Jones]

https://bugs.kde.org/show_bug.cgi?id=370237

--- Comment #8 from Chris Jones  ---
Desktop: With OpenGL the problem is less pronounced than it used to be; the
strokes are drawn in small chunks instead of fluidly with a timing of roughly
0.7 seconds between strokes, gets slightly worse as the timing is increased,
and goes back to being fluid at around 1.5 seconds between strokes.  Angle
gives very similar results.  With CPU rendering, strokes are drawn in a
consistently choppy fashion regardless of the timing between strokes.

Surface Pro 4: OpenGL and Angle both behave like CPU rendering does on the
desktop (i.e. a bit choppy), and it doesn't look like changing timing between
strokes is having any adverse affect.  CPU rendering is consistently fluid no
matter the timing.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

[Boudewijn Rempt]

https://bugs.kde.org/show_bug.cgi?id=370237

Boudewijn Rempt  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #7 from Boudewijn Rempt  ---
Does it matter whether opengl or angle are enabled, or when cpu rendering is
used?

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

[Isabelle LaBrot]

https://bugs.kde.org/show_bug.cgi?id=370237

Isabelle LaBrot  changed:

   What|Removed |Added

 CC||stinkyfishli...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

[Chris Jones via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370237

--- Comment #6 from Chris Jones  ---
I forgot to add that this problem resurfaced in the first 3.1 beta (3.0.99.90),
so I'm still using 3.0-9e17aff since that's the most recent build that doesn't
exhibit the problem.  I don't recall when it initially cropped up (it might
have been in the switch from 2.9 to 3.0) and then was subsequently fixed, but
I'll try and locate those versions if that would help in tracking down the
issue.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

[Chris Jones via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370237

--- Comment #5 from Chris Jones  ---
No stabilizer, only basic smoothing is on, although none of the smoothing
options seem to make any difference.  Also I haven't been able to repeat the
Advanced Colour Selector incident so far.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

[Bollebib via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370237

Bollebib  changed:

   What|Removed |Added

 CC||kwadraatn...@hotmail.com

--- Comment #4 from Bollebib  ---
you don't have stabilizer or another smooth option active per mistake?

I would assume not,as advanced color selector has nothing to do with that,but
it might be something to eleminate first,and be absolutely sure

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

[Boudewijn Rempt via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370237

--- Comment #3 from Boudewijn Rempt  ---
Yes... Though it's still strange that this doesn't happen to me, but it
suggests a place to start looking.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

[Chris Jones via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370237

--- Comment #2 from Chris Jones  ---
Happens whether it's enabled or not.

Strangely, I just opened the Advanced Colour Selector docker, and the problem
went away until I closed it again.  I tried opening it again and the problem
was still there though, so I'm not sure what that was about.  Does that offer
any clues?

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 370237] Strokes are delayed ~1.5 seconds after the previous stroke

[Boudewijn Rempt via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370237

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org

--- Comment #1 from Boudewijn Rempt  ---
Does this also happen with instant preview enabled or disabled?

-- 
You are receiving this mail because:
You are watching all bug changes.