Is clicking/popping on dac normal?
Jul 11, 2014 at 11:16 PM Thread Starter Post #1 of 19

imeem

100+ Head-Fier
Joined
Sep 28, 2012
Posts
432
Likes
24
My a/v receiver yamaha rx v377's dac clicks/pops whenever i change music tracks or stop while using wasapi. it clicks even more when i press the test button under Playback device> properties > Advanced (tested on windows 7/8 and 2 different computer, HDMI and optical. However it rarely clicks/pops when im using direct sound and doing other stuff like watching youtube videos. I compare the receiver to my fiio E17 via optical: the E17 doesn't pop or click and when it does (which is uncommon), it's not as loud and noticeable.
 
What is causes it to click? Is it because Yamaha implemented the dac badly? And this isn't normal right and is a valid reason for a refund? 
 
Jul 12, 2014 at 12:45 AM Post #2 of 19
I just posted on this issue with my Modi here (I eventually fixed it by using a powered USB hub):
http://www.head-fi.org/t/640785/schiit-modi-usb-dac/510#post_10702806
 
I would first start by downloading this tool:
http://www.thesycon.de/deu/latency_check.shtml
 
And looking for latency spikes above 500 microseconds.  I would next go through this guide to attempt to optimize your windows system for real-time audio playback.  Pay particular attention to the part where you need to go into your BIOS and disable CPU throttling:
http://www.sweetwater.com/sweetcare/articles/pc-optimization-guide-for-windows-7/
 
If you're still having issues, there are lots of things you can do to try to remedy this, including updating your motherboard chipset drivers, updating the drivers for your network card (usually a likely culprit), and updating your video card drivers.  Lastly, if you are using an Nvidia graphics card, there's a tool to disable its "PowerMizer" throttling capability, which can also cause large latency spikes.
 
Jul 12, 2014 at 2:46 AM Post #3 of 19
That sound is probably your receiver figuring out what kind of audio it's being sent from your PC whenever your PC interrupts the audio stream.
 
With DirectSound, audio is often output continuously, even if that audio is just silence.  WASAPI gives applications exclusive control, so if that application isn't actively outputting audio, it may relinquish control back to DirectSound or stop outputting altogether until it once again has audio to send.  Those switches between DirectSound and WASAPI interrupt the stream so the receiver once again needs to pick up the stream once the PC has started sending it again.
 
The extent of the effect may vary depending upon your computer.  I have my desktop PC connected to a Pioneer Elite receiver.  I have clicks/pops whenever the audio signal changes, like from WASAPI to DirectSound or if I change the number of speakers.  Otherwise there is no issue.  My laptop does like to stop sending audio whenever there hasn't been any for several minutes, so it causes more clicks and pops once it starts sending audio again.
 
Jul 12, 2014 at 10:00 AM Post #4 of 19
  I just posted on this issue with my Modi here (I eventually fixed it by using a powered USB hub):
http://www.head-fi.org/t/640785/schiit-modi-usb-dac/510#post_10702806
 
I would first start by downloading this tool:
http://www.thesycon.de/deu/latency_check.shtml
 
And looking for latency spikes above 500 microseconds.  I would next go through this guide to attempt to optimize your windows system for real-time audio playback.  Pay particular attention to the part where you need to go into your BIOS and disable CPU throttling:
http://www.sweetwater.com/sweetcare/articles/pc-optimization-guide-for-windows-7/
 
If you're still having issues, there are lots of things you can do to try to remedy this, including updating your motherboard chipset drivers, updating the drivers for your network card (usually a likely culprit), and updating your video card drivers.  Lastly, if you are using an Nvidia graphics card, there's a tool to disable its "PowerMizer" throttling capability, which can also cause large latency spikes.

K i downloaded the tool, windows 8 says 1000 ms (which is false according to your link) and windows 7 is below 500 ms. On your second link, i did everything except for the stuff that didn't apply to me or doesn't make sense, such as usb power management, startup items, and disabling sound exclusive mode. I will tr updating my drivers later.
 
So far, there is no difference other than that it pops less/less harsh when i press the test button under Playback device> properties > Advanced. The popping when changing tracks and stopping remains. 
 
Jul 12, 2014 at 2:27 PM Post #6 of 19
  I should note, I think the tool is broken for windows 8 so I wouldn't give it much credence in that instance.

Why even link it when it's known that it doesn't work on W8?
 
LatencyMon (http://www.resplendence.com/latencymon) will work on Windows 8 -- that being said, the popping sounds more like a buffer issue to me, try adjusting that before making a bunch of tweaks you're unsure about.
 
Jul 13, 2014 at 1:57 AM Post #7 of 19
  Why even link it when it's known that it doesn't work on W8?
 
LatencyMon (http://www.resplendence.com/latencymon) will work on Windows 8 -- that being said, the popping sounds more like a buffer issue to me, try adjusting that before making a bunch of tweaks you're unsure about.

i try all buffering size. from the lowest to the highest. On foobars, it made absolutely no difference. on Jriver, it just delays when the popping occurs. kk I will try your link in the morning. 
 
Jul 13, 2014 at 9:33 AM Post #8 of 19
  My a/v receiver yamaha rx v377's dac clicks/pops whenever i change music tracks or stop while using wasapi. it clicks even more when i press the test button under Playback device> properties > Advanced (tested on windows 7/8 and 2 different computer, HDMI and optical. However it rarely clicks/pops when im using direct sound and doing other stuff like watching youtube videos. I compare the receiver to my fiio E17 via optical: the E17 doesn't pop or click and when it does (which is uncommon), it's not as loud and noticeable.
 
What is causes it to click? Is it because Yamaha implemented the dac badly? And this isn't normal right and is a valid reason for a refund? 

 
I don't think it's the DAC used in Yamaha which causes this ... but more like synchronization issue.
 
Which devices in your system are the senders for HDMI and S/PDIF? Are those set to be as default audio playback devices (system playback devices) or are you controlling the connection troug your playback software output settings?
 
Jul 13, 2014 at 11:36 AM Post #11 of 19
  Pops, clicks can be overcome with buffering settings in your player.
 
A.

not in my case. i chose the lowest buffering settings to the highest and it made no difference.
 
Jul 13, 2014 at 3:54 PM Post #13 of 19
  What is your player and are u using windows?
 
Alex

if you have read my post, i'm using windows 8 and 7, but mainly windows 8. My players r Jriver and Foosbar.
 
 
 
EDIT: k i downloaded asio4All and the poping/clicking stopped. Kinda weird. Tho idk if i should continue using asio4all, since it's just a generic version. 
 
Jul 13, 2014 at 5:10 PM Post #14 of 19
asio4all is fine -- if it works, why would you consider not using it?
 
edit: http://www.resplendence.com/download/LatencyMon.exe
 
There's the download link in case you want to give it a shot.
 
Jul 14, 2014 at 7:34 PM Post #15 of 19
  asio4all is fine -- if it works, why would you consider not using it?
 
edit: http://www.resplendence.com/download/LatencyMon.exe
 
There's the download link in case you want to give it a shot.

idk. I don't really like unnecessary drivers/program on my computer. But if  ASIO4all is the only way, so be it. 
 
Here's a picture of latencymon 
 

Users who are viewing this thread

Back
Top