Jump to content

TheExodu5

  • Posts

    4
  • Joined

  • Last visited

  • Country

    country-ZZ

Retained

  • Member Title
    Newbie
  1. Thanks for the input guys. I think in my eyes that I will put this subject to rest. My suspicions seem to have been mostly confirmed (and by someone with experience in developing such systems, thanks exa). I will assume that a USB connection should be error and jitter free under the condition that the connection has a high enough bandwidth to supply the buffer, and if the communication implementation includes proper error correction. I will also assume that the quality of the source USB port power (-V, +V) should be largely irrelevant as long as the DAC unit can properly isolate the receiving USB chip so that the power does not "dirty" the rest of the unit.
  2. How acceptable is it to use volume control in software? Is it even possible using ASIO/WASAPI drivers? I'm asking because I have a Burson HA-160 amp coming in, and while I expect it to be a great amp, I may run into volume control issues. The amp comes with Burson's stepped attenuator for volume control. While it "should" offer superior quality to a potentiometer, there will obviously be some limits regarding volume control. As a result, I'm exploring the possibility of using software volume control to complement it. Any input is appreciated.
  3. Preface: I am a graduated computer engineer and work in the software business. I am also a relative newbie with respect to the audiophile scene. That being said, my father is an avid audiophile and I have had the pleasure of auditioning many setups with him. Recently, I built him a music server and we've auditioned the Meitner, Invicta, and Weiss DAC202 on his B&W 800 Diamond speakers. Being a computer engineer, I am relatively well versed in the technical workings and interactions of computer interfaces. That being said, I do not have any professional experience with the USB interface. Most of my hardware engineering experience is limited to FPGA development, microcontroller programming, and communication with relatively simple interfaces such as serial interfaces. I am not going to discount the possibility that the quality of the USB interface on the PC or that the quality of the USB cable matters. It very well might. I'm here to find out why. To me, used in the intended asynchronous fashion, USB should be able to deliver perfect 1:1 data that is completely devoid of data degradation or timing issues. Take a USB drive, for example. When you transfer data to and from it, nothing happens to it. Error correction and proper back/forth communication in between the drive and the USB's port controller ensures that the data arrives perfectly. If there are any flaws in the data, they are detected thanks to error correction and promptly fixed. Undetected errors are extremely rare, to the point where I have never encountered a corrupt file sent over USB in my lifetime. They're possible, but the error correction used is quite robust and makes undetected errors extremely unlikely. That being said, I realize that the USB interfaces in DACs may not use USB in the ideal fashion. They say they use asynchronous USB, but I'm not sure how it's implemented. Data is buffered into the DAC's USB interface at a rate determined by the DAC's asynchronous USB controller. How big is the buffer? How likely are data errors? I would have to assume that the PCM audio data arrives in "chunks", each chunk representing a bunch of PCM data with attached error correction bits. If the chunk is determined to be erroneous, the DAC would have to request a new chunk from the PC. If it's not retrieved correctly in time, you'd basically have a missing chunk of data, resulting in audio drop outs. After the data makes it through the buffer, it's essentially reclocked by the DAC's master clock, retransmitted and sent to the DAC chip. I've described what I suspect happens using asynchronous USB implementations. If designed in a proper fashion, I see absolutely no reason why the quality of the cable or USB port would effect the sound. At least, there's no reason it should effect the bits and how they're processed by the DAC in any way. That being said, there are a few unknowns to me: can the -V, +V lines in the USB connection somehow "dirty" the DAC's power? I don't know...I'm not terribly comfortable with electrical engineering subject matter. If someone could enlighten me, I'd be forever grateful.
  4. Preface: I am a graduated computer engineer and work in the software business. I am also a relative newbie with respect to the audiophile scene. That being said, my father is an avid audiophile and I have had the pleasure of auditioning many setups with him. Recently, I built him a music server and we've auditioned the Meitner, Invicta, and Weiss DAC202 on his B&W 800 Diamond speakers. I should have rather phrased the question: Why should music players sound different? While auditioning, I did not detect any difference in between Foobar, Media Monkey, and JRiver. My father says he could. Furthermore, I did detect a difference in between optical and USB...USB was more focused, and optical was a bit more diffuse, and I suspect that is due to the added jitter of optical. I'm not going to discount the possibility of there being differences...as I have said I am not an experienced audiophile and I was listening to material that I wasn't overly familiar with, so differences might be hard to pick up. However, I am perplexed as to why there might be differences. So, back to my question, why should players sound different? Does anyone here understand the inner workings of this software? As far as I'm aware, the process should look something like this (assuming no DSPs are used): Software reads WAV -> Software converts to PCM -> Output over an interface using that interface's driver API Where is the subjectivity in this chain? To me, it can only be when the WAV is converted to PCM. How does this conversion occur? Is it done using a custom implementation? Is it done using a standard software library? I'm not particularly interested in answers like "well they sound different to me, so they must be different". I'm interested in the why. I would be very interested if someone with some technical understanding of the subject could chime in.
×
×
  • Create New...