The following troubleshooting tips can help diagnose and correct most concerns with the D3. We have attempted to make this list as comprehensive as possible, so some of these may not apply to your issue, but please go through each tip.
- Restart your computer and make sure your computer’s OS and all related apps are up-to-date.
- Verify that the audio cable (or headphone) connection out of the D3 is complete and in working order by unplugging the cable and then reconnecting.
- Remove all other USB devices temporarily from your computer to see how this affects D3 playback. Audio over USB and bus powering a device can both be somewhat demanding. USB ports can share a bus internally and can also share their bus with devices internally as well. Because of this, some ports may not perform as well as others, so be sure to try each USB port one at a time.
- If using Windows, uninstall the USB driver from your computer. Then disconnect D3 from your computer and plug it back in to allow the driver to re-install automatically. You can find complete instructions from Microsoft on how to reinstall a plug-and-play device under Windows here.
- If you are using a Mac, try a NVRAM/PRAM reset. This resets the system configurations for some audio and video related items and can many times help clear up problems related to audio. See Apple’s support page for information on how to do this. Also, be sure to check the App store to see if there's a newer version of Mac OS you could be running.
- Try music with different bit depths and sample rates. On a Mac these settings are under Applications --> Utilities --> Audio MIDI Setup. Try using both 16-bit as well as 24-bit settings.
- Experiment with using a different media player (iTunes, Songbird, WinAmp, Cog, etc) and different audio file types (MP3, ALAC, FLAC, etc). And if your media library is located on an external drive or network attached storage (NAS), try playing audio files on your internal local hard-drive.
- If possible, try your D3 with a different computer to see if something is causing an issue in the current setup.