Erratic pot behavior

[Ataraxia2320]

Hey I did a quick search and only found posts in relation to my problem but I found nothing helpful.

All my knobs in reaper are behaving very erratically. When I try to pan for example the value jumps around instead of moving smoothly, making it almost impossible to pan anywhere but 100% or center.

This has been a problem for me since I updated my computer to Windows 10. I am using a mouse for my input primarily, but the problem also persists when I use my laptop's touch pad. Furthermore I have also tried using other mice, but to no avail.

Has this happened to anyone else? Does anyone have any ideas?

[ReaperMadness]

Oh... I thought you were talking about something else.

[Tommy V]

Originally Posted by ReaperMadness

Oh... I thought you were talking about something else.

That's funny ... considering your nickname here

[clepsydrae]

Shot in the dark: do you have an UI scaling enabled in windows?

You might post a licecap of what's happening so we can get an idea.

Try a fresh portable install and let us know what happens.

You're using the latest version of reaper, yeah?

[Gerry P]

Originally Posted by Ataraxia2320

All my knobs in reaper are behaving very erratically. When I try to pan for example the value jumps around instead of moving smoothly, making it almost impossible to pan anywhere but 100% or center.

see if this helps

http://forum.cockos.com/showpost.php...2&postcount=61

[Ataraxia2320]

Originally Posted by Gerry P

see if this helps

http://forum.cockos.com/showpost.php...2&postcount=61

Yup, this works, but at 100% I can't read anything on my computer.

Has anyone reported this to the bug fixes section?

[Ataraxia2320]

When Windows 10 is at 125% scaling(which is default I believe, at least my laptop says it is the recommended setting) all pot knobs are impossible to set correctly.

This can be fixed when you reduce scaling to 100%, but this makes all text elsewhere on my computer cramped and unreadable.

I'm sure that a lot of windows 10 users are also affected by this so I would fudging love it if you guys could get around to fixing this in future installments.

Cheers.