On Sat, 5 Jul 2014, Fons Adriaensen wrote:
> On Sat, Jul 05, 2014 at 10:17:21AM -0700, Len Ovens wrote:
That was one of the projects I looked at. Thank you.
> There's one problem with this: the author has the H-bridge
Good to know... Yes that makes sense, right away. From the look of the
video it does not add very much resistance, but a quick fader movement may
be hard on the motor still.
For me it is a toss up between using motorized faders and just supplying
enough faders (24?) that don't need a motor. The simple answer is that
while I don't use more than two inputs at a time, even a relatively
simple project could use up all my faders by the time I have a few subs
and master. 8 motor faders starts to look cost effective pretty quick. The
ability to come back to a project and have my faders where I left them
without a cue sheet (which would only be aproximate anyway) would be a
bonus that is hard to put a price on.
My first project will not have (resitive) faders because the interface
does not support analog inputs. It will have buttons and maybe I can work
encoders in there too. It is based on a PC USB keyboard ($3 new) which is
not MIDI out of course, so the SW interface will be in the computer based
on the code from actkbd. I do not know if I will be able to get encoders
to work past the debounce, but even having transport control and other
button based controls will be worth something.
It may even be worth while to be able to use the numeric pad for midi out
while letting the rest of the keys go through as normal.
Linux-audio-user mailing list