Operation Manual

319
PRO2 Live Audio System
Owner’s Manual
Appendix D: Troubleshooting
This appendix gives details of troubleshooting the PRO2 Live Audio System.
No audio
If you have set up the PRO2 and followed all of the instructions for obtaining audio, but
you are not hearing anything through the speakers, check the following:
• Make sure the appropriate ST buttons in the channel fast strips are on.
• Make sure the appropriate ST buttons in the source a/b panels (monitors section of
the output bay) are on.
• Make sure nothing is muted.
• Make sure no faders are set to minimum.
• Check that the VCA group and master faders are at unity gain.
• Use solo at selected points in the signal path to try and pinpoint where the signal is
being lost.
•Check the Preferences screen for correct signal routing by making sure channel
sources/destinations are correctly assigned.
If you still don’t have any audio, contact Midas Technical Support.
Troubleshooting automation
This section explains the error messages that you may see when using PRO2
automation.
Error messages
Error messages, which can appear when you are accessing the Files or Automation
screens, provide useful information on the condition that triggered them. Due to the
way the filing and automation systems interact with the internal processing system of
the PRO2, not all error messages are indicative of a problem; some may appear due to
the current state of the system and just require a retry of the operation.
Error messages comprise two components — a first line of text containing the error
condition, followed on the next line by a description of the error (prefixed by the text
“response:”). The error condition text indicates the operation that may have triggered
the error message, while the error description text explains the reason for failure and,
in some cases, also provides information that may be useful to service engineers. The
following diagram shows a typical error message.
Error condition (see “Error
condition messages” on
page 320)
Error description (see “Error
description messages” on
page 321)