I have a question about the re-clocker; So pretty much all modern DACs are async, where the DAC clocks data at its own rate from the USB host (as opposed to receiving bursts of data at whatever rate the HOST sends them);
When the reclocker was in the loop, async DACs still appeared as async to either the Aurender, windows PC, or InnuOs zen (as if the re-clocker was totally not there at all); I assume it's passing back the USB enumeration credentials back to the main USB HOST;
So I guess what I have a question about is the role of the expensive oven controlled 3 parts per billion accuracy oscillator in the phoenix; I assume this clock pulls data from the HOST (music server), but the attached DAC is still operating in asycn mode pulling data according to its own clock-- unless the re-clocker re-configures the operating mode of the USB dac such that the re-clocker pushes data.
Can someone please pipe in that has a clear understanding of what is going on here? TIA!
When the reclocker was in the loop, async DACs still appeared as async to either the Aurender, windows PC, or InnuOs zen (as if the re-clocker was totally not there at all); I assume it's passing back the USB enumeration credentials back to the main USB HOST;
So I guess what I have a question about is the role of the expensive oven controlled 3 parts per billion accuracy oscillator in the phoenix; I assume this clock pulls data from the HOST (music server), but the attached DAC is still operating in asycn mode pulling data according to its own clock-- unless the re-clocker re-configures the operating mode of the USB dac such that the re-clocker pushes data.
Can someone please pipe in that has a clear understanding of what is going on here? TIA!