Rank: Member
Groups: Member
Joined: 12/29/2010(UTC)
Posts: 15
Location: United Kingdom
|
OK, I think that I have the back end of my sytem thought through now. It will be Buffalo > Ivy/Legato > Balanaced > Hypex modules. I now need to sort the front end out. As a bit of history, I am building a new all-in-one system to upgrade my existing one seen here: http://www.diyaudio.com/...stid=1403097#post1403097I have a Cambridge Audio 500SE, which I am going to use as a transport. I had planned to build it: Transport > Tentlabs X03.2 low jitter clock > Mux reciever > 12S > DAC. In fact, I have already bought the X03.2 and the MUX. My question: Would it be better to get 12S direct from the transport board, and feed this into the Buffalo module? I would need to be able to switch digital inputs, as I want to be able to add a Sonos, or similar, at some stage. I could use a 4 pole switch in front of the DAC to do this. The down side of this would be that I would need to keep adding spdif to 12S reciever modules for each new input. No big deal. The 4 pole switch may not be optimal also. If I did go down the 12S direct route, would a Metronome, or my Tentlabs clock be beneficial? It has been pointed out to me that the Sabre Dacs reclock themselves already. Edited by user Sunday, January 2, 2011 4:36:12 AM(UTC)
| Reason: Not specified
|
|
|
|
|
|
Rank: Member
Groups: Member
Joined: 11/9/2007(UTC)
Posts: 453
Location: usa
|
For I2S, the bitclock must be 64fs for Buffalo to accept it (whether it is sending 16, 24 or 32 bit data). If your transport outputs 64fs, then you can go straight.
|
|
|
|
|
|
Rank: Member
Groups: Member
Joined: 12/29/2010(UTC)
Posts: 15
Location: United Kingdom
|
Important info, obviously - Thanks.
How do I go about dicovering the bitrate of my Cambridge Audio bitclock?
Should the 12S route provide significantly better SQ, or less distortion/jitter? If not, then I will stick with spdif.
|
|
|
|
|
|
Rank: Member
Groups: Member
Joined: 11/9/2007(UTC)
Posts: 453
Location: usa
|
This is how I did it for another device: link. For now I would recommend you use spdif. BTW, I have the Buffalo II straight to Hypex modules and sounds really good even without the I/V.
|
|
|
|
|
|
Rank: Member
Groups: Member
Joined: 7/21/2010(UTC)
Posts: 75
Location: Colorado
Thanks: 1 times
|
Go I2S if you can and you can keep the I2S lines short. I2S is the native language of the DAC and avoids unnecessary conversions to and from SPDIF, hence, it should perform better, with less jitter.
|
|
|
|
|
|
Rank: Member
Groups: Member
Joined: 11/9/2007(UTC)
Posts: 453
Location: usa
|
barrows wrote:...I2S is the native language of the DAC and avoids unnecessary conversions to and from SPDIF... Buffalo is multilingual :-)
|
|
|
|
|
|
Rank: Member
Groups: Member
Joined: 12/29/2010(UTC)
Posts: 15
Location: United Kingdom
|
Thank you all for your replies.
I am going to stick with my original plan: Transport > Tentlabs XO3.2 Low Jitter Clock using direct spdif > MUX > Buffalo.
Should I use spdif between MUX and Buffalo, or use the 12S option?
|
|
|
|
|
|
Rank: Member
Groups: Member
Joined: 11/9/2007(UTC)
Posts: 453
Location: usa
|
At that point, I think try both since it is very easy to switch.
|
|
|
|
|
|
Rank: Advanced Member
Groups: Member
Joined: 1/7/2011(UTC)
Posts: 65
Location: Russia / Moscow
|
Prompt signal I2s... From a source
In II. Goes simply on cable SPDF???
Is necessary still that that to buy???????
Type of it???
S/PDIF Transceiver
|
|
|
|
|
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.
