MOTU Micro Lite [148/166] Troubleshooting

APPENDIX C: TROUBLESHOOTING AND CUSTOMER SUPPORT

148

in ClockWorks to make sure there is a connection between

the MTC port in the left-hand column and the computer

port in the right-hand column.

My MIDI software won’t sync to tape via my MOTU

interface.

Make sure that the interface is slaved to SMPTE ﬁrst by

opening ClockWorks to see if you get a running update of

time code while tape is running. As long as the SMPTE

display shows that the interface is successfully locking to

the SMPTE and generating MIDI Time Code, MIDI

software should also be able to lock to the MIDI Time

Code.

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 Patch

Thru feature in your host MIDI software, or via a routing

you were not aware of in ClockWorks. To solve the

problem, try to identify from where the extra routing is

coming. For example, switching off the computer will tell

you if it’s the culprit or not. The Routings tab in

ClockWorks (or the Device Settings & Routing window

under OS 9) is also a good place to hunt for a problem.

TROUBLESHOOTING

Troubleshooting is always simplest and most effective

when the exact problem can be speciﬁed clearly and

concisely. If you are surprised by an error message or by

seemingly erratic behavior in the console or network, take

a moment to jot down the relevant details: exactly what the

error message said (including any error ID numbers),

what actions were done on-screen just before the problem

occurred, what kind of ﬁle you were working with, how

you recovered from the problem, and any unusual

conditions during the occurrence of the problem. This

may not enable you to solve the problem at once, but will

greatly aid in isolating the problem should it reoccur.

If the problem you are encountering seems inconsistent,

try to determine what the necessary pattern of actions is

that will cause it to occur. Genuine bugs in application

software like the ClockWorks are almost always consistent

in their manifestation: the same set of actions under the