🤯🤯🤯🤯. Pants on fire 🔥
@thyname : I don't ask you what car you drive. I don't own a computer. I use a DAC that placed fifth on ASR's list of over 100 DAC's. I place my trust in science and proper engineering - not golden ear voodoo! |
@thyname : the input receivers of all present day DAC's re-clocks the incoming data. So no need for another black box inserted between transport and DAC. |
"C-Lock" sounds like what Wavelength was using as the input receiver back around. the same time! The cable wasn’t the problem though. It was getting the transport and DAC to sync up. A major problem which before the asynchronous input receiver was handled by the IS2 circuitry/cable. IS2 is practically extinct these days! |
|
@jasonbourne71 : what’s your DAC by the way? The sound card in your computer?
|
You are all more aware of the technology of these units, but from the description of my ancient (but modded) Museatex Meilor Bitstream DAC first introduced in about 1992:
|
😂😂🤦♂️🤦♂️
Are you sure about this? On reclocking. USB yes, things like S/PDIF or Toslink, certainly not. Which is what you use with your $16 eBay “transport”
|
@thyname : If I remember correctly Gordon Rankin of Wavelength built the first asynchronous DAC back around 1992-93. No need then to sync the transport and DAC to reduce/eliminate jitter (uncertainty in timing). The input receiver of that DAC and all present day DAC's re-clocks the incoming data. So no need for a clock between the transport and DAC. Jitter from the transport is a non-existent problem solved decades ago! |
Including the CD transports? In other words, are you saying a connect a CD transport to my DAC, via S/PDIF, will the clocks in my CD transport and DAC be synced?
Do you own a DAC?
|