Hi Keith, just
Sorry I haven't been over this way in a while (and I seem to have misplaced my old username).....
Anyway.... I see some interesting conclusions on this thread - but, unfortunately, most of them aren't technically correct.
Therefore, I'd like to take this opportunity to clarify things.
You will NOT get "noise floor problems" because of a faulty driver. The driver simply passes the bits on from your player to the DAC. A bad driver, or a driver conflict, could potentially cause dropouts, loss of signal, and could even cause your computer to be unable to see the DAC at all, or to refuse to play at certain sample rates if the driver "says" it doesn't support them - but it isn't going to raise the noise floor - it simply doesn't work that way. (In those rare instances when a driver causes "screeching" or "popping" issues, those are actually symptoms of the signal dropping out for very short periods of time, and are not actually "distortion" introduced into the data itself.)
However, various hardware issues could possible cause the noise normally present on the ground of a computer to "bleed through" into the audio, and that noise (on the computer itself) will vary depending on what software is running (because that affects how much current the computer uses and the "patterns" that use follows). With a bad ground noise problem, you can sometimes actually hear the pitch of the noise change as you open or resize windows on the screen. Since Optical inputs are always isolated, and the Coax input on the DC-1 is also transformer isolated, this should only ever happen with USB (unless there's a hardware problem)... and, if your computer is really bad, a $50 USB ground isolator will eliminate it (but you really shouldn't need one).
1) The noise floor on the DC-1 is pretty low (check the specs for yourself), but still not low enough to be inaudible with some very sensitive IEMs. (It will work great with all regular headphones, and MOST IEMs, but wasn't specifically designed to be used with super-sensitive IEMs.)
2) Sometimes you will get ground noise issues due to the way the DC-1 and whatever component you have connected to it are grounded. If you think this might be happening, simply ground the outside shield from one of the DC-1's RCA connectors directly to a similar point on your source equipment; IF you have a ground noise problem, that should make it go away. If it doesn't go away, then you probably don't have ground noise.
3) However, IF you have a noise issue on your DC-1, with all types of inputs, and ONLY when the ASRC is enabled, and grounding your stuff together doesn't help, then you probably have a hardware issue with your DC-1 - and you should call or e-mail us (Emotiva) for an RMA so we can get it fixed for you. In general, switching the ASRC in and out, while NOT changing anything else, should NOT cause a huge jump in noise level and, if it does, then you probably have a hardware problem.
Hi Keith, thank you for your comments and advice. In reference to your last item (#3).
1) The noise only appears when using the ASRC with
no other changes to the system or environment.
2) The noise does not sound like conventional ground loop hum - it sounds more like a discrete digital stutter overlaid over the sound being played. I realize that we are in the digital domain, so this statement may not mean much. However, unlike constant ground loop hum, it is also correlated to the material being played (i.e., only present when there is sound present and a function of that sound, although it is not clear to me what that exact correlation is without much further testing). However, it is not correlated to mouse movement windows opening/closing, hard drives spinning or other computer activity as far as I can tell (I know exactly what you meant when you asked this, because many cheap sound cards do make various spurious sounds that seem to be related to computer activity and video changes.)
3) The noise is only present in the left channel (another indicator that this is not a grounding issue).
4) The amount of noise (i.e., it's amplitude) is a function of the deviation from the 192kHz sample rate (i.e., it is more audible at 44.1 kHz, far less audible at 96 kHz and completely absent at 192 kHz). This refers to the sample rate displayed on the unit,
not the sample rate of the source material. There is
no correlation between the source material sample rate and the actual "played at" sample rate with regard to this noise. In other words it is a function of the configured sample rate for MME or the WASAPI/ASIO negotiated rate (i.e., finally, the rate displayed on the Emotiva unit) and is
independent of the source material's sample rate. To say it differently, you can play 44.1 kHz sampled material at a 44.1 kHz sample rate (i.e., no conversion) with ASRC and hear this noise quite prominently. Likewise with 48 kHz sampled material (as found in the audio material on many Blu-Ray discs) being played at a 48 kHz sample rate as displayed on the unit.
5) It is a problem not with one unit or five units, but either all units or many units (Note: This statement is somewhat anecdotal and based on reading the forum posts of other users affected by this issue).
6) It is independent of the player being used. In fact it can be reproduced with no player at all, but by simply pressing the play button next to the sample rate selection combo box of the Windows playback device settings dialog - see my original post on how to reproduce the problem easily and consistently.
7) The noise is definitely present when the balanced line outs are used, which is how I use the unit. It is most likely present in the headphone output as well, based on other forum posts, but I have not verified).
8) It is not clear if this problem is caused by incompatibility with certain USB chipsets, affects only some units or affects all units at this time, you guys will have to do internal testing to figure that one out.
I would be very thankful if others would follow my steps as posted in a previous post for reproducing this problem and report back if they cannot reproduce it with their unit, so that we can at least know that it is a problem only affecting some units/users/USB chipsets, but
not all. If I can narrow things down further, I will update this post to help with troubleshooting.