 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
 |
|
||||||||||||||
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
|
1. My computer spontaneously rebooted. What gives? 2. I’m hearing clicking, popping in my audio, and/or experiencing audio dropouts. 3. The input meters on the console are not showing activity. 4. The input meters on the console are showing activity, but I don’t hear anything. 5. The output meters on the console are not showing activity. 6. The output meters on the console are active, but I don’t hear anything.
1. My computer spontaneously rebooted. What gives? [top] If you are running Windows XP, Vista, or Windows 7 and your computer spontaneously reboots, you probably have experienced what Microsoft calls a “bug check,” but what everyone else calls the Blue Screen of Death (BSOD). The default setting for the BSOD is not to show the BSOD, but to reboot the computer. This isn’t very helpful for tracking down problems. If you are experiencing blue screens, here’s how you can help us track it down. (These instructions are for XP, but Vista and Windows 7 are similar): 1. Select Start/Control Panel/System Now, next time you get a blue screen, look at it. See if the crash occurred in echogals.sys, echo24.sys, echo3G.sys, echondgo.sys or echo1394.sys; if it did, then it’s probably something we need to fix. Restart your computer and find the most recent .dmp file - this is the memory dump. It’s probably in the \WINDOWS\minidump folder. Zip up the .dmp file and send it to Echo technical support along with a description of how it happened. This will help us track down the problem.
2. I’m hearing clicking, popping in my audio, and/or experiencing audio dropouts. [top] If the audio buffers in your audio application are set too low, you may experience clicking, popping, and drop-outs. Correct buffer settings will differ from machine to machine depending on your particular setup. Your motherboard, hard disk, processor, and RAM are all factors in audio recording/playback performance. You will set the number and size of the audio buffers in your audio application; so, refer to the given audio application’s documentation for buffer setting instructions. If you have wireless, you may need to turn this off. There may be a physical switch which disables your wireless capability. Make sure you have the input clock set to internal in the Console application, unless you are syncing to another device via Word Clock, S/PDIF, or ADAT. For a complete discussion on clocking, please refer to your Echo product manual. Run as few programs as possible in the Windows system tray. The Windows system tray is the section of the taskbar containing the clock. Each icon you see in the tray represents a running program, and programs in the tray consume your computer’s resources. Programs running in the tray can cause audio latency and unpredictable behavior in your audio programs. Right-clicking the icon and selecting “disable” will remove most programs from the tray. You can also check our FAQ sheet here for some other troubleshooting tips.
3. The input meters on the console are not showing activity. [top] Make sure the device going into the Echo hardware is actually sending a signal. Note that some instruments and devices may need a preamp or a mixer with a preamp to adjust the input level. For PCI-based interfaces, make sure the cable from your breakout box to the Echo PCI card is attached. If there is a power switch, make sure it is turned on. This is true for the AudioFire 4, AudioFire 8, AudioFire Pre8, AudioFire 12, Layla24, and Mona. If you are using the digital inputs, make sure you have the correct digital mode selected in the console. If you have checked the above items, your Echo product may need to be serviced; contact Echo support.
4. The input meters on the console are showing activity, but I don’t hear anything. [top] Make sure the input channel is not muted (M) in the console. Make sure the output is not muted in the console. If monitoring through your audio program, check the routing in that program. Make sure that you have speakers correctly connected to the appropriate outputs.
5. The output meters on the console are not showing activity. [top] Make sure you have the Echo hardware selected as the output in your audio application. Within any audio application, you should be able route the output of a track to an output of your Echo hardware. Make sure this is set up correctly; you can refer to your audio application's manual for instructions on setting up your audio interface. Make sure the track in your audio program is not muted. Make sure the “playback” channel strip for the given output bus on the console isn’t muted.
6. The output meters on the console are active, but I don’t hear anything. [top] Make sure you have your speakers connected to the same outputs that you have designated for playback in your audio application. If you are using a mixer and not getting output, try taking the mixer out of the setup. Connect an amplifier or powered monitor speakers directly to your Echo Hardware to check for a signal. If there is a signal, the problem is the routing in your mixer or other outboard gear. |
COPYRIGHT 2011 ECHO DIGITAL AUDIO CORPORATION |