Start by checking every component in the audio chain. Is the problem eliminated by swapping cables, headphones, or the audio source?
- DACs: Try a different USB port, a different USB cable, and a USB hub or different computer.
- Amplifiers: Try another audio player, a different input cable, and another pair of headphones. For battery powered amplifiers, try connecting a power adapter or swapping batteries.
- Amp+DACs: Try the amplifier by itself (use 3.5mm/RCA input instead of USB input). If the amplifier operates normally, see DAC troubleshooting. Otherwise, refer to Amplifier troubleshooting.
Please also refer to your device's specific Instructions Guide. Many behaviors are easily explained by normal device operation.
USB device is not recognized by PC
Causes: Damaged or unsuitable USB cable or USB port, or missing drivers.
Solution: Try a 3-foot or shorter USB cable. Long and/or custom USB cables can impact device connectivity at some USB ports. Avoid boutique 'audiophile' cables. The official Universal Serial Bus specification dictates a 90-ohm characteristic impedance; boutique cables may or may not conform to mandatory data specifications.
A different USB port or powered USB hub can sometimes help.
If using a Type C USB port, please try a different Type C adapter.
DAC feels hot to touch
JDS Labs DACs are designed with linear regulation, whereas most consumer electronics are designed with high efficiency switching regulation. Linear regulation is free of switching noise and produces heat during the process of stepping down the supply voltage.
DACs tend to operate at low voltages (5V or less), thus, more energy is converted to heat in the linear regulation stages compared to our higher voltage amplifiers. Use of AC transformers ensures mains isolation, while heavy use of linear regulation enables exceptional performance.
Every DAC we design begins with a careful power consumption budget for each supply rail as well as a corresponding thermal budget. We validate power and thermal characteristics early in the prototyping process to ensure stable operation. Each design must also pass a plethora of FCC and CE compliance tests prior to production.
In other words, rest assured your DAC is operating safely and normally!
No audio from Netflix or Hulu or Prime
Some media apps in Windows set default playback to Dolby Digital®. This format is not supported by most external DACs, which results in no audio output. To resolve, disable Dolby Digital®:
Right click the volume icon in your taskbar --> Click Sounds --> Playback, Select Properties of your DAC --> Playback Devices --> Supported Formats --> Uncheck Dolby Digital
Some installations may not present the "Supported Formats" tab. As a workaround, you can also uncheck "Allow applications to take exclusive control of this device" under the "Advanced" tabe.
If neither of these solutions help, you may also first select another audio device, and then switch to your DAC to prevent the app from defaulting to an unavailable format.
Intermittent, quiet crackling or popping sounds, like dust on a turntable
Causes: Digital audio requires uninterrupted, real time data. Quiet crackling or popping sounds during playback are symptomatic of buffer underrun, meaning the USB or S/PDIF audio source failed to deliver a continuous stream of digital data to the DAC. Or more simply, the device driver's real time process was interrupted. Buffer underrun on a USB host is a low level software behavior that may occur regardless of the load and available computational resources of your computer.
Higher sampling rates are more likely to result in buffer underrun conditions because more data must be transmitted. Some known causes include: Intel Haswell CPUs, Apple's Fusion Drive, WASAPI Playback on Windows, and USB ports serving multiple devices. Faulty USB or optical cables can also create buffer underrun, since data will not be reliably delivered.
Solutions: Set your DAC to a lower sampling rate, such as 24/44.1k or 24/96k. Try a different cable. For USB DACs, try a USB port on a different USB bus of the PC, such as a port on the opposite side of your laptop or tower. Try an external USB hub. Also see Cantabile's Glitch Free PDF.
If your DAC and PC support coaxial or optical S/PDIF input, switch to a mode other than USB.
For the original JDS Labs EL DAC, make sure to install the Bravo HD Drivers. This will allow you to increase the buffer length from the Bravo HD app.
For current generation DACs including Element II, EL DAC II, Atom DAC, please install the optional XMOS drivers from the product page. XMOS sets a "safe" buffer length through the provided drivers.
Games hang or experience loading delays
Causes: A known operating system bug can cause some DirectSound (Direct3D) applications, usually games, to freeze for up to 60 seconds while attempting to load an absent hardware device.
Solution: Open Device Manager and expand the 'Human Interface Devices' category. Right click on 'HID-compliant consumer control device' and select Disable. If multiple deviecs with the same name are present, check each device's Properties -> Details -> Hardware Ids. JDS Labs DACs use VID_262:
PS4 / PS5: Low volume
Causes: PS4 contains a USB audio bug which sets very low volume despite showing maximum volume on screen.
Solution: Use optical output if possible. If you require USB audio, please contact us and we can load alternative firmware onto ODAC or first generation Elements to disable operating system level volume adjustment. This modification disables PS4's ability to reduce volume.
For Atom DAC, EL DAC II, or Element II, please refer to our custom PS4/PS5 firmware downloads.
Linux: Low volume or unsatisfactory audio quality
Causes: In Ubuntu, the Pulsesound interface may not reflect the sound configuration defined by `alsamixer`. In other words, 100% volume in the GUI is inaccurate and/or equalization has been incorrectly applied to the digital audio stream.
Solution: Re-install `alsa-utils` and ensure the latest version of `alsa-lib` is installed (part of the `libasound2` package):
sudo apt-get update sudo apt-get upgrade sudo apt-get install alsa-utils --reinstall sudo apt-get install libasound2
If low volume persists, open the alsamixer command line interface (CLI):
Use the navigation commands presented by the CLI to check and adjust volume of your DAC. After making adjustments in alsamixer, save settings to persist when the DAC is reconnected or PC is rebooted. Use `locate asound.state` to find the directory in which sound settings are stored. Assuming asound.state is located in `/var/lib/alsa/asound.state`, execute the following example commands:
sudo alsactl store cp /var/lib/alsa/asound.state to ~/.config/asound.state
Audible click when changing tracks or starting/stopping playback
Causes: Quickly changing tracks in some software causes a DAC to suddenly cut the digital audio stream, resulting in discontinuity at the analog output. Mathematical discontinuity is a common and normal behavior, and is handled differently by each audio system. Each layer of the audio chain may impact how discontinuties are handled (USB to I2S engine, drivers, and application level).
Solution: While our newer asynchronous XMOS based USB engines generally handle discontinuities well, it's possible that application level transitions will produce an audible transient.
Try adding Fade In and Fade Out. Within foobar2000, for example, try increasing Fade In and Fade Out length under: Preferences --> Output --> Playback --> Output.
Other audio apps may refer to Fade In as "delay" or "buffer".
Some DACs enter self-mute mode when audio stops, and such muting may reveal a discontinuity. If possible, disable auto mute or standby mode.
DAC intermittently disconnects or distorts, or DAC unavailable after standby
Causes: Unsuitable USB cable, or use of a dock or KVM Switch, or undesirable USB power management settings.
Newer operating systems (Win 7, 8, 10, and OS X 10.9+) sometimes utilize unnecessary power management configurations, which can limit power availability to a DAC.
Solutions: Try a 3-foot or shorter USB cable (also refer to 'USB device is not recognized by PC').
If you are using a Thunderbolt-to-USB adapter, it may help to use a different adapter brand/model.
Keyboard Video Monitor Switches, or KVMs, have been known to result in random dropouts of USB audio devices. Try a direct connection to your PC.
Try a powered USB hub. A hub guarantees power availability to connected equipment.
Alternatively, try disabling power management options. In Windows, Open Control Panel --> Hardware and Sound --> Power Options --> Change Plan Settings --> Change Advanced Plan Settings --> USB Settings --> Set 'USB selective suspend setting' to Disabled. While this configuration may help, a USB hub is a more reliable solution.
One owner writes, "The udev rule I had in place was being overridden by tlp power saving (which I didn't know was running). The solution was to add the device to tlp's USB power saving blacklist."
Whining noise from external monitors when using USB Input
Causes: Monitors and external speakers are often powered by switching power supplies, like your computer. While OL DAC and EL DAC are isolated from mains using an AC transformer, ground loop occurs between the PC ground and speaker ground. The audible noise may change as your PC load changes.
Solution: If possible, switch to optical input. If your PC lacks optical output, it's best to install an affordable PCI-Express card with optical output. Alternatively, you can try a set of ground loop isolators.
Unable to connect to an Android
Causes: Please refer to our blog article, How to Connect Android, iPad, or iPhone to a DAC.
Solution: Element, OL DAC, ODAC RevB and C5D can connect to any operating system which supports UAC1 DACs. Summarizing the above article:
- Ensure that your specific Android device and OS version supports USB DACs.
- Try an in-line USB hub.
- Try a powered USB hub.
- Try another OTG cable.
- Try rebooting the Android device while the DAC is connected.
- Try the demo version of USB Audio Player Pro.
Please note that support is dependent on the mobile operating system, and can vary with each operating system version! Google officially implemented USB Audio Class 1 (UAC1) support effective Android v5.0. Some customers have reported that previously DAC compatible Android v4.x devices no longer support their DACs after upgrading to Android v5.x. Others report that previously non-working Android 4.x phones and tablets finally gained support with Android v5.x. In other words, support remains unpredictable. The following user maintained list may help you: UAC1 - Android Compatibility.
Connectivity success is most reliable in Android 6 and newer. If you still encounter difficulty, try connecting your DAC to an in-line or powered USB hub, then connect the hub to your Android's USB Adapter. Some Androids disable the 5V supply pin during OTG connections, which can prevent a successful connection. A hub eliminates 5V uncertainty. A list of tested USB Adapters is maintained in the JDS Labs FAQ.
Unable to connect to iPhone or iPad
Causes: Please refer to our blog article, How to Connect Android, iPad, or iPhone to a DAC.
Solution: ODAC RevB, C5D, OL DAC, EL DAC, and The Element can connect to any operating system which supports UAC1 DACs. Summarizing the above article:
- Ensure that your version of iOS supports your Lightning adapter
- Try Apple's Music app before trying other apps
- Try reconnecting the USB cable
- Try rebooting the phone or tablet while the DAC is connected, especially after iOS updates.
- Make sure you are using a genuine Lightning adapter. The following model is supported:
JDS Labs has confirmed DAC support for iOS versions 7.x through 11.x (most recent build as of January 2017). Customers have reported DAC connectivity success with iOS 7.x, 8.x, 9.x, 10.x, and 11.x. Please note that support is dependent on the mobile operating system and can vary with each operating system update!
The older Lightning to USB Adapter, part #MD821AM, may be used with iOS 7.x thru 10.x, but does not support USB Audio when used with iOS 11.
Support frequently changes for Lightning to USB adapters. Newer units may require a newer version of iOS to be recognized. When a newly obtained Lightning adapter is connected to an older version of iOS, you may receive the warning, "This accessory is not supported by this device." Try updating to the latest version of iOS.
Some versions of iOS may initially display a warning such as, "ODAC RevB is not supported". Accept the warning and simply reconnect the USB cable. Your DAC should then successfully connect without warning.
If your DAC is unable to connect to your iPhone or iPad, try another iOS device for comparison. A dirty Lightning jack can prevent a DAC from connecting, even when the phone is able to charge or sync. Try cleaning troublesome Lightning jacks with a can of compressed air.
While all apps should support USB DAC operation, we have found that Apple's Music app is most likely to connect, especially after major iOS releases. A successfully connected DAC will appear at the bottom of the Music app in iOS 10:
Equalizer APO - Weak volume or unexpected sound quality
Cause: Some customers have reported unexplained low volume or sound quality issues when using Equalizer APO in conjuction with their USB DACs. This application replaces the sound device and digitally processes audio before it is sent to the USB DAC.
As of 06/2020, the application has been known to fail to provide expected audio output after disconnecting and reconnecting a USB DAC.
Solution: At this time (06/2020), we recommend uninstalling Equalizer APO if you are encountering difficulties. Please direct feedback to the software publisher.
Unknown DFU Device in Device Manager
Cause: DFU stands for "Device Firmware Upgrade". Element II, EL DAC II, and Atom DAC support firmware updates utilizing their DFU device. This optional device is not required for audio playback, and Windows does not install the driver. Thus, it appears as an unknown/uninstalled device.
Solution: You may install the optional XMOS drivers for your DAC to enable the DFU device. XMOS drivers are available on each item page, or from our Downloads page.
XMOS Driver Will Not Install
Cause: During installation of the XMOS drivers, some PCs have been known to remove the XMOS audio device and suggest a restart. The XMOS drivers are not installed and no device can be found after restarting the PC.
A normal installation does not prompt for a restart!
Solution: Finish the XMOS driver installation and do not restart when prompted. Immediatelly run the XMOS installer a second time. The driver should install correctly this time.
Amplifier or Preamp issues
Loss of Power
Loss of power indicates that your power adapter is disconnected, damaged, or incorrect. First, please check the basics:
1. If you have recently moved or reorganized your desk, make sure you have connected the original power adapter supplied by JDS Labs. Do not substitute for other power adapters.
2. Verify that your power adapter is firmly plugged in at both ends. Pets can accidentally unplug barrel connectors.
3. Verify that your surge protector is turned on (you are using a surge protector, right?).
If you've made it this far, it's helpful to know that all JDS Labs amplifiers and DACs are powered by AC transformers. All AC transformers contain a 1-time safety fuse. This fuse can blow during a storm or brownout. Some uninterruptible power supplies (battery backup units, or UPS's) can also blow the safety fuse. Dropping the power adapter may break the fuse as well. Unfortunately, the entire transformer must be replaced when the safety fuse blows.
There are two ways to verify that your AC transformer is working:
A) Place your hand on the power adapter after leaving it connected to the wall for at least five minutes. Is it operating at room temperature, or above room temperature? A working transformer will be warm to the touch. A damaged transformer will be cold.
B) Measure AC voltage of the barrel connector with a multimeter. Normal readings of our power adapters will range between 17-24VAC depending on the model and your outlet. A reading of 0V indicates a blown fuse.
Element II - No Audio
Cause: You may have accidentally pressed the Power/Mode button for more than 1 second.
Solution: Please refer to the Element II Quick Start guide. Press the Power button for > 1 second to toggle between RCA Output mode and Headphone Output mode.
All JDS Labs amplifiers are capable of powerful volumes when driven by an appropriate audio source. You should be able to reach painful listening volumes from virtually all headphones on the market. If volume is weak or mediocre, there is most likely a simple explanation. Please check the following:
- Make sure your amplifier is connected to a 2VRMS DAC. Weaker audio sources will limit maximum volume.
- Have you tried High Gain? Low gain is intended for low to moderate volumes.
- Check volume at your audio source and app. Volume should be set to max.
- For apps such as Tidal or Roon, please disable settings like Loudness Normalization or Volume Leveling. Such settings can sometimes limit the volume of your music.
- MacOS defaults to a low system volume. Make sure to adjust OS volume to 100%. Control listening level from your amplifier.
Feel free to contact us if you need additional help.
Diminished audio, or mono output, or loss of left or right channel
Causes: A partial or total loss of audio usually indicates a damaged cable or audio jack.
Solution: Try another input cable and another set of headphones. If using a 4-pin TRRS headphone cable (any cable equipped with a microphone or additional functionality), make sure to use an appropriate TRRS-to-TRS splitter. TRRS cables are incompatible with ordinary audio jacks.
Many customers mistakenly try to resolve channel loss by partially removing the audio connector from the amplifier's jack. This is not a solution! A partially unplugged cable shorts the Left and Right cables, resulting in mono output.
Feel free to contact us if other cables do not help, and we'll be glad to inspect further.
Severe distortion or clipping
Causes: Amplifier gain or volume is set too high for your equipment.
Solution: Set amplifier to low gain position, or reduce listening volume. Please refer to Power is Volume for a technical explanation.
Objective2 and Objective2+ODAC use a high-performance topology requiring that gain be configured to match the strength of your DAC or audio source. Please see the O2 FAQ for more information.
Constant buzzing or whine
Causes: Constant buzzing may indicate a damaged input cable, damaged audio jack, or ground loop interference.
Solution: Try another input cable. If buzzing persists with other cables, but vanishes when disconnecting the cable from the audio player, you're experiencing ground loop. Try connecting the amplifier and audio source to different electrical outlets, or if possible, operate the amplifier from battery power (unplug power adapter). As a last resort, try a ground loop isolator.
Constant background hiss
Solution: Try another audio player. If noise persists, you may have very high sensitivity (efficiency) headphones. For optimal performance with all headphones, set amplifier to the lowest gain position, set the audio player's volume at or near the maximum level (i.e., 100% volume at PC), and only adjust volume using the amplifier's volume knob. Switch the amplifier to high gain mode only when maximum listening volume is insufficient.
Intermittent buzzing or other background noise
Causes: Random buzzing or bursts of noise usually indicate wireless interference from cordless phones, cell phones, wireless routers, etc. The audio source itself may be generating background noise.
Solution: Try a different input cable. Position amplifier as far away as possible from wireless devices. Cell phone and wireless routers should be positioned at least 4ft away from audio amplifiers. Some 1.9GHz (DECT) cordless phones have been known to cause significant audible interference with amplifiers and other devices, even from base stations positioned several rooms away. If neither help, try a different audio source.
Static or noise while adjusting volume
Causes: Analog potentiometers use a mechanical wiper travelling along a resistive path to adjust signal voltage (listening volume). Moving your amplifier's volume knob causes the wiper to move along its path. This mechanical process produces low level noise while the knob turns, and is most noticeable while music is playing. The noise may or may not be audible depending on your system.
Solution: Please understand that wiper noise is a normal behavior of analog volume controls and varies based on many conditions.
Certain climates can exacerbate the effect. You are more likely to notice wiper noise when adjusting volume while listening to quietly recorded music, or to music with low energy content.
Wiper noise may become more noticeable as your potentiometer ages. The average potentiometer has a mechanical lifespan of 15,000 turn cycles, or about four years assuming 10 complete turns per day. If your potentiometer has reached the end of its consumable lifespan, we'll be glad to swap the part for you at cost.
Causes: This is a minor side effect of a high performance analog volume control. Any amplifier which relies on an analog potentiometer to control volume will exhibit some degree of channel imbalance at the lowest threshold of knob rotation. Audible channel imbalance usually resolves by 15-25% rotation of the knob.
So why do amplifier designers still rely on analog potentiometers? Performance! Tiny digital potentiometers can control volume with great resolution and balance at all volumes. However, digital pots introduce unwanted capacitance, which directly degrade total harmonic distortion (THD). High-end digital potentiometers with sufficiently low THD+N do exist, but their implementation in a headphone amp raises cost and limits performance. As long as gain is set appropriately, analog potentiometers provide audibly excellent channel balance and THD+N.
For further reading, please see NwAvGuy: All About Gain - The Channel Balance Problem
Solution: Use the lowest gain setting of your amplifier. For particularly sensitive headphones, you may also need to reduce volume at your audio source.