Let me try to help you with that
my understanding of the "relay click" is that it is produced by a circuit suddenly turning off and on and that this is usually caused by a change in resistance. Ideally the driver and/or the design of the circuit should be advance enough to tell the DAC to chill and be more patient before changing stages, but I am not a computer engineer so I can not tell how difficult this is to accomplish or whether a better performance require another physical element on the board regardless of the driver. however this doesn't mean there is nothing we can do to avoid it in our end.
so, we should aim to avoid those sudden changes in resistance. I tried to produce the clicks on my end and noticed 2 scenarios. first, when jumping to other time marks while playing a song it could randomly happened. second, when skipping to a different track. by analyzing how I caused them to start happening we can think of counter measures.
the first scenario is very simple, the click wasn't really so random, it occurred when the change of track time was between segments with a huge difference in volume (which makes sense to assume would also cause a huge change in resistance) , we can fix this by enabling smooth seeking (see attached picture).
the second scenario which I believe you are more concerned about is a bit harder to fix, but still easy. on a bit perfect mode we can not really do cross-fading between track so the only thing we can do is make sure the next track loads really quickly. the reason for this is because of the way audio playback works, every time you open a file (this includes skipping to the next track) the player actually seeks the library and then launches the decoder from zero (as if you had just opened the program), if there is no mixing process involved, this result in the bit stream suddenly having to build the buffer from zero. from the DACs perspective since the bit stream suddenly ended, the DAC might as well have ended its job and switch resistance level. to prevent this try setting the buffer size to the lowest possible (so it gets built and sent to the DAC faster) and hopefully just like that it should be fixed. Once you notice there is no click while changing tracks I encourage you to experiment increasing the buffer size little by little, having a low buffer can produce clicks of its own if you ever encounter a situation where your CPU is really busy, since it could queue and therefore delay building the buffer.
if the problem still persist try installing the KS plugin and run that instead of ASIO. Usually we take foobar's ASIO for granted and forget it has not been touched since 2012 and straight out says on its page that it could be bugged. the KS plugin is even older but in theory should have a faster stream than ASIO since it is as direct as it gets. in any case that's the one I use and works fine for me
View attachment 77154
