Clunky mouse when trying to change value settings (in effects and elsewheree)

Realtime rendering, there is a chance your system is just lagging. The newer applications are programmed to take up a lot more processing power. On my laptop is smooth as butter, i7 16gb ram nvme ssd. On my PC much older system, it's laggy, 980ti i7 860 16gb ram. et. What are you computer specs, that's important to note here for this problem.

To add to my last post, just changing the polling rate did not sadly resolve the issue - the problem seemed to be with the switch on the mouse itself - supposedly a common issue with the Naga. If anyone is having this issue I'd recommend doing a mouse test online and seeing if when dragging the mouse button flickers on and off. This will not affect most windows usage, but Adobe does. Ended up returning the mouse and getting another to resolve the issue.

https://www.youtube.com/watch?v=M9968_Ha-OE

Someone else found the same thing, but I've been having this issue recently with a new Razer Naga - was absolutely doing my head in with it not clicking a dragging correctly. Changing the polling rate down from 1000hz alleviated the issue, so anyone using gaming mice will want to check that.

I experimented with my mouse a bit, and it looks like the source of the issue is your mouse's polling rate.

You see, I have a Logitech G-whatever mouse and despite the pain in the ass the Logitech G hub is giving me 95% of the time, I can at least set the mouse's polling rate on it. Polling rate is measured in Hz and can vary from 125Hz to over 1000Hz depending on the brand and model of the mouse in question. Looks like Adobe can't keep up with 1 ms response time.

I set mine to 125Hz and the 'click and drag' feature worked as it should. So if you have a mouse with interchangable polling rate, try to change it to a lower value, see if it fixes anything. It worked for me.

On version 2023 and still with this problem.... the only thing that worked but it's not exactly a fix.. was to set the dpi of the mouse with the mouse software to the lowest.. and then the windows sensitivity to max. Now my mouse feels a bit unconfortable but premiere works finally. 

@MHoeckerand @jack5E5F thanks for your answers, it really works!

In my case it was just fine to raise mouse sensivity in Windows settings from 5/10 to 6/10.

And lowering mouse DPI from 800 to 500 to keep the same speed.

Now it catchs even super small movements since I start moving my mouse.

For anyone finding this in 2021.

I searched for weeks. Two options (No other "odobe advice" works anyway)

1. If you set your windows mouse setting dpi way up, this fixes it, but then you have a mouse pointer that is clunky. (happens when you have to set the mouse itself back to 100 dpi to compinsate for the windows mouse dpi settings that is way up)

2. Easy way, without doing any settings. Flick your mouse to the right/left fast, way over what is normal. It then becomes "alive/wakes up" and then set it as it is now *functioning.

This is clearly an ADOBE FUALTY MOUSE DPI BUG thing that needs to be patched in the software.

Hope this helps someone out there. Take care

It's 2020 and  I found myself having the same problem.  What I found out from some other posts is that it has something to do with Windows mouse speed (sensitivity) settings and a multi resolution mouse.  I had my mouse at highest sensitivy (using the adjustment buttons on the mouse itself) and Windows' speed/sensitivity all the way down.  This changed the way that Premiere recognized the mouse's movements.

As Premiere is one of my primary tools, this had to work so I set the speed of my mouse to max in Window's settings, and then adjusted sensitivity back down using the buttons on the mouse itself, and this seems to work just fine for me.

I will say that Premiere should probably update to recognize the mouse movement and speed regardless of what settings are in Windows.  If it moves a certain (small) distance in screen space, it should adjust the value.

I booted up Premiere for the first time in a few weeks and I have the same problem now. It worked fine earlier this month. Did you ever find a fix? I updated to the most current version hoping it would resolve the issue but no luck. I don't know how a full-time, professional editor deals with this stuff, under pressure, under deadlines, "oops, my NLE is broken again. Guess I'll spend a few hours online asking fellow users how to fix it or submit a bug report and keep my fingers crossed." I guess they probably use Avid.