Sorry i have no schematic , nope only when silence , i`ve already checked all of the psu`s . and they are all ok . I was thinking that the voltage reg my be hissing but checked with other psu and it is the same ...
Or e.g. the UAC2 async controller sends feedback data which are incorrect or unrecognized by the windows UAC2 driver and buffer issues happen on the device.
How did you check they do not occur when music is louder? Are they periodic or random? Do they occur also when no music is being played? When the USB cable is disconnected? How loud are the clicks? Can you record them?nope only when silence
Looks like a clock locking issue then. If the usb stops sending data, the sync is lost. when it starts again it needs to find lock and that gives a click. Keeping sending data (even zeroes) keeps the dac clock in sync.Could it be the software driver putting the DAC into some sort of standby or power saving mode when there is no audio playing?
I bring that up because I had this exact problem with two different commercial USB audio interfaces from Focusrite, a Scarlett 6i6 and a Clarett 2Pre. This happened under Linux. I did not test the Windows behavior. I tried all sorts of OS and audio subsystem tweaks but could not get it to stop. When audio data ceased to flow, after about 15 seconds the unit went into some sort of sleep mode and reset the audio format and rate values. Whenever I later restarted playback there was a pause and a faint pop. It seemed that the sleepy time audio format and rate were not the same as the audio I was sending to the DAC, so it had to change over the clock internally (44.1 vs 48kHz) or something.
In the end I used a "dumb" approach: I wrote a script that used aplay to send /dev/zero data to the DAC using the same format and rate as the audio data I would otherwise send. When I stopped sending my own audio data (via an app I wrote) I fired up the zero-data script to keep the interface alive and running. When I want to send audio data to it again, I just kill the script before doing so (all automated). Works like a charm. Not a universal solution, however!
You could test for this same behavior using some other Windows audio app for some period of time, then killing that and starting to send your audio data again.
Take a look at the I2S bus - does it stop? Some controllers will stop I2S data during silence, and most DACs have an auto-mute mode that is engages. That can create an audible click or pop when the clocks resume and the delta-sigma modulators start again. If only DATA becomes zero and the other clock lines stay active, you can sometimes just put an inverter on the DIN line and that usually tricks DACs from ever going to hardware mute.
You could also test by playing another track in the background. Something ultra quiet, the goal is to have some data on the bus, ideally ±1LSB dither. If that stops the clicking, you have an auto-mute problem.
You could also test by playing another track in the background. Something ultra quiet, the goal is to have some data on the bus, ideally ±1LSB dither. If that stops the clicking, you have an auto-mute problem.
If this description is correct:
then IMO there cannot be zeros-only on the I2S data line. It's very unlikely that a silent part of the recording as described in the quote would produce a longer stream of zero samples, for the DAC power management to kick in. But as I say - IF the description is correct. There have been a number of unanswered important questions in this thread.They appear when there is silence in the music , for example at the end of drum solo , or when singer not singing but the track is playing .
I`ve tried to capture the best way I can and here is the Output of the DAC playing 500 HZ sine , measured one channel , clicks are in both channels :
Don't know that such measurements are helpful. Scope shots of the click noise in the time-domain view relative to USB board MUTE signal might be helpful.
Those spectrogram lines do suggest a buffer issue, not really related to track volume. Is a reasonable UAC2 feedback value sent? Does the driver respect the feedback value correctly? Both can be determined by analyzing the USB packets e.g. using wireshark, with a bit of effort and subsequent processing.
- Home
- Source & Line
- Digital Line Level
- DAC "click" sound when playback starts/stops