RME Audio Fireface 802, User Manual

Page: 37 / 112

User's Guide Fireface 802 © RME 37
18. Hotline – Troubleshooting
The newest information can always be found on our website
www.rme-audio.com , section FAQ,
latest Additions.
The unit and drivers have been installed correctly, but playback does not work:
•
Is Fireface 802 listed in the System Profiler? (Vendor ID 2613).
•
Has Fireface been selected as current playback device in the audio application?
The 8 ADAT channels don’t seem to work
•
The optical output ADAT2 has been switched to AES/SPDIF. As can be seen in the block
diagram, all channels and their assignments still exist, but the optical transmitter has been
disconnected from ADAT2 and is now fed from the AES output (channels 13/14). The
ADAT2 playback devices are still usable by routing and mixing them in TotalMix to other out-
puts.
Playback works, but record doesn’t:
•
Check that there is a valid signal at the input. If so, the current sample frequency is dis-
played in the Settings dialog.
•
Check whether the Fireface 802 has been selected as recording device in the audio applica-
tion.
•
Check whether the sample frequency set in the audio application (‘Recording properties’ or
similar) matches the input signal.
•
Check that cables/devices have not been connected in a closed loop. If so, set the system’s
clock mode to ‘Master’.
Crackle during record or playback:
•
Increase the number and size of buffers in the application.
•
Try different cables (coaxial or optical) to rule out any defects here.
•
Check that cables/devices have not been connected in a closed loop. If so, set the system’s
clock mode to ‘Master’.
•
Check the Settings dialog for displayed Errors.
Possible causes for a Fireface not working
•
The FireWire or USB cable is not, or not correctly inserted into the socket
Driver installation and Settings dialog/TotalMix work, but a playback or record is not possible
•
While recognition and control of the device are low bandwidth applications, playback/record
needs the full FireWire transmission performance. Therefore, defective FireWire cables with
limited transmission bandwidth can cause such an error scheme. The same is true for USB
cables.