View Issue Details

IDProjectCategoryView StatusLast Update
0006659ardourfeaturespublic2015-12-13 07:56
Reporterdon3 Assigned To 
PrioritynormalSeveritytweakReproducibilityalways
Status newResolutionopen 
Product Version4.3 
Summary0006659: Mixer Trim knob: "Magnetic" zone around 0.0 dB seems a bit too large
DescriptionArdour version: 4.4.0, nightly 4.4.163

Fedora 21 + CCRMA
XFCE on VNC (current screen size 1280x1009)

The "magnetic" zone around 0.0 dB when dragging the Trim knob up or down in mixer strips seems a bit too large. If I left-click and drag up from the knob, the value doesn't start changing until I get near the top of the strip. It's far enough that I've thought dragging wasn't working on more than one occasion. Perhaps it's just me.
TagsNo tags attached.

Activities

x42

2015-10-30 16:55

administrator   ~0017551

The dead-zone at detent is 42 pixels times ui-scale (preference, default 1.0).

I guess the issues in your case is because the knob is near the top of the screen already, in that case, just drag right instead.

top/right -> increase
left/bottom -> decrease

Alternatively use the mouse-wheel (which skips the detent altogether)

don3

2015-10-30 17:18

reporter   ~0017553

Last edited: 2015-10-30 17:19

x42: Yes, it could be that I tended to "give up" on upward drags earlier than I might've otherwise because the knob is near the top. (I hadn't tried left/right - thanks for that.) But still the dead zone [ah, that was the term I was looking for!] on this seems a lot bigger than on other controls - seems as though it could be half that (maybe less) and still have plenty of detent feel. Maybe just me. :)

Preferemces > GUI > GUI and Font scaling is set at Default currently.

x42

2015-10-30 19:19

administrator   ~0017554

The only other knobs that have a detent is the gain and dim controls in the monitor section.
All other controls (faders etc) in ardour are completely linear.

the "42px" was determined empirically, the goal was to make zero reachable without having to be extra precise (slow down to disable mouse acceleration) with touchpads on many machines. It's a compromise. Personally I'd also favor a slightly smaller value although, I need to admit, 42 is a nice number :)

Like with scaling in general, we need a better way to detect a sensible default or make this configurable somehow.
Let's keep this bug report open, details like this currently just below our the radar, there will be further related updates for HiDPI support in the not too distant future.

Meanwhile, if you compile ardour yourself, you can change this in gtk2_ardour/ardour_knob.cc line 356

don3

2015-10-30 20:22

reporter   ~0017555

Ah okay. cool -- thanks for the explanation! How did I miss the significance of 42 ?? :-)

You just got me thinking about some of those other controls, like faders, panners, etc. Perhaps is would be nice if those had (small) detents as well. Or maybe something like "edge resistance" or "stickiness" would be better, so that it isn't impossible to hit other values close to the detent (+/- 0.1 on the faders, for example). The GUI scale value seems to work like that. Or magnetic with an option to override, like when using the "fine adjust" modifier. Just tossing out random ideas...

So far I've been using only binaries from ardour.org, but I've had a local clone of the Git repo for some time now. I've just been looking for some spare time to install the dependencies and build it locally, and start looking around in the code more deliberately (oh, and maybe finally learning C++). Thanks for the tip in any case!

chaot

2015-12-06 09:54

reporter   ~0017701

I also stumbled upon this and think 42 pixels (yes, yes, hard to argue that this value is wrong) is too much and should be decreased.

An aditional idea would be to only introduce the dead-zone after the 0dB (or whichever value the dead-zone resides around) has been left for the first time. So, if you want to change the trim then the button reacts instantly but it's still easy to hit the 0dB when returning.

I'm using a 13 inch full hd display by the way. That probably also changes how this issue is perceived.

x42

2015-12-06 10:24

administrator   ~0017703

mmh, I find 42px on a 12.5" 1920x1080 display too small and would like to increase it :)

x42

2015-12-06 10:36

administrator   ~0017704

Last edited: 2015-12-06 10:38

trying on different machines

  10" 1024x768, ui-zoom: 80% : I'd like a smaller value
  12.5" 1920x1080, ui-zoom: 125% : I'd like a larger value

I get the feeling we might need:

  px_deadzone = 42.f * ui_scale * ui_scale;

or a similar exponential relationship instead of the current linear: 42.f * ui_scale

don3

2015-12-07 02:05

reporter   ~0017708

Last edited: 2015-12-07 03:00

If you need another data point:

  VNC session of various resolutions (eg, 1820x1024) with viewer on 1920x1080 15" laptop, UI zoom: default : Dead zone is so big that I initially started to open a bug report to say that dragging up or down from zero didn't work at all.

Also wondering whether mouse resolution/gain/acceleration/whatever might play a role, as I tend to use faster settings than most people I know. (So maybe I tend to "give up" after a smaller movement, seeing no response.)
EDIT: Anyway, the dead zone looks quite large, even moving slowly...

I guess I'm implicitly comparing with detented controls provided by other tools, using the very same screen/mouse setup. Within Ardour sessions even -- LinuxDSP MBC2B plugin's GUI, for example, seems to have a much smaller dead zone.

Issue History

Date Modified Username Field Change
2015-10-30 16:36 don3 New Issue
2015-10-30 16:55 x42 Note Added: 0017551
2015-10-30 17:18 don3 Note Added: 0017553
2015-10-30 17:19 don3 Note Edited: 0017553
2015-10-30 19:19 x42 Note Added: 0017554
2015-10-30 20:22 don3 Note Added: 0017555
2015-12-06 09:54 chaot Note Added: 0017701
2015-12-06 10:24 x42 Note Added: 0017703
2015-12-06 10:36 x42 Note Added: 0017704
2015-12-06 10:38 x42 Note Edited: 0017704
2015-12-07 02:05 don3 Note Added: 0017708
2015-12-07 03:00 don3 Note Edited: 0017708