Project CD Box RS2T and reclocker


Has anyone used a reclocker with a Project CD Box RS2T transport?  What hardware?  Results?

128x128Ag insider logo xs@2xallvinyl

Waste of money! Present day DAC’s have asynchronous input receivers that handle the timing of incoming data. You’d have to go way back to find a DAC that needed a reclocker!

jasonbourne71's avatar

jasonbourne71

364 posts

 

Waste of money! Present day DAC’s have asynchronous input receivers that handle the timing of incoming data. You’d have to go way back to find a DAC that needed a reclocker!

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?

 

@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! 

Jitter from the transport is a non-existent problem solved decades ago!

😂😂🤦‍♂️🤦‍♂️

 

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.

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”

 

jasonbourne71’s avatar

jasonbourne71

369 posts

And yes, I do use a DAC and transport connected by a coax RCA cable.

 

A present-day DAC should handle a signal via USB without problems. But why use that type of connector? I’d say that the onus is on the designer of a DAC having a USB input to make sure that the implementation is correct and jitter is not introduced into the circuitry.

@thyname 

Are you sure about this? On reclocking. USB yes, things like S/PDIF or Toslink, certainly not. 

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:

Museatex (Meitner) implemented the "C-Lockcircuitry back in those days to address poor jitter performance through the S/PDIF.

@jasonbourne71 : what’s your DAC by the way? The sound card in your computer?

 

jasonbourne71's avatar

jasonbourne71

370 posts

 

A DAC is essentially a sound card. That’s all! Put it in a fancy machined-from-a-solid-billet case and you can charge $50K for the same parts as the $100 KTB DAC. Nobody will be able to tell the difference from, say, the real expensive Audio Note DAC! Because Hi-End DAC’s are a good example of confirmation bias!

 


@jetter : claiming to address jitter on the incoming S/PDIF is one thing and reclocking the signal is another, totally different.

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! 

 

 

"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!

@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.

@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!