My NOS AD1865 DAC

Status
This old topic is closed. If you want to reopen this topic, contact a moderator using the "Report Post" button.
Is the setup used on my board optimum? will the output of the CS8414 communicate with the SM5842 correctly? Is it better to use a clock on board?
What does the "dither" function do, does it improve sound quality?
I never thought there would be so much to consider when making a DAC.
 
Already said. The clock is in the signal source.
Yes it works. The external clock is the one embedded in SPDIF, extracted and put to MCK.
For other questions I already said that you might want to use some kind of switches or jumpers.

!B+gz4ZwBGk~$(KGrHqMOKjUEzF3vMUJyBM+5pSkqB!~~_35.JPG
 
Last edited:
Can you move out that copper bridge from under the DAC ?
And you have one extra bridge that you could run on PCM - the power for the SM regulator can go under the GND bridge.
I would use bridges for the digital signals from SM to AD and route the outher signals on the PCB. Is eases the future testing with an oscilloscope.
 
I have made some more changes to the PCB. I made the CS8414 output 16-Bit I2S and set the SM5842 to accept the 16-Bit I2S. I disconnected the MCK from the CS8414 because everybody says its high in jitter. I put the SM5842 in Jitter-Free Mode (SYNCN=HI) I'm going to use a 11.2896Mhz 1pps TXCO for SM5842.
How does a TXCO compare to the usual XTAL between the XTI,XTO pins, as the cost of TXCO's is pretty high?
 

Attachments

  • PCB.jpg
    PCB.jpg
    691.7 KB · Views: 350
  • Circuit.jpg
    Circuit.jpg
    582.5 KB · Views: 342
I don't think is a good ideea using a different clock for the SM5842.
The audio DATA will have the same jitter as the MCLK. If you use a different clock instead of MCLK, you still have the incoming DATA jitter. The SM will approximate the location of the incoming data, it will add or skip samples based of the instantaneous difference between the DATA (that had the embedded MCLK) and your local XTAL.
The MCLK tells the DAC when the DATA is ready to be converted. Having an arbitrary clock, with no relation to the incomming data is... wrong, not better. They will have to resynchronize periodically. Even the data sheet says: "Note that resynchronization affects the internal operation and can generate a momentary click noise output."
 
Last edited:
Status
This old topic is closed. If you want to reopen this topic, contact a moderator using the "Report Post" button.