Re: [LAD] sliders/fans

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: <d@...>
Cc: <linux-audio-dev@...>
Date: Thursday, November 24, 2011 - 8:31 pm

--_34be1a53-15ad-4275-9de0-db44c711d109_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

> From: d@drobilla.net

Pretty sure they can all emulate with dual button click.

> > >=20

th=20
a=20
ing
n

There are some implementation issues here though which might mean the
pragmatic approach is to not specify the actual stepped values as long as
the model is adhered to.

For example=2C bristol goes from 0.0 to 1.0 and the graphic is just a visib=
le
representation of the value. Other libraries might work with pixel steps
so isn't there an issue where the whole issue of what acceleration given=20
by 'Shift' becomes a little subjective? I suggested we might advise on what
the step should be but that might be incorrect. If the interface definition
just suggests that accelerated motion is given by ''"
then an implementation can confirm just by given the acceleration=2C the=20
actual values depend on the app?

> There's also the acceleration/slow factors for mouse control=2C which

y
h

Perhaps I need to have a look at the HID documents you were referring
to=2C the next step is probably to make some proposals and see how many=20
people agree/object to the suggestions?

Regards=2C nick.
=

--_34be1a53-15ad-4275-9de0-db44c711d109_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

&gt=3B From: d@drobilla.net&gt=3B To: nickycopeland@hotmail.com&gt=3B That said=2C some laptops don't have middle buttons...Prett=
y sure they can all emulate with dual button click.&gt=3B &gt=3B &g=
t=3B &gt=3B &gt=3B &gt=3B This would have to be defined in relation to =
the underlying unit the&gt=3B &gt=3B &gt=3B controller is for=2C to add=
ress the quantisation issues Fons has&gt=3B &gt=3B &gt=3B mentioned=2C =
or at least worded in a more generic way.&gt=3B &gt=3B &gt=3B &gt=
=3B Personally I don't think the underlying unit should define the steps wi=
th &gt=3B &gt=3B Control/Shift: I viewed them as going min to max in a =
given number of&gt=3B &gt=3B keypress/repeats irrespective of the quant=
isation. If it is not done as a &gt=3B &gt=3B fraction of the full thro=
w of a control then it might just end up as being&gt=3B &gt=3B another =
arbitrary set of definitions?&gt=3B &gt=3B I see. Yes=2C that's pr=
obably fine. I was wrong about units/quantisation&gt=3B here (see belo=
w).There are some implementation issues here though which might mea=
n thepragmatic approach is to not specify the actual stepped values as =
long asthe model is adhered to.For example=2C bristol goes from=
0.0 to 1.0 and the graphic is just a visiblerepresentation of the valu=
e. Other libraries might work with pixel stepsso isn't there an issue w=
here the whole issue of what acceleration given by 'Shift' becomes a li=
ttle subjective? I suggested we might advise on whatthe step should be =
but that might be incorrect. If the interface definitionjust suggests t=
hat accelerated motion is given by ''&lt=3BSome_Key&gt=3B&lt=3BArrow_Up&gt=
=3B"then an implementation can confirm just by given the acceleration=
=2C the actual values depend on the app?&gt=3B There's also the=
acceleration/slow factors for mouse control=2C which&gt=3B can't be de=
fined this way.&gt=3B &gt=3B &gt=3B &gt=3B &gt=3B Most of the keybo=
ard accelerators I use are based on U/D/L/R Arrow&gt=3B &gt=3B &gt=3B &=
gt=3B and H/J/K/L 'vi' style controls. &gt=3B &gt=3B &gt=3B &gt=3B =
&gt=3B &gt=3B &gt=3B &gt=3B I have no objection to changing them especially=
if it is a generally&gt=3B &gt=3B &gt=3B &gt=3B agreed&gt=3B &gt=
=3B &gt=3B &gt=3B set of changes and a coherent proposal.&gt=3B &gt=3B =
&gt=3B &gt=3B &gt=3B &gt=3B A good attitude to have :)&gt=3B &gt=3B=
&gt=3B &gt=3B &gt=3B &gt=3B &gt=3B There are diverse other issues that=
might need to be considered such&gt=3B &gt=3B &gt=3B &gt=3B as&gt=
=3B &gt=3B &gt=3B &gt=3B how to handle lin vs log controls?&gt=3B &gt=
=3B &gt=3B &gt=3B &gt=3B &gt=3B &gt=3B Glad you said that. I prefer=
the GUI to have equal steps. The backend &gt=3B &gt=3B needs to decide=
if they have to be lin/log.&gt=3B &gt=3B Agreed. Everything here =
is about the *view*. How that maps to actual&gt=3B parameter values is=
an underlying model issue.&gt=3B &gt=3B The view is is inherently =
always in pixels=2C which are inherently never&gt=3B quantized to whate=
ver unit you want. It mustn't be confused with the&gt=3B underlying mo=
del=2C which is where things like unit quantization and&gt=3B linear/lo=
g mapping happen.Perhaps I need to have a look at the HID documents=
you were referringto=2C the next step is probably to make some proposa=
ls and see how many people agree/object to the suggestions?Rega=
rds=2C nick.
=

--_34be1a53-15ad-4275-9de0-db44c711d109_--

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [LAD] "bleeding edge html5" has interesting Audio APIs, David Robillard, (Mon Nov 21, 6:40 pm)
Re: [LAD] "bleeding edge html5" has interesting Audio APIs, David Robillard, (Mon Nov 21, 7:19 pm)
Re: [LAD] "bleeding edge html5" has interesting Audio APIs, David Robillard, (Mon Nov 21, 7:49 pm)
Re: [LAD] "bleeding edge html5" has interesting Audio APIs, Rui Nuno Capela, (Mon Nov 21, 9:55 pm)
Re: [LAD] "bleeding edge html5" has interesting Audio APIs, David Robillard, (Mon Nov 21, 10:03 pm)
Re: [LAD] "bleeding edge html5" has interesting Audio APIs, Patrick Shirkey, (Mon Nov 21, 11:46 pm)
Re: [LAD] "bleeding edge html5" has interesting Audio APIs, Nick Copeland, (Mon Nov 21, 10:42 pm)
Re: [LAD] "bleeding edge html5" has interesting Audio APIs, David Robillard, (Mon Nov 21, 11:33 pm)
Re: [LAD] "bleeding edge html5" has interesting Audio APIs, Gordon JC Pearce, (Mon Nov 21, 11:37 pm)
Re: [LAD] "bleeding edge html5" has interesting Audio APIs, Fons Adriaensen, (Mon Nov 21, 10:58 pm)
Re: [LAD] "bleeding edge html5" has interesting Audio APIs, David Robillard, (Mon Nov 21, 11:33 pm)
Re: [LAD] "bleeding edge html5" has interesting Audio APIs, Alexandre Prokoudine, (Tue Nov 22, 11:33 am)
Re: [LAD] "bleeding edge html5" has interesting Audio APIs, Fons Adriaensen, (Tue Nov 22, 1:54 pm)
Re: [LAD] "bleeding edge html5" has interesting Audio APIs, Fons Adriaensen, (Tue Nov 22, 3:03 pm)
Re: [LAD] "bleeding edge html5" has interesting Audio APIs, Fons Adriaensen, (Tue Nov 22, 3:32 pm)
Re: [LAD] "bleeding edge html5" has interesting Audio APIs, Alexandre Prokoudine, (Tue Nov 22, 1:59 pm)
Re: [LAD] "bleeding edge html5" has interesting Audio APIs, Fons Adriaensen, (Tue Nov 22, 2:54 pm)
Re: [LAD] sliders/fans, James Morris, (Tue Nov 22, 12:05 pm)
Re: [LAD] sliders/fans, Alexandre Prokoudine, (Tue Nov 22, 2:58 pm)
Re: [LAD] sliders/fans, Paul Davis, (Tue Nov 22, 2:26 pm)
Re: [LAD] sliders/fans, hermann, (Tue Nov 22, 2:41 pm)
Re: [LAD] sliders/fans, David Robillard, (Thu Nov 24, 6:23 pm)
Re: [LAD] sliders/fans, Nick Copeland, (Thu Nov 24, 9:30 pm)
Re: [LAD] sliders/fans, David Robillard, (Thu Nov 24, 11:59 pm)
Re: [LAD] sliders/fans, Nick Copeland, (Thu Nov 24, 6:37 pm)
Re: [LAD] sliders/fans, David Robillard, (Thu Nov 24, 6:55 pm)
Re: [LAD] sliders/fans, Nick Copeland, (Thu Nov 24, 7:02 pm)
Re: [LAD] sliders/fans, David Robillard, (Thu Nov 24, 7:21 pm)
Re: [LAD] sliders/fans, Fons Adriaensen, (Thu Nov 24, 8:45 pm)
Re: [LAD] sliders/fans, David Robillard, (Thu Nov 24, 11:52 pm)
Re: [LAD] sliders/fans, Fons Adriaensen, (Fri Nov 25, 10:53 am)
Re: [LAD] sliders/fans, Nick Copeland, (Fri Nov 25, 8:52 am)
Re: [LAD] sliders/fans, Fons Adriaensen, (Fri Nov 25, 10:29 am)
Re: [LAD] sliders/fans, Jeff Koftinoff, (Thu Nov 24, 11:12 pm)
Re: [LAD] sliders/fans (again), Fons Adriaensen, (Thu Nov 24, 11:42 pm)
Re: [LAD] sliders/fans, Fons Adriaensen, (Thu Nov 24, 11:20 pm)
Re: [LAD] sliders/fans, Nick Copeland, (Thu Nov 24, 9:03 pm)
Re: [LAD] sliders/fans, Fons Adriaensen, (Thu Nov 24, 9:24 pm)
Re: [LAD] sliders/fans, hermann, (Thu Nov 24, 8:31 pm)
Re: [LAD] sliders/fans, David Robillard, (Thu Nov 24, 11:57 pm)
Re: [LAD] sliders/fans, hermann, (Fri Nov 25, 4:06 am)
Re: [LAD] sliders/fans, David Robillard, (Wed Dec 7, 7:28 pm)
Re: [LAD] sliders/fans, Paul Davis, (Wed Dec 7, 7:32 pm)
Re: [LAD] sliders/fans, Neil C Smith, (Wed Dec 7, 7:39 pm)
Re: [LAD] sliders/fans, Paul Davis, (Wed Dec 7, 7:43 pm)
Re: [LAD] sliders/fans, David Robillard, (Wed Dec 7, 8:03 pm)
Re: [LAD] sliders/fans, Thorsten Wilms, (Thu Dec 8, 9:44 am)
Re: [LAD] sliders/fans, Paul Davis, (Wed Dec 7, 10:33 pm)
Re: [LAD] sliders/fans, David Robillard, (Thu Dec 8, 12:40 am)
Re: [LAD] sliders/fans, Nick Copeland, (Thu Dec 8, 5:23 am)
Re: [LAD] sliders/fans, David Robillard, (Fri Dec 9, 7:10 pm)
Re: [LAD] sliders/fans, Nick Copeland, (Fri Nov 25, 8:40 am)
Re: [LAD] sliders/fans, Philipp √úberbacher, (Thu Nov 24, 10:17 pm)
Re: [LAD] sliders/fans, Fons Adriaensen, (Thu Nov 24, 8:57 pm)
Re: [LAD] sliders/fans, Nick Copeland, (Thu Nov 24, 8:50 pm)
Re: [LAD] sliders/fans, Nick Copeland, (Thu Nov 24, 8:31 pm)
Re: [LAD] "bleeding edge html5" has interesting Audio APIs, David Robillard, (Tue Nov 22, 1:04 am)
Re: [LAD] "bleeding edge html5" has interesting Audio APIs, Fons Adriaensen, (Mon Nov 21, 9:34 pm)