![bitperfect 2.0 bitperfect 2.0](https://is.investorsstartpage.com/images/hthumb/bitperfect.top.jpg)
These situations are other overt failures, just like dropouts. Nor would you consider it a failure to be bit-perfect if someone accidentally yanked the USB plug out. Likewise: you wouldn’t consider a power outage during playback to impede the “bit perfect” nature of the playback chain either. It is not a guarantee that no component in the chain will ever experience a catastrophic failure–no-one can guarantee that for you. The “lossless” designation in Roon serves as a confirmation that the playback chain is designed in a way that does not change the bits. This is a catastrophic failure in the context of USB Audio–and unrelated to the idea of whether or not the playback chain is “bit perfect”. If a packet is corrupted and dropped, you will hear a dropout. There are not extra technical implications associated with being “driverless” in general.
BITPERFECT 2.0 DRIVER
All “driverless” means is that a driver came with the OS instead of from the device vendor. Also, there is no such thing as “driverless usb”. You can force re-sampling within XBMC or by using DirectSound, but by going with Wasapi you are getting bit-perfect copies of your FLACs to your DAC. It uses the standard libFlac library and delivers bit-perfect data to your chosen Windows output layer. This is true on both Mac + Windows–there is no platform distinction as you’re implying. Cath, there is no doctoring of the FLAC data at 16-bit in XBMC. While bad packets can be detected and dropped, there isn’t bandwidth allocated for resending them (or, generally, time available to do so) so they are not resent.
![bitperfect 2.0 bitperfect 2.0](https://phimhd1080.com/uploads/images/Chroma%208%20USB%202_0%20WEB%20UP%204(1).jpg)
All UAC 1.0 and 2.0 audio transfers happen in isochronous mode.