Post by i***@public.gmane.orgHi - Has anyone set up an 03D (or similar Yamaha digital mixer) to
control Logic's faders using midi remote? I have set it up to act as
hardware controller for Pro Tools LE (Digi001) and that works OK. Any
advice greatfully received,
Many thanks - Ian
Following is an earlier post I wrote regarding my complete 03D strategy.
Some of it refers to how you would automate the 03Ds functions from within
Logic and some refers to setting up the 03D as a remote controller OF Logic.
To get the most out of the 03D for remote functions you need to use the "To
Host" port to connect to your computer. The reason is when you do, the 03D
can act as a multiport interface sending different remote layers to the
computer at different ports. This way you can get around the inherent 16
midi channel limit.
==============================
Every parameter in the 03D sends out either sysex or midi controller when a
value is changed. The 03D has a" to host" port on it. In the mixer you can
set weather the 03D behaves as either a standard 1 port midi interface or as
a multiport I/F. I use multiport. This way I can send to LAMP in various
layers and split the data inside LAMP to send it where I need it to go..
I use port #1 to send the mixer's own movements (sysex and midi CC's).
I use port #2 for the midi connectors on the 03D where I may have other
equipment connected.
I use ports #3-6 respectively for the four midi remote layers that I
generally use to control LAMP's audio faders.
OK, now for what I do inside LAMP...
You'll notice that the physical input in the environment allows you split
specific ports out of the sum input. My Unitor8 uses my modem port so that's
modem 1-8 taken. I bring the "To Host cable from the 03D into my printer
port. As explained earlier various data comes in from the 03D on ports 1-6
Let's use printer port #1 as an example - The one that all the 03D's
parameter movement data comes in on.
In all these examples you'll notice that I always have an OFF setting. I
learnt this the hard way. For a while I had weird behaviour from LAMP until
I discovered that all the data coming from the 03D when not required was
messing with LAMP. In my autoload song I always have all these cable
switchers default to the OFF position.
I create a cable switcher. I cable from printer #1 to the switcher. Then I
define two settings for the switcher output.
#1 I call OFF. This output goes nowhere.
#2 I call RECORD. This output gets cabled to the Sequencer in.
When I want to record 03D automation I set the switcher to RECORD, and
select the 03D instrument as the track to record onto. Make sure you set the
03D instrument as the default "instrument without midi thru" or whatever
it's called or you'll get a midi feedback loop. The 03D has no local off
facility. Set up this way all movements at the 03D get recorded in LAMP and
you'll hear them as you record, and when playing back the 03D will see all
automation. You can watch the faders move and also see the virtual knobs
moving in the 03D display.
I use a similar approach for the 4 midi remote layers to control the audio
objects in LAMP. I have the midi messages for the 4 remote layers setup so
the faders on the 03D control the faders on LAMP's audio objects and the
on/off buttons on the 03D to control the mute functions. Each midi remote
layer has 16 faders/ switches you can specify midi messages for. So I use
remote layer #1 for Audio channels 1-16 and remote #2 for 17-32. I use
remote #'s 3&4 to give the same control of the busses and outputs. Note that
there only being 16 midi channels available the 4 midi remote layers have
exactly the same settings, but they show up at different ports on the
physical input in LAMP which then allows you to send them to different
groups of faders.
I take physical inputs printer 3-6 and cable them to their own cable
switchers. I define three settings for each of the 4 switchers.
#1 I call OFF. This output goes nowhere.
#2 I call DIRECT. This output gets cabled directly to the Audio playback
object which in turn is cabled to the various banks of audio objects. I get
direct control of LAMP's faders and when you move an 03D fader you'll see
the corresponding LAMP fader move also.
#3 I call RECORD. This output gets cabled to the sequencer input for
actually recording fader or mute automation for LAMP's various audio
objects. Just make sure you have the appropriate audio playback object
selected as the record track in the arrange window. This way you'll hear the
moves as you record and won't have to switch anything to also hear the
playback.
That's it.....
==================================
This next section describes how I configure the Midi remote layers in the
03D
==================================
First a quick bit of theory. A controller is only one type of midi message.
When you set up the 03D the first thing you have to do is specify the type
of midi message the remote fader sends. Problem is, you have to specify it
as a hexadecimal value. Just as decimal is a 10 based way of counting,
hexadecimal is a 16 way of counting. It goes 0, 1, 2, 3, 4, 5, 6, 7, 8, 9,
A, B, C, D, F. In order, here are the midi messages and their respective hex
values.
Note off - <8n.xx.yy> 8 is the message or status byte, n is the midi channel
from 0 - F. xx is the note number and yy is the velocity.
Note On - <9n.xx.yy> Notice the only thing that changes is the status byte.
Polyphonic Aftertouch - <An.xx.yy> Once again, only the status byte changes.
Control Changes - <Bn.xx.yy> This is the one that we will be using. B is the
status byte, N is the midi channel, xx is the controller number (in your
case 07) and yy is the value.
Program Change - <Cn.xx> Notice the shorter message. Program changes need
only specify, status, midi channel and value.
Pitch Bend - <En.xx.yy>
System Exclusive - F0 - FF.
Select fader channel 1 one the remote page.
First we have to specify the status (controller). In the first square of
data. scroll through until you get to "B0". "B" for controller and "0" for
midi channel 1. Cursor across to the next data square. Here we specify
"which" controller. In this case - "07". Note that although we are in
hexadecimal the first 9 values of counting are the same as decimal. Cursor
to the next square. Normally hare is where you would enter the value to be
sent, but we don't want any specific value sent, we want this value to
represent the position of the fader so Yamaha have cleverly included and
extra setting for this. If you scroll all the way past the end value (FF)
the next setting is "FAD" Meaning "fader value". Lastly, in the next square
scroll a ll the way to the end (past FAD) and you will come to a setting
marker END. That's it finished.
Your completed string should read "B0 07 FAD END"
All you do now is select the following fader objects and do the same,
changing only the channel value.
Fader#1 - B0 07 FAD END
Fader#2 - B1 07 FAD END........
Fader#16 - BF 07 FAD END
=======================
Hopefully this makes some sense and is of some help.......