After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 683726 - Rectangle Select Tool Lag
Rectangle Select Tool Lag
Status: RESOLVED DUPLICATE of bug 663582
Product: GIMP
Classification: Other
Component: Tools
2.8.2
Other All
: Normal normal
: 2.8
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2012-09-10 14:04 UTC by Ludde
Modified: 2012-11-15 14:54 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ludde 2012-09-10 14:04:10 UTC
The rectangle select tool lags behind pretty bad when using a USB poll rate any higher then 125 reports/second.
125 is working fine.
Comment 1 Michael Schumacher 2012-09-10 14:19:05 UTC
Could this be a GTK+ problem?
Comment 2 Ludde 2012-09-10 14:53:54 UTC
(In reply to comment #1)
> Could this be a GTK+ problem?

I'm afraid that is beyond me Schumie. :)
I selected "Product: GIMP" because thats the closest i could get for now with my knowledge. ;)
Comment 3 Max Mustermann 2012-09-27 18:31:53 UTC
Thanks, Ludde, for reporting this. 
This bug sounds very similar to bug 645345, but it should have been fixed in GIMP 2.8.2. 
Jus to be certain: can you please try again with the current GIMP 2.8.2 you find at gimp-win.sourceforge.net? Are the symptoms the same as in bug 645345?
Your answer within the next 6 weeks is appreciated. Thank you.
Comment 4 Ludde 2012-09-28 11:02:13 UTC
You are welcome. :)

Yes it does and i bet he/she are using hardware that supports a USB poll rate higher then 125 and did not think about that at the time.
Using 125 is not a problem at all (this is not BF3 or Quake ;) so i'm just so happy to have found a solution for this.
When going any higher then 125, both rectangle and ellipse get choppy and i have tryed turning color management off.
I re-installed with the one from gimp-win.sourceforge.net as we speak and the problem is still there i'm afraid.

I am using a Logitech G500 with the newest official drivers.
Ivy Bridge 3570K
amd_catalyst_12.9_beta_dotnet4 drivers.

By the way, even at 125 and color management off, and now the rectangle tool works, pressing space and moving the image still gets stucky with digital distortions.
Ive seen people chat and relate that problem to the color management thingie, but i never did get any good results with that myself.
It was introduced when you added the single-window mode, sometime around there anyway.
so, no luck with that one, i was hoping this solved that too, but, nope. ;)
Comment 5 Max Mustermann 2012-11-12 19:02:52 UTC
You describe two problems here: 
1. Fuzzy distortions when panning the image: they are handled in bug #674928.
2. The lagging selection tools. If this doesn't match to bug #645345, we have to keep this bug open and have an eye on it, until somebody can fix it.
Comment 6 Ludde 2012-11-12 22:03:00 UTC
Roger that. :)

So, about the lagging of the selection tools..
I am now using Windows 8 64bit, new installation and a new mouse, Logitech G400 and the situation is identical as before and i can reproduce it in my sleep. :)
But, i do not haveto since i know that all i haveto do, is turn the polling rate down to 125 and only 125 and all is good and i dont need a higher polling rate for Gimp and i dont think anyone else need that either.

So I figured that this information alone was valuable since the solution is so simple but still very not so obvious for the user, though.
People that buy a "gaming-rate" mouse dont run at 125 by default i would say, and those kind of users are many.
So i mentioned it first in Gimp Chat since that thing ends up on a Google-search so the rest of the planet can find the solution, that my theory anyway. ;)

I also put a normal priority on the bug report since its solvable by the user.
But mm-yes, i guess the bug is still open then since its still around in your latest official build.
Comment 7 Michael Natterer 2012-11-12 23:20:58 UTC
But you use 2.8.2, not git, right? The frame rate is now limited for all
tools, no matter how you configure your mouse. I would guess this is
rather a duplicate of bug 663582.
Comment 8 Michael Natterer 2012-11-12 23:23:05 UTC
Yes, just watched the video again (comment 45 of bug 663582).

*** This bug has been marked as a duplicate of bug 663582 ***
Comment 9 Ludde 2012-11-13 01:01:10 UTC
Yes,
well, your official http://www.gimp.org/downloads/ 2.8.2 for Windows is the one im talking about within this bugreport.
But, i'm personally using the latest compiled one for Windows i can find atm, and that is a portable 2.8.3 32bit one, although im on Windows8 64bit.  
Source:
http://nightly.darkrefraction.com/gimp/
Latest (2012-11-12) 
And my bugreport still stands, even with that one. :P
Comment 10 Michael Natterer 2012-11-13 07:22:42 UTC
Sven, can you also reproduce this on the nightly builds?
Comment 11 Ludde 2012-11-13 19:28:17 UTC
The nightly from the darkfraction site yes, i can reproduce up to this date.
Latest test was minutes ago with the (2012-11-13) build.

I must say, when i use 125 reports per second, your official one sure feals much faster and responsive then the newest nightly builds im trying lately and im not sure i feel that is a good thing. 
Thats not a bugreport, just personal comment like - hey! thats the opposite improvement of what i was hoping for, wrong direction! :)

Anyway, if there is any specific finished compiled build for Windows you like me to test, then give me the link and i'll test it.
I do not know how to compile and all that.
Comment 12 Ludde 2012-11-13 20:38:45 UTC
Some "inofficial" blabla.. :)

I repeat, everything was OK/perfect before with the select tools as long as the mouse was set at 125.
The select tools acts and feels like a normal window in Windows on 125 with your official build, like it should.

With the latest builds i am trying it feels slow and tired on 125, and the rest you know, still there.
Now, that would leave me no option but to fall back to a build that was fast with 125 when im going to do personal Gimping since one option is slow, another is eum, a pain in the butt. :)
If this is a result of the new 60 limit if thats correct, then i for one am not happy about it. :P

Do i look nervous, does it show, really? ;)
Comment 13 Ludde 2012-11-15 05:56:45 UTC
I did some selection tool testing with some builds and i set the G400 at full 1000rps this time.
It will show that the problem is not at my end atleast and, where the bug showed up, kinda. :)

gimp-2.6.6-i686-setup = pass
gimp-2.6.7-i686-setup = pass
gimp-2.6.8-i686-setup = pass
gimp-2.6.9-i686-setup = pass
gimp-2.6.10-i686-setup = pass
gimp-2.6.11-i686-setup = pass
gimp-2.6.12-i686-setup-2 = pass
gimp-2.7.0-i686-setup (dev version) = pass

gimp-2.7.1-setup (dev version)
Select tool blinks and the faster you move the faster it blinks, so you wont even see the selection if you move normal > fast.
The cursor itself has no problem.

gimp-2.7.2 i could'nt find right now.

gimp-2.7.3-setup (dev version)
The bug for this bugreport shows up for the first time here.
 
Might as well do a few more, with no luck of course. :) 
gimp-2.7.4-setup (dev version)
gimp-2.7.5-setup (dev version)
gimp-2.8.0-rc1-setup
gimp-2.8.0-setup
gimp-2.8.2-setup-1
Comment 14 Michael Natterer 2012-11-15 08:28:47 UTC
Ludde, I don't know what GIMP version is provided by "portable" GIMP,
can you check the video (comment 45 of bug 663582) please? If this
looks like your problem, then the bug is fixed, the fix is just not
in any official release yet.

And thanks for the research about which version introduced the issue,
I guess 2.7.3 is the version that switched to cairo drawing.
Comment 15 Ludde 2012-11-15 12:58:48 UTC
O-ohh yes sir, thats the one, thank you.  :)
You are welcome and thank You guys, all of you, for what you doo.
Bye for this time devs, over and out. :)

//Ludde
Comment 16 Michael Natterer 2012-11-15 14:54:21 UTC
Thanks for checking Ludde, resolving as duplicate again :)

*** This bug has been marked as a duplicate of bug 663582 ***