Bug 395494 - The new blur effect should be applied faster
Summary: The new blur effect should be applied faster
Status: RESOLVED DUPLICATE of bug 391819
Alias: None
Product: kwin
Classification: Plasma
Component: effects-various (show other bugs)
Version: 5.13.0
Platform: Other Linux
: NOR minor
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-16 15:26 UTC by Filip Fila
Modified: 2018-06-16 16:01 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Filip Fila 2018-06-16 15:26:28 UTC
Issue: When moving a transparent window for somewhat of a larger distance, the new blur effect needs a small, but noticeable amount of time to actually apply the blur.

This is nothing major, but it is distracting ie. my eye will always notice the blurring taking place in front of me. This is especially a problem if the background image has sharp details in it, such as text e.g. The contrast between the sharp details and the blurred ones is too strong. Also, there is a noticeable difference between how the blur works when moving a transparent window just a little bit or for a larger distance. 

I've made a video which demonstrates this difference: https://youtu.be/cNMyTHIZZXk

Although it is actually a bit worse in a real environment because the video quality is not 100%, you can clearly see in the first portion of the video that when a window is moved to its new position it takes a bit of time for the blur to kick in. In the second part of the video the background is already nicely blurred when the window is placed in its new position.

If technically possible, it would be great if the blur could be applied faster or if it could actually at least be applied gradually instead of going from 0 to 100. 

____

KWin Version: 5.13.0
KDE Plasma Version: 5.13.0
KDE Frameworks Version: 5.47.0
Qt Version: 5.11.0
OS: Manjaro Linux
Comment 1 Vlad Zahorodnii 2018-06-16 15:38:27 UTC
Blur effect doesn't blur behind transformed windows (wobbly windows effect transforms/deformates windows). That's because blur effect operates on rectangular regions.

*** This bug has been marked as a duplicate of bug 391819 ***
Comment 2 Filip Fila 2018-06-16 15:48:53 UTC
(In reply to Vlad Zagorodniy from comment #1)
> Blur effect doesn't blur behind transformed windows (wobbly windows effect
> transforms/deformates windows). That's because blur effect operates on
> rectangular regions.
> 
> *** This bug has been marked as a duplicate of bug 391819 ***


You're absolutely correct, this happens because of Wobbly Windows. However, when I was using the old blur and forced it everywhere with Kvantum  it didn't have this issue IIRC, it blurred instantly. But that might be because the blurring method was very different?

Could a workaround be possibly made that detects if a user has Wobbly Windows on and then implements the gradual blurring that the new screen locker has? Although this may open other problems, of course.
Comment 3 Vlad Zahorodnii 2018-06-16 15:53:34 UTC
(In reply to Filip from comment #2)
> You're absolutely correct, this happens because of Wobbly Windows. However,
> when I was using the old blur and forced it everywhere with Kvantum  it
> didn't have this issue IIRC, it blurred instantly. But that might be because
> the blurring method was very different?
> 
> Could a workaround be possibly made that detects if a user has Wobbly
> Windows on and then implements the gradual blurring that the new screen
> locker has? Although this may open other problems, of course.

That would still produce visual problems. See https://bugs.kde.org/show_bug.cgi?id=391819#c8
Comment 4 Filip Fila 2018-06-16 16:01:48 UTC
(In reply to Vlad Zagorodniy from comment #3)
> (In reply to Filip from comment #2)
> > You're absolutely correct, this happens because of Wobbly Windows. However,
> > when I was using the old blur and forced it everywhere with Kvantum  it
> > didn't have this issue IIRC, it blurred instantly. But that might be because
> > the blurring method was very different?
> > 
> > Could a workaround be possibly made that detects if a user has Wobbly
> > Windows on and then implements the gradual blurring that the new screen
> > locker has? Although this may open other problems, of course.
> 
> That would still produce visual problems. See
> https://bugs.kde.org/show_bug.cgi?id=391819#c8

Ah, that's pretty bad, yes. I was just trying to think of ways to speed up the blurring once the window is put into position or to at least alleviate the transition somehow, but maybe it's impossible. Thank you for looking into this regardless of that and for your quick reply.