<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'><div dir='ltr'>
> From: fons@linuxaudio.org<br><div>> To: linux-audio-dev@lists.linuxaudio.org<br>> Subject: Re: [LAD] sliders/fans<br>> <br>> On Thu, Nov 24, 2011 at 02:21:25PM -0500, David Robillard wrote:<br>> Suppose the minimum value of the widget would correspond to say<br>> -100 dB if not handled specially. If you just have a single fader<br>> per channel, you could arrange for the model or the DSP code to<br>> translate that to 'off'. That is no longer the case if you have<br>> 'VCA' faders.<br>> <br>> There are two thing you'd expect from such a system: <br>> <br>> * If either the channel or the group fader is at minimum, then<br>> the channel must be off (zero gain).<br>> <br>> * If the channel fader is at -50 dB, and the group at -60 dB<br>> you don't want zero gain, but -110 dB. Becaus either fader is<br>> still in a position where you'd expect that moving it makes a<br>> difference.<br><br>Wow. Isn't this a far bigger topic?<br><br>For example, having a user interface definition that says UpArrow<br>means the controller moves up is separate from saying:<br><br>a. UpArrow and gain implies dB values<br>b. UpArros and Frequency control implies lin/log/exp Hz values<br><br>If we want to impose semantics on the controllers that are under motion <br>then that is going to be one _big_ specification. Again, perhaps I need to<br>look at the HID definition we are referring too, I was actually anticipating<br>just the syntax of what the diverse key/mouse combinations cause rather<br>than what they effect.<br><br>There are some interfaces that expect fixed pixel steps for their controls,<br>the interfaces are not 'resizable'. Others are. I think it might be difficult <br>to impose semantic meaning of any given chance in the interface guide<br>for that and probably a few other reasons.<br><br>Comments?<br><br>nick<br></div> </div></body>
</html>