Inhaltsverzeichnis
Werbung
SMPTE when the MTP/Express Console is the
active application. To make the MTP/Express
Console the active application, click on of its
windows (such as the Sync Controls window).
My MIDI software won't sync to tape and the MIDI
Express XT.
Make sure that the MIDI Express XT is slaved to
SMPTE first by opening the SMPTE Reader. As
long as the SMPTE Reader window shows that the
MIDI Express XT is successfully locking to the
SMPTE and generating MIDI sync, MIDI software
should also be able to lock to the MIDI sync signal.
My Performer program won't sync to tape and the
MIDI Express XT, no matter what I do.
Are you using Version 3.4 or higher? If not, then
you need to update because older versions of
Performer don't support MTC. Contact Mark of
the Unicorn for information about updating. If you
are using Version 3.4 or higher, make sure that
MTC is chosen in the Receive Sync dialog box.
Make sure the correct port (modem or printer) is
chosen. Use the MIDI Monitor Window to see on
which port the MIDI Express XT is sending MTC
and to make sure it is the desired format. In the
MIDI Monitor window, MTC lights up the "CO"
indicator. Make sure that Performer's settings
match the incoming time code format.
When I play notes from my MIDI controller, the
notes sound funny/chopped off/phased/etc. OR I
run out of voices sooner than I should on my sound
sources.
This means that you are probably routing data to
the sound source twice by accident, either via the
Auto-Channelize feature in Performer or other
MIDI software, or via a route you were not aware of
in the Cable Routing or Channel Mapping
windows in MTP/Express Console. To solve the
problem, try to identify from where the extra
routing is coming. For example, switching off the
Macintosh will tell you if it's the culprit or not. The
Cable Routing window is also a good place to hunt
for a problem.
104
MIDI data received from the Express XT by the
Macintosh is garbled. Likewise, MIDI data going
from the Macintosh to the Express XT gets garbled,
too.
First, be sure that your software is set to 1 MHz for
its serial port speed. If it is, then the DIN-8 cable
between the Macintosh and the Express XT may be
too long, or it may need replacing. A length of no
more than 30 feet is recommended and, depending
on the electromagnetic environment, maybe even
less. Because of a limitation with the Macintosh
serial ports, well-balanced, standard RS-422
compatible signals cannot be used between the
MIDI Express XT and the Macintosh; therefore,
the signal in the cable can get noisy as the length of
the cable increases. In general, use a cable that is
shielded, has approximately 100 Ohms character-
istic impedance and has as little capacitance as
possible.
My old DX7 causes problems on the Express XT as
soon as I plug its MIDI OUT cable into one of the
MIDI IN cables.
Very old DX7s emit a continuous stream of Yamaha
system exclusive message headers (F0 43) as a form
of active sensing. This output can interfere with the
Express XT. As a result, we recommend that you
mute system exclusive data on the MIDI
Express XT input cable to which your old DX7 is
connected.
You can determine if your DX7 emits this form of
active sensing by connecting a MIDI cable from the
MIDI OUT on the DX7 to any MIDI IN on the
MIDI Express XT. Look at the input LED to see if it
flickers continuously. If so, it is emitting active
sensing data, either in the form of regular MIDI
active sensing (which is OK) or Yamaha system
exclusive headers (which will cause problems).
Power off the DX7 and the Express XT. Power on
the Express XT and open the MTP/Express
Console. Mute system exclusive on the input cable
and then route the input cable to any output cable.
Power on the DX7. If the output cable LED does
not flicker, it shows that you have successfully
Werbung
Inhaltsverzeichnis
