sm5842 + 2xpcm63 dac

This old topic is closed. If you want to reopen this topic, contact a moderator using the "Report Post" button.
Joined 2003
Paid Member
You might wonder why no body is reacting here :confused:

There are many threads with hundreds of dicussions on many parts of the design you showed us here, like power supply, the way you designed your pcb, the digital filter vs NOS etc etc....

Still no reactions. I am puzzled too. I did look at the design and what came to mind is that it is evident you have spent a great deal on the power supply, which I think is important too.

Though a few questions:

You are using small coils to filter thze power supply. Have you considered to use them at the output to the IC's to make sure the IC sees high impedance towards to the power supply?

Are you using a low Jitter clock, like the Tent or so? This makes a difference too.

I see no termination of the Output from the PCM63. How are you terminating? I expect passive I/V ?

What type of Electrolytes are you using ? BG's or similar or normal stock ? Here gain is to be made...

For the rest this for sure will be a good sounding DAC, regardless of small details, my experience is, that this combination just sound very good.

Hope you will get some other inputs too :cool:

Hi dddac,

Thanks for your reply !

for the psu I'll use coils between the global psu (about 10-12v) and the regulators to avoid switching noise to polluate it. Since I have a regulator per IC, I thought it wasn't necessary to put coils in it. If you say it'll better, I'll add it.
At least I can make place for it on the pcb and strap if it isnt't better.

For the clock, I will use a tentlabs XO.

for the I/V stage, I have 2 separates boards to test. One is super-pair I/V and the other is a tntaudio output stage with passive I/V + amplification.

the schematic is here:

The electrolytics will be bc136 or os-con I think.

I saw that you've build a pcm63p dac too. How does it sound compared to tda1541 ?

I looked deeper and it seems that you're right.

According to the sm5842 datasheet, it can input i2s (LR alternating, leading data) by puting Inf1n high and inf2n low.

After that, I should hook up the input data to DIL and DIR simultaneously, right ?

If I do so, the input length goes to 24 bits. If the cd-pro2 outputs only 16 bits data, is it a problem as, if I remember well, i2s always outputs 32 bits, filling with zeros ?

thanks rboer for finding this out, I didn't looked at it enough ! :smash:
I2S Bus specification.
The SM5842 will not accept the above and it is also limited to 32/44/48 samples rates. That leaves three options, EIAJ CDROM mode, EIAJ 16bit and EIAJ 18bit. The EIAJ format is LSB justified or trailing data in the SM5842 datasheet. The SM5842 also allows one to select the input data wordlength. In your position, I would set the CD Pro to EIAJ 16bit and set the SM5842 to 16bit input data wordlength and LR alternating trailing data. If you are not using any of the digital processing functions the data should remain at 16bits.
I've just finished the 2nd board version

here it is:


I've added some 100R/100nF filtering on the psu opamp's vref.
I up the thread because I need some help with my dac.

here's the latest schematic:

the dac works well with my cd-pro2 drive, except that I got a click regularly, like an old turntable.

If I set the jitter free mode of the sm5842 off, the click comes more often.

Apart from that, it works well.

the psu's are ok, well regulated at 5v, without excessive noise.

To be sure, I removed the vhc175 and shunt the signals passing through. I also removed the series resistor but it's the same. :bawling:

I can't do any of these, since the dac works in 11.2896 mhz and the drive with 33.8688.

The drive outputs 11.2896Mhz clock derivated from 33.8688, I could use it but I think it won't be optimum regarding to jitter.

a better solution is probably to multiply by 3 the dac clock to feed the drive, isn't it ?

what pll could I use to achieve this ?

This old topic is closed. If you want to reopen this topic, contact a moderator using the "Report Post" button.