Jump to content
  • The Computer Audiophile
    The Computer Audiophile

    Asynchronicity: A USB Audio Primer

    thumb_02.jpgRecently the validity of USB as an audio interface has been called into question by some audiophiles. Adding to this was an all-encompassing statement in The Absolute Sound professing that USB interfaces are inferior to S/PDIF interfaces across the board. This had much of the computer audio world understandably bent out of shape. Instead of a disservice to the audiophile community I will attempt to provide accurate information based on facts and discuss different USB implementations. I'll focus mainly on the two different types of USB implementations asynchronous and adaptive. In my opinion any USB, Firewire, S/PDIF, or AES/EBU interface is capable of outperforming the other interfaces on any given day. None of these interfaces is inherently better or worse than the others. It's the implementation of the interface in each product that separates the men from the boys.

     

    [PRBREAK][/PRBREAK]

     

     

     

     

     

    <b>Introduction</b>

     

    Note: <i>I am by no means a leading authority on USB audio and I relied heavily on engineers in the industry while researching this article. Some, but not all, of my sources were Gordon Rankin from Wavelength Audio, Charlie Hansen from Ayre acoustics, and engineers at Data Conversion Systems (dCS). I filter out all marketing terms and bias when analyzing my correspondence with all experts. This article has been in process for several months, long before the TAS article was published in print. This is not a response to the TAS article rather it's an attempt to provide facts about USB audio and arm consumers with more information. Like everything I write this article is wide open to comments and criticism from anyone in the world. I encourage everyone to leave a comment below.</i>

     

     

     

    Universal Serial Bus (USB) is gaining in popularity by the minute among audiophiles seeking to connect a music server to their high-end audio system. One reason for this increasing popularity is the ubiquity of the USB interface. USB is available on virtually every computer manufactured in the last ten years. Plus, it's pretty easy to grasp the music server concept at a high level when all that's needed is to plug a cable into a USB port. Complexity, confusion, and a unique set of compromises arise when audiophiles involve internal cards like the Lynx or RME card that requires installation inside the computer's case. USB on the other hand is nearly fool-proof. A USB cable can only connect to a DAC and computer one way and once its connected the listener will have sound coming from the computer. Granted the configuration may need some fine tuning to get the best sound possible but nonetheless getting sound out of a USB port is quite simple.

     

     

     

    Many audio component manufacturers are currently building Digital to Analog Converters (DAC) with USB inputs. Some manufacturers are also building USB to S/PDIF converters that allow listeners to output audio from their computer's USB port and input that digital signal into a DAC without a USB input. Listeners have also elected to use a USB to S/PDIF converter if the USB implementation on the converter offers better performance or more sample rate options than the USB input on their current DAC. Like every other consumer product in audio and elsewhere, not all USB enabledDACs and converters are created equal. By far the most popular USB implementation method uses what's called Adaptive USB mode. The newest USB implementation used by a select few manufacturers is called Asynchronous USB mode. The technical differences between adaptive and asynchronous modes are very large. In addition there are differences between implementations within each USB mode. For example there are a few different adaptive USB implementations that differ widely in features and sound.

     

     

     

    Before delving into the adaptive and asynchronous USB details, here are some basics to keep in mind. The term USB DAC is a consumer friendly description of a digital to analog converter (DAC) with a universal serial bus (USB) input. This article is about USB inputs and their implementation withinDACs . One must separate the interface from the DAC as a whole to really understand what's going on and to make an educated purchase. A DAC with a so-called poor USB implementation may have the best S/PDIF implementation on the market and vice versa. Thus the sound of a DAC may vary widely based on the input used. The main thing to keep in mind when reading about adaptive and asynchronous USB modes is clocking. Clocking is extremely important with digital audio. Many digital audio experts agree that keeping the clock as close to the DAC as possible, or using a master clock for all digital components is the way to achieve the most accurate sound. In consumer high-end audio as well as professional audio clocking is a major concern and very often external master clocks are used to achieve the best sound.

     

     

     

    Here is one way to think about USB implementations that may help readers more familiar with S/PDIF. If I were a college Professor this is where I would tell my students to never repeat this and never write this on an exam. It is forillustrative purposes only.

     

    S/PDIF has three main specs:

    1. RCA/BNC

    2. Toslink

    3. XLR AES/EBU

     

     

    USB Isochronous audio has three main transfer modes.

    1. Synchronous used primarily for ADC work.

    2. Adaptive

    3. Asynchronous

     

     

     

     

     

     

     

     

    <b>Adaptive Mode USB</b>

     

    Most USB capable DACs today use adaptive mode USB. This is commonly done using a PCM270x chip from TI and to a lessor extent the PCM290x or CMedia parts. The big plus for DAC Manufacturers when using this chip is that no programming is required. The chip can be "popped" into place without extensive R&D, USB audio programming skills, a lengthy time to market, and a substantial amount of money. Big drawbacks to this method are very limited sample rate support (32, 44.1 & 48k), maximum of 16 bit audio, and sound quality.

     

     

     

    Another less common adaptive USB implementation is done using a TAS1020 chip. Manufacturers then have a choice of implementing the chip exactly like the PCM270x without additional programming or possibly using the example code provided by TI, or the manufacturer can purchase code from CEntrance, Inc. to use with the TAS1020. Popular devices using the CEntrance code are the Benchmark DAC1 variants, Bel Canto USB Link, and the PS Audio Perfect Wave DAC. Using the TAS1020 and CEntrance code greatly enhances the USB interface and allows native 24/96 playback without the need for additional device drivers or special software.

     

     

     

    Some creativity is also used with each of the previous adaptive USB implementations. Some manufacturers use jitter reduction techniques such as adding an asynchronous sample rate converter. This can improve jitter measurements quite well but has also been reported to cause some fatiguing over extended listening periods. Some listeners report this as a Hi-Fi type of sound that is initially impressive, but long term listening may confirm otherwise. Another jitter reduction technique is to use an adaptive USB chip that converts directly to S/PDIF inside the DAC. The S/PDIF signal is then passed though theDAC's standard S/PDIF chip that has likely been refined for many years in countless audio products. This conversion technique can be a fairly good compromise between a simplistic adaptiveimplementation like the PCM270x chip from TI and a well done asynchronous DAC design.

     

     

     

    Using either of the aforementioned implementations requires adaptive mode USB. When using adaptive mode USB the computer is the master clock. In layman's terms the DAC is a slave to the computer and has absolutely no control over the timing of the audio. According to digital experts the USB frames in adaptive mode introducesubstantially greater jitter into the signal than asynchronous mode. "In Adaptive mode the computer controls the audio transfer rate, and the USB device has to follow along updating the Master Clock (MCLK) every one millisecond. The USB bus runs at 12MHz, which is unrelated to the audio sample rate of any digital audio format (i.e. 44.1K requires a MCLK = 11.2896MHz). Therefore Adaptive Mode USB DACs must derive the critical master audio clock by use of a complex Frequency Synthesizer. Since the computer is handling many tasks at once, the timing of the USB audio transfers has variations. This leads to jitter in the derived clock." Says Wavelength Audio's Gordon Rankin.

     

     

     

    Adaptive DAC information collected via USB Prober

    ____________________

     

    Audio Class Specific Audio Data Format

    Audio Stream Format Type Desc.

    Format Type: 1 PCM

    Number Of Channels: 2 STEREO

    Sub Frame Size: 3

    Bit Resolution: 24

    Sample Frequency Type: 0x04 (Discrete)

    Sample Frequency: 44100 Hz

    Sample Frequency: 48000 Hz

    Sample Frequency: 88200 Hz

    Sample Frequency: 96000 Hz

    Endpoint 0x01 - Isochronous Output

    Address: 0x01 (OUT)

    Attributes: 0x09 (Isochronous <b>adaptive</b> data endpoint)

    Max Packet Size: 576

    Polling Interval: 1 ms

     

    ___________________

     

     

     

     

     

     

    <b>Asynchronous Mode USB</b>

     

    Asynchronous USB capable DACs are few and far between. Currently Ayre, Wavelength, and dCS are the major manufacturers with asynchronous products on the market. In my opinion the reason for this lack of async DACs is simply because it's very difficult implement this technology. There is a specific skill set required to implement asynchronous USB and it's not common place in high-end audio. Implementing async USB requires a manufacturer to write its own software for the TAS1020 chip and invest thousands of hours on this part of the DAC alone. The limited number of manufacturers who've decided to take on this task instead of going with a plug n' play chip are doing it because they think the performance gains far outweigh the development pain.

     

     

     

    Asynchronous USB essentially turns the computer into a slave device as opposed to adaptive USB which does the opposite. Thus, an asynchronous USB DAC has total control over the timing of the audio. One very important feature of asynchronous USB mode is bidirectional communication between the computer and the DAC. The computer sends audio and the DAC sends commands or instructions for the computer to follow. For example the computer's clock becomes less accurate over a given period of time and can send too much data too quickly and fill up the buffer. Asynchronous DACs will instruct the computer to slow down, thus avoiding any negative effects of a full, or empty, buffer which can manifest itself into audible dropouts and pops or clicks. According to Wavelength Audio the tail is no longer wagging the dog when using asynchronous USB mode. Plus all of this is done without additional device drivers or software installation.

     

     

     

    Asynchronous DAC information collected via USB Prober

    __________________________

     

    Audio Stream Format Type Desc.

    Format Type: 1 PCM

    Number Of Channels: 2 STEREO

    Sub Frame Size: 3

    Bit Resolution: 24

    Sample Frequency Type: 0x04 (Discrete)

    Sample Frequency: 44100 Hz

    Sample Frequency: 48000 Hz

    Sample Frequency: 88200 Hz

    Sample Frequency: 96000 Hz

     

    Endpoint 0x01 - Isochronous Output

    Address: 0x01 (OUT)

    Attributes: 0x05 (Isochronous <b>asynchronous</b> data endpoint)

    Max Packet Size: 588

    Polling Interval: 1 ms

     

    _______________

     

     

     

     

     

     

    <b>Conclusion</b>

     

    There you have it, my attempt to clarify a little bit about USB audio and explain why all USB implementations are not equal. To render an opinion on the state of USB audio one must research the different technologies and listen to different implementations of each technology. Currently in my listening room I have the Ayre QB-9 asynchronous USB DAC, WavelengthCosecant asynchronous USB DAC, dCS Paganini with Puccini U-Clock asynchronous USB converter, and a number of adaptive USB implementations including the Benchmark and Bel Canto implementations using CEntrance USB code. I am comfortable saying that USB is certainly an audiophile interface and it's ready for prime time. I am not comfortable making proclamations that USB is better or worse than the all other interfaces. There are alsodifferences within USB and I do think asynchronous can be better than adaptive USB implementations provided the implementation is impeccable. Readers considering the purchase of a USB DAC or converter must listen to as many products as possible before making a decision. Reading the TAS article and this article are only the tip of the iceberg. Take everything you've read with a bit of skepticism, but don't second guess what you hear while listening to a USB DAC demo. If it sounds go to you then it's good.

     

     

     

     

     

     

     

     

     

    Some Photos of my current Asynchronous USB selection

     

     

     

     

     

    <center>Async Stack</center> <center> <a href="http://images.computeraudiophile.com/graphics/2009/0730/full_02.jpg"><img src="http://images.computeraudiophile.com/graphics/2009/0730/small_02.jpg" alt="Async Stack"></a> </center><center>click to enlarge</center>

     

     

     

     

     

    <center>dCS Puccini U-Clock</center> <center> <a href="http://images.computeraudiophile.com/graphics/2009/0730/full_05.jpg"><img src="http://images.computeraudiophile.com/graphics/2009/0730/small_05.jpg" alt="dCS Puccini U-Clock"></a> </center><center>click to enlarge</center>

     

     

     

     

     

    <center>dCS Paganini DAC</center> <center> <a href="http://images.computeraudiophile.com/graphics/2009/0730/full_06.jpg"><img src="http://images.computeraudiophile.com/graphics/2009/0730/small_06.jpg" alt="dCS Paganini DAC"></a> </center><center>click to enlarge</center>

     

     

     

     

     

    <center>Ayre Acoustics QB-9 DAC</center> <center> <a href="http://images.computeraudiophile.com/graphics/2009/0730/full_07.jpg"><img src="http://images.computeraudiophile.com/graphics/2009/0730/small_07.jpg" alt="Ayre Acoustics QB-9 DAC"></a> </center><center>click to enlarge</center>

     

     

     

     

     

    <center>Wavelength Audio Cosecant DAC</center> <center> <a href="http://images.computeraudiophile.com/graphics/2009/0730/full_08.jpg"><img src="http://images.computeraudiophile.com/graphics/2009/0730/small_08.jpg" alt="Wavelength Audio Cosecant DAC"></a> </center><center>click to enlarge</center>

     

     

     

     

     

    <center>dCS Volume Control Close-up</center> <center> <a href="http://images.computeraudiophile.com/graphics/2009/0730/full_10.jpg"><img src="http://images.computeraudiophile.com/graphics/2009/0730/small_10.jpg" alt="dCS Volume Control Close-up"></a> </center><center>click to enlarge</center>

     

     

     

     

     




    User Feedback

    Recommended Comments



    Take it easy Chris! - I LIKE research, and I LIKE high end audio. You completely misinterpreted my comment! <br />

    <br />

    You like to challenge people who make assertions by asking for the research to support it. In this case I was responding in a positive way with the "bada bing" comment! The writer responded with the research you were requesting - you probably were not expecting that! I did read the research and felt it added to the discussion. <br />

    <br />

    I think you need to take a look at how much of a control freak you are, unless you just want writers that tell you and your little sponsors how great you are!<br />

    <br />

    cheers<br />

    Eric

    Share this comment


    Link to comment
    Share on other sites

    Eric - Your response was exactly what I was expecting. It also says much more about you than it does me. Personal attacks like calling me a control freak are very sophomoric, especially when you include statements like, <i>"... you and your little sponsors ..."</i>. This is classic playground terminology that only takes away from any point you were trying to make. I take pride in the fact I am not a control freak and I encourage all comments whether they agree with me or not. In fact I even added a sentence about that in the article. Take a look around the site here, you'll see many comments that disagree with what I say and add much to the discussion. A one-sided site ads nothing and would be a disservice to this wonderful hobby and hobbyists. I am no preacher and the readers of CA are certainly not in the CA choir. <br />

    <br />

    Asking for research is certainly not challenging people. It's actually trying to get more information in front of those who seek it instead of relying on hearsay. I am actually very happy the links to the research were provided and I expected the links to be provided. Your comment about reading the research and feeling that, <i>"it added to the discussion"</i> was close to something I would have said in college if asked a question about research I really did not read.<br />

    <br />

    Saying you responded, <i>"in a positive way with the "bada bing" comment"</i> is a little misleading. I appeared to me as more of a "gotcha" like you thought I was burned by the fact that research links were posted. It also appeared to me like you rubber stamped the fact that links were provided without reading the material and doing more research which you are a big fan of. More research into this topic including counter arguments to the papers provided clearly leads one to conclude there is no consensus on this topic. I asked for the link from the reader because I wanted to make sure he was not just saying something he had heard through the grapevine. We all know forums are full of ideas that live on forever often repeated without any knowledge of the origination of the idea.<br />

    <br />

    Share this comment


    Link to comment
    Share on other sites

    Thank you Chris<br />

    <br />

    It helps clarifying what we are talking about when discussing USB DACs.<br />

    A part from Wavelength, DCS and Ayre, are you aware of other manufacturers having developped asynchronous USB interfaces, or being in the process of developping it?<br />

    <br />

    Thanks

    Share this comment


    Link to comment
    Share on other sites

    Hi Fyper - NObody I know has developed an asynchronous USB DAC at this level. The EMU 0404 is technically asynchronous via USB, but it's design and implementation are 180 degrees different than Ayre, Wavelength, and dCS. There is a reason the EMU is only $200 even though it's one of the only async USB DACs in the world.<br />

    Share this comment


    Link to comment
    Share on other sites

    http://www.bd-design.nl/contents/en-us/d168.html<br />

    <br />

    Which I think existed earlier than you heard about async USB ...<br />

    I worked on the software myself in 2006.<br />

    <br />

    I like to have this as an example that it is not (or at least not always) the big audio companies who are innovative, but the power of high qualified individuals is.<br />

    You could call this one obsolete already (16/44.1 only), but there will be more ...<br />

    <br />

    Share this comment


    Link to comment
    Share on other sites

    Peter,<br />

    <br />

    Bernt is a good friend of mine and yes this would be considered an asynchronous device. But it is not an ISO Asynchronous device and therefore would require drivers.<br />

    <br />

    I would not call 16/44.1 obsolete a number of my customers think the dynamics of the NOS style dacs sound better than current 24/32 bit units.<br />

    <br />

    Thanks<br />

    Gordon

    Share this comment


    Link to comment
    Share on other sites

    Chris ... you comment on using USB Probe - is this a piece of software I can download from somewhere??<br />

    <br />

    Eloise

    Share this comment


    Link to comment
    Share on other sites

    AD1865.<br />

    <br />

    I don't consider it similar to Firewire. It uses an internal buffer of 64KB (and uses USB 1.1 IIRC).

    Share this comment


    Link to comment
    Share on other sites

    Good to hear. All I know is that I told Bert to find you at the last RMAF and talk a bit about things. I don't think that really happened, you being quite busy.<br />

    <br />

    It is true that it requires its own drivers, and for that matter its own player software. Not a good thing by itself.<br />

    <br />

    <strong>a number of my customers think the dynamics of the NOS style dacs sound better than current 24/32 bit units.</strong><br />

    <br />

    At least I try to keep that up. (but for 24/192) :-)<br />

    <br />

    Peter

    Share this comment


    Link to comment
    Share on other sites

    Peter,<br />

    <br />

    Yes he did stop by at RMAF and we talked for a couple of minutes but it was mass hysteria at the room.<br />

    <br />

    BTW you mentioned that small companies are not the driving force here. I would have to put WA as one of the driving forces and I am not a large company. Actually if you look at computer audio none of the large companies are really prepared for it. They are all using technology from some other company.<br />

    <br />

    In regards to the 24/32 @192.... got me I think a number of people are ripping their cd collection and thinking it's 16/44.1 why do anything more than that.<br />

    <br />

    Also the AD1865 dac chip is an 18 bit part used by Audio Note also. He could just write a ASIO wrapper for .NET and be compatible with a lot of applications.<br />

    <br />

    Thanks<br />

    Gordon

    Share this comment


    Link to comment
    Share on other sites

    Thanks. Hoping that Chris allows for a little more offtopic :<br />

    <br />

    It seems that I suggested that only the big companies can get these kind of things done, but I actually wanted to say just the opposite (also still having in mind the slaughter of A.J. and T.F. at me stating similar before) : the real progress is made by the small companies and even individuals. There is logic in this I think;<br />

    <br />

    Small companies who give all their heart to the product, and individuals just the same, may work 1000s (yes thousands) of hours to get something done, which would not be allowed by the big companies who just have to pay for that, possibly by hireing expensice contractors. The easy example is myself. I must be somewhere at 6000-7000 hours on the development of XX, and against my normal hourly tariff even my own company (ehh, owned by me) would not have paid for such an investment. Not with a selling price of EUR 72, and not with a selling price of EUR 999. It would require sales amounts of over 10,000 and 750 units respectively, and neither is feaseable (on beforehand, when decisions for investments must be taken).<br />

    <br />

    Another kind of example would be the development of a loudspeaker. So, talking about Bert, I must have spent 500 hours at least on helping him with let sounding a horn not as a horn. Again against my tariff he sure wouldn't have spent that. Helping as a friend does wonders here, and friends are never big companies (unless something would be in it for myself afterall).<br />

    <br />

    So, the real innovative stuff not only really happens with individuals (who just need to be very good at their job, like electrical engineering), but it also is logic it goes like that.<br />

    Of course these things happened at the large audio companies in the past, and it just may these days. But economy is not really challenging right now.<br />

    <br />

    Peter<br />

    <br />

    Share this comment


    Link to comment
    Share on other sites

    I noticed BD design lists using any USB cable as a feature. Probably the case though the I imagine the esoteric cable companies will disagree. I also look forward to more ethernet DACs.

    Share this comment


    Link to comment
    Share on other sites

    But of course it is true that just a random cable can be used, since this way of using USB is just about data (and not about audio !).<br />

    <br />

    Do you care about the USB cable when you, say, download pictures from your digital camera ?<br />

    <br />

    Peter

    Share this comment


    Link to comment
    Share on other sites

    While the innovation comes from the small companies I would suggest that it won't take long for the big companies to get involved if they see a market. Perhaps 2010 will be an interesting year for USB audio.<br />

    <br />

    Hi Peter - nice to see you about!<br />

    <br />

    Best<br />

    Andrew

    Share this comment


    Link to comment
    Share on other sites

    It will be interesting to see which way the specialist HiFi manufacturers go.<br />

    <br />

    So far we've seen Bryston and Audio Research go the route of basic USB connection which can easily be improved on. Ayre go the route of licensing WaveLength's async USB technology and soon will have Naim launching their new (first) DAC on which any form of dedicated computer interface is conspicuous by it's absence, preferring to support optical or SPDIF either direct to the motherboard or via third-party interface.<br />

    <br />

    Eloise

    Share this comment


    Link to comment
    Share on other sites

    It's hard to generalize and implementation is everything but if we just look at the DACs on the CASH List the interfaces that have provided sonic superiority are:<br />

    <br />

    Berkeley Audio Design Alpha DAC – AES<br />

    Weiss Engineering Minerva – Firewire<br />

    Devilsound DAC – only Adaptive USB offered<br />

    Bryston BDA-1 – AES<br />

    Benchmark Media Systems DAC1 HDR – AES<br />

    Wavelength Audio Proton – only Asynchronous USB offered<br />

    <br />

    IMO the excellent digital interface cards and software drivers with the Lynx AES16 and Juli@ give them the slight advantage. The CA reviews of these DACs seem to confirm. What I find surprising are the FW DAC owners that use their DACs such as a Weiss DAC2 or FireFace 800 as input to the Berkeley DAC. What is noticeably absent in the above is toslink, which is almost universally said to be an inferior interface in terms of sonics but which many manufacturers seem compelled to implement for CD transports and legacy systems. And obviously the best USB has to offer is excellent 24/96 but nothing higher.

    Share this comment


    Link to comment
    Share on other sites

    The question of whether or not you need to do format conversion and where the clock resides in the chain seems very important but often gets confused in these comparisons. A lot of apples and oranges discussions. <br />

    <br />

    A comparison I would pay money to hear is Lynx -> BADA (or Bryston or whatever) compared to Ayre USB DAC compared to Firewire directly to Weiss Minerva/DAC2 compared to Firewire to Metric Halo ULN-2 or 8. No interface conversions, but still apples and oranges in that the DACs are entirely different. One of the things I am curious about is, independent of the DAC, does USB have "a sound"? Does Firewire? <br />

    <br />

    Does the Lynx card output AES natively? <br />

    <br />

    When feeding a BADA or Bryston DAC, is the Lynx calling the shots (clock wise), or is the DAC the master clock.?<br />

    <br />

    Share this comment


    Link to comment
    Share on other sites

    Hi Dan - When using a lynx with the Alpha DAC or Bryston BDA-1 there is no master clock. The Lynx and each DAC would user their clocks. This is because there is no word clock in or output on the Alpha or BDA-1. The dCS Paganini I am listening to right now has word clock in and out and the Puccini u-Clock has four word clock outputs. Thus I am clocking the Lynx and the Paganini via the U-Clock (master clock in this configuration) when under 96 kHz.

    Share this comment


    Link to comment
    Share on other sites

    For completeness, could an explanation of the use of Bulk USB in audio be given? I have in my mind some idea about this being used as the main USB protocol for external disks but I think it is used in audio too just can't remember in what products. Does it simplify USB communication, not needing asynchronous communication by using a big buffer & reclocking the data out?

    Share this comment


    Link to comment
    Share on other sites

    JKeny,<br />

    <br />

    Consider the amount of time you are investigating this why not just go to USB.org and look it up.<br />

    <br />

    Bulk cannot be used in Audio without a driver. If you use either of the bulk or interrupt endpoints you would have to write a driver.<br />

    <br />

    It actually complicates things using bulk and interrupt because there is no guarantee that the packets will reach the endpoint in a continuous time period.<br />

    <br />

    Only Isosynchronous USB is guaranteed to support Audio and has the highest priority on the buss.<br />

    <br />

    Thanks<br />

    Gordon

    Share this comment


    Link to comment
    Share on other sites

    Just confused by reading various post regarding asyn usb implementation. I think it is implemented in some control feedback to adjust USB to send faster or slower to match with the DAC clock. But what that means is that the incoming data rate is constantly being adjusted and always slightly different from DAC clock. Is it being resampled? What would DAC do to handle this problem. I'm thinking of CD player, the CDP is constantly adjusting the CD spinning rate to have a constant data stream. This process may create a lot of jitter.<br />

    <br />

    Another question, if DAC clock is slower than the speed of player software. With Asyn USB, the USB transmission follow the DAC clock. So we have a player software keep sending data with its own speed, which is faster than the USB transmission rate. What the PC is going to do to handle it?<br />

    <br />

    I think if the player software also slave to the USB transmission speed, it should be fine. But how to make a player software slave to USB transmission speed? Is there such a player.<br />

    <br />

    If we can test whether wavelength DAC is bit perfect, it is going to help understand whether the implementation slave the audio play and USB from end to end. If not, then there would be some resampling by PC which may impact audio quality. <br />

    <br />

    Anybody test whether Wavelength is bit perfect with USB interface?

    Share this comment


    Link to comment
    Share on other sites

    <i>"Anybody test whether Wavelength is bit perfect with USB interface?"</i><br />

    <br />

    I'm not sure you are asking the right question here. There is no way to test such a thing because the output of all DACs is analog. Thus, the bits are "gone."

    Share this comment


    Link to comment
    Share on other sites

    <strong>if DAC clock is slower than the speed of player software. With Asyn USB, the USB transmission follow the DAC clock. So we have a player software keep sending data with its own speed, which is faster than the USB transmission rate. What the PC is going to do to handle it?</strong><br />

    <br />

    Either async or isync, the player sees a buffer. When the buffer is half empty (or whatever is decided for) the player receives a message. Next the player becomes active and fills the buffer. This goes on and on.<br />

    With the async that needs a driver (see Gordon's post) the buffer is at the DAC side (in de DAC box).<br />

    <br />

    Peter

    Share this comment


    Link to comment
    Share on other sites




    Guest
    This is now closed for further comments




×
×
  • Create New...