Knobs not working correctly on high-DPI devices? (FIXED)

[loneboat]

I'm considering jumping from FL Studio to Reaper, so I downloaded the trial, and was disappointed within the first 2 minutes. Whenever I try to adjust a knob even a tiny bit, the knob goes crazy and jumps all over the place, making it completely unusable. :-( I'm seeing the same behavior with my touchpad, wired mouse, bluetooth mouse, etc...

I'm not ready to give up on Reaper over something so random though. Everything else in it looks great! I did some searching here, and I found two threads which seem to discuss similar issues:

http://forum.cockos.com/archive/index.php/t-128587.html

http://forum.cockos.com/archive/index.php/t-129686.html

From reading these, I'm getting the impression it is because I'm using a high-dpi device (I'm on a Microsoft Surface Pro 3). The suggested workaround of changing my OS DPI settings does seem to fix the issue, but (1) doing so makes all the UI elements really tiny, and (2) having to do this every time I want to fire up Reaper will not work with my workflow - it would drive me nuts.

I did see several people in those threads mention that "the Windows8.1-64 update" fixed the issue, but I'm running the latest x64 download from Reaper's home page, which I'm assuming has all the latest updates included (my "About" dialog reports I'm running v5.04/x64). Are there separate updates I have to find and apply? Both of the threads I linked to from above are from 2013, so I'm guessing any bugfixes they mentioned have been included in the main download for a while.

Anyone else on a high-DPI device seeing similar issues?

[Allasseon]

Hi,
I have the same problem. I have disabled high DPI scaling only for Reaper (right-click on the Reaper-icon, Compatibility-tab, check "Disable display scaling on high DPI settings"). This still leaves Reaper UI elements tiny but at least you don't have to change your system settings every time before you start Reaper. And the knobs work as they should (at least they do for me).

[loneboat]

Originally Posted by Allasseon

Hi,
I have the same problem. I have disabled high DPI scaling only for Reaper (right-click on the Reaper-icon, Compatibility-tab, check "Disable display scaling on high DPI settings"). This still leaves Reaper UI elements tiny but at least you don't have to change your system settings every time before you start Reaper. And the knobs work as they should (at least they do for me).

Thanks for the suggestion! I'll give that a shot.

Still a disappointing way to start off my adoption of Reaper. It's not like this is some weird corner-case bug - I can't use one of the main GUI elements without crippling the UI with a tiny interface... :-\

[MikComposer]

Same problem! It also happens when I'm using vst plugins with knobs like Glitch!

I'm on Win 10 and in 1080 res.

[Birgit]

I'm on Win 8.1 and got the same problem.

Here are my 2 cents to this. I encountered this bug on NI Maschine too.
Disabling high DPI scaling is not a solution for me because all VST GUIs would become very tiny too.

My workaround is to turn knobs using the mouse-wheel. This works for all knobs except that one in the track panel for the envelope automation lines. So I use a theme that has a fader here.

Generally you can use a theme with no knobs like the Classic_1.x that comes with the Reaper installation.

[shannow777]

I have the same problem as well. Pan knobs will not work correctly at all.

Im running a 4k monitor with 3840x2160 res. Reaper looks absolutely amazing. Crystal clean lines and just a joy to look at but Pan knobs are killing it.

I have had to search for themes that use a pan slider which works without a problem but that limits you to a small amount of possible themes.

It's very frustrating because from what I have seen, all the best themes use Knobs.

I have had the same problem with other software. It's all to do with the text/icon/apps magnification options in Windows. It recommends %150 which in truth is the only viable option as everything becomes to small to see otherwise.

I really think this needs to be addressed because monitor resolutions are getting bigger, not smaller.

I want to use the stock reaper theme but with the current pan knob glitch, It is just not going to happen.

[ELP]

I really cant understand people who buy such an named High DPI Monitor, if at the end the User has to scale everything bigger, because everything is now to small on screen .

Higher DPI needs fitting really big screens..! For me, everything under 48" is to small for 4k
-refers to text, GUI, desktop,...

otherwise with scaling you see not more on desktop and without you can read text
only with one ultra magnifier.

[xanthos84]

same issue here,
win 10 - 4k monitor, pan/volume knobs and sliders behave weird.

compatibility mode setting is a no go as everything will shrink to unreadability!

[Birgit]

Originally Posted by xanthos84

same issue here,
win 10 - 4k monitor, pan/volume knobs and sliders behave weird.

compatibility mode setting is a no go as everything will shrink to unreadability!

using the mouse wheel is the only possible workaround I found for this bug.

[xanthos84]

Originally Posted by Birgit

using the mouse wheel is the only possible workaround I found for this bug.

will not work on every theme with some different sliders/knobs....

[Tl-Aem]

same issue!

W10 - 4K

with 125%DPI or 150%DPI, trying to moving pan knobs stuck the whole system.

Work perfet with 100%DPI, but it's very too small to work with.

Any fix soon?

Reaper v5.29/x64.

Mouse wheel doesn't work on my system

[MT_]

Originally Posted by ELP

I really cant understand people who buy such an named High DPI Monitor, if at the end the User has to scale everything bigger, because everything is now to small on screen .

At OS-level zoom of 200%, effective resolution of 4K display is Full HD, just text and GUI elements in DPI-aware applications are much smoother and sharper.

[bgrg]

Same problem here, is there a workaround yet? I set the Windows GUI at 150%.

I've upgraded to 4K mostly because I really needed the extra screen space for the more complicated mixes in Reaper, it's disappointing that the knobs are broken...

[Justin]

Working on a fix now, I'm pretty sure this is a bug in win10's SetCursorPos() implementation for non-DPI-aware apps.

[ivansc]

Originally Posted by Justin

Working on a fix now, I'm pretty sure this is a bug in win10's SetCursorPos() implementation for non-DPI-aware apps.

Any chance the fix might be, or lead to reaper becoming dpi-aware?

[bgrg]

Originally Posted by Justin

Working on a fix now, I'm pretty sure this is a bug in win10's SetCursorPos() implementation for non-DPI-aware apps.

Thanks for the reply, it's great news!

[Justin]

Originally Posted by ivansc

Any chance the fix might be, or lead to reaper becoming dpi-aware?

Unrelated

[ivansc]

Originally Posted by Justin

Unrelated

I know - we have an expression in the UK: I was "chancing my arm" a bit.
Happy new year, btw.

[Justin]

If you all want to test a fix, there is a 5.32pre9 in the prerelease forum ...

[bgrg]

Originally Posted by Justin

If you all want to test a fix, there is a 5.32pre9 in the prerelease forum ...

So far the fix and everything is working, thank you!

[musicbynumbers]

Any chance this could also lead to a fix for absolute devices like touchscreens or pen input devices (including the pen on the surface pro 3)?

It acts in a non linear way right now when moving a pan knob up or down.

[Justin]

Originally Posted by musicbynumbers

Any chance this could also lead to a fix for absolute devices like touchscreens or pen input devices (including the pen on the surface pro 3)?

It acts in a non linear way right now when moving a pan knob up or down.

hmm might need to add an option for these... lemme look into it

[AHarker]

Justin - I'm running into this problem myself in an iPlug VST on windows - any chance you'd be able to share the workaround to the bug? I'm using ClientToScreen() and SetCursorPos() and it's working under win 7, but some win 10 users are reporting issues.

Thanks