7 Aug
2014
7 Aug
'14
8:39 a.m.
Please excuse my "youthful" enthusiasm...
I am having some success with my usb computer keyboard as a midi control
surface.
All things are assignable to any key.
the key events press, release, and repeat can be set separately (or
ignored)
Key presses can control:
- Jack transport:
roll
stop
zero
1 or ten sec forward or back (will make this settable)
I have press do one second and repeat do 10
- midi messages these are all in hex and can include:
channel messages like key, ctl, pgm, etc
sysex up to 20 char in total
I am not sure what the limit is for jack
but any of the control surfaces I have
studied seem to send less.
The reality is that there are lots of control surfaces out there and sw
has to handle what they send.
I do have a question though about ardour control by midi. The Mackie IF
says it sends control messages that are in the form num of ticks up or
down. This means I should be able to have a key send ticks up and another
ticks down, but this doesn't seem to work.
Also, It seems the master rec-enable is not toggle-able. Odd. I have tried
both making a map file and using the learn function. Is there more
documentation for this somewhere? It would not be impossible to toggle
things from inside the controler or take ticks up and down and convert to
127 or 1024 steps. This is not just for ardour but I am wanting to know
what is standard.
--
Len Ovens
www.ovenwerks.net
7 Aug
7 Aug
7:48 p.m.
On Wed, 6 Aug 2014, Len Ovens wrote:
I do have a question though about ardour control by
midi. The Mackie IF says
it sends control messages that are in the form num of ticks up or down. This
means I should be able to have a key send ticks up and another ticks down,
but this doesn't seem to work.
It does work... but only into the the mackie midi in. It only seems to
expect 0 to 100 ticks which is probably not enough for a fader anyway.
This is probably due to physical limitations in the encoders, getting more
than 96 or so ticks per full turn starts to get expensive real quick (10
to 1 or so... which answers the why use motor faders question). Changing
controls on the gui while monitoring the midi out was very informative.
Also, It seems the master rec-enable is not
toggle-able. Odd. I have tried
It is if I call myself a mackie control surface. That seems like as good a
standard as any for mapping, though it would just be a sample config file
and the user is welcome to create their own.
As it is not too hard, I think it is best to make fader/pitch controls
that convert ticks to absolute value and accept the same from midi in. All
the MIDI info I have also suggests that a controller should give a value
between 0 and 127 so the same there. Encoders are already taken care of
and work as is (using two key events). I have three LEDs to play with and
will set them up as user settable, but my default will probably be Record,
Roll and select (use all controls for stuff on a single channel)
Really, having the logic for a control surface as an application gives a
lot of room for things a HW surface can't do.
--
Len Ovens
www.ovenwerks.net
8:28 p.m.
On Thu, Aug 7, 2014 at 1:44 PM, Len Ovens <len(a)ovenwerks.net> wrote:
On Wed, 6 Aug 2014, Len Ovens wrote:
I do have a question though about ardour control by midi. The Mackie IF
Ardour has an internal scaling factor for those ticks, or did at some
point. The Mackie D8B mixer had similar issues with its scroll wheel. We
seem to have removed it.
says it sends control messages that are in the
form num of ticks up or
down. This means I should be able to have a key send ticks up and another
ticks down, but this doesn't seem to work.
It does work... but only into the the mackie midi in. It only seems to
expect 0 to 100 ticks which is probably not enough for a fader anyway. This
is probably due to physical limitations in the encoders, getting more than
96 or so ticks per full turn starts to get expensive real quick (10 to 1 or
so... which answers the why use motor faders question). Changing controls
on the gui while monitoring the midi out was very informative.
8:29 p.m.
On Thu, Aug 7, 2014 at 2:28 PM, Paul Davis <paul(a)linuxaudiosystems.com>
wrote:
On Thu, Aug 7, 2014 at 1:44 PM, Len Ovens <len(a)ovenwerks.net> wrote:
correction. the scaling factor was ONLY for the scroll wheel. faders work
fine for me on an SSL Nucleus usng Mackie Control, which I strongly
recommend (Mackie Control (or the Nucleus if you want to pay for it :)
On Wed, 6 Aug 2014, Len Ovens wrote:
I do have a question though about ardour control by midi. The Mackie IF
Ardour has an internal scaling factor for those ticks, or did at some
point. The Mackie D8B mixer had similar issues with its scroll wheel. We
seem to have removed it.
says it sends control messages that are in the
form num of ticks up or
down. This means I should be able to have a key send ticks up and another
ticks down, but this doesn't seem to work.
It does work... but only into the the mackie midi in. It only seems to
expect 0 to 100 ticks which is probably not enough for a fader anyway. This
is probably due to physical limitations in the encoders, getting more than
96 or so ticks per full turn starts to get expensive real quick (10 to 1 or
so... which answers the why use motor faders question). Changing controls
on the gui while monitoring the midi out was very informative.
8:47 p.m.
On Thu, 7 Aug 2014, Paul Davis wrote:
On Thu, Aug 7, 2014 at 2:28 PM, Paul Davis
<paul(a)linuxaudiosystems.com> wrote:
On Thu, Aug 7, 2014 at 1:44 PM, Len Ovens <len(a)ovenwerks.net> wrote:
On Wed, 6 Aug 2014, Len Ovens wrote:
I do have a question though about ardour
control by midi. The Mackie IF says it sends
control messages that are in the form num of
ticks up or down. This means I should be able
to have a key send ticks up and another ticks
down, but this doesn't seem to work.
It does work... but only into the the mackie midi in. It only seems
to expect 0 to 100 ticks which is probably not enough for a fader
anyway. This is probably due to physical limitations in the encoders,
getting more than 96 or so ticks per full turn starts to get
Ardour has an internal scaling factor for those ticks, or did at some
point. The Mackie D8B mixer had similar issues with its scroll wheel. We
seem to have removed it.
There seems to be some scaling for the encoders too, Sometimes one tick
moves one notch and sometimes two... probably to get 100 out of 96, which
makes sense(defaults to pan, I haven't tried other modes yet). I have not
played with the scroll as yet.
correction. the scaling factor was ONLY for the scroll
wheel. faders work fine
for me on an SSL Nucleus usng Mackie Control, which I strongly recommend (Mackie
Control (or the Nucleus if you want to pay for it :)
So far I have spent $3 on this surface :) I expect the key labels will
cost more than that though. Still, it is already very usable in the form
it sits. I think if I do 5 or 6 channel banks I will have as complete
channels as possible. If I just use the controller and make my own switch
panel, I could get the full 8 + master and transport. I am aiming for
half.. The encoders and "faders" will have their own HW.
--
Len Ovens
www.ovenwerks.net
3795
days inactive
3795
days old
linux-audio-dev@lists.linuxaudio.org
4 comments
2 participants
participants (2)
-
Len Ovens -
Paul Davis