I can see where using a general purpose computer in bridged mode could make sense. In this case the computer is used as a server, this means something like Roon core only on computer, this connected to a streamer, various companies make these, in my case I use Sonore OpticalRendu, this becomes Roon endpoint. This segregates or isolates dac from noisy and inferior clocks in general purpose computers. Still, I've compared my custom build server/steamer as both Roon core and endpoint (unbridged mode) to the bridged mode with the Sonore, bridged mode easily betters the unbridged setup. Keep in mind, my custom build sever/streamer uses Enterprise level RAM and hard drive, passive cooling, high speed processor, Euphony OS, $6K linear power supply. Bottom line, IME segregating a general purpose computer from dac with a basic streamer only gets you part way there, YMMV.
Any audiophile use computer (MacBook) as your audio streaming source?
I rarely see any audiophile talking about streaming audio digital sources from a computer. I understand MacBook can accept native lossless formats form all the various platforms, and it can store unlimited music files in any format, so supposedly it’s the best source, and the digital file is the most purest before it’s fed to the dac. Anyone compared the sound quality of computer vs other audio streamer?
- ...
- 151 posts total
@yyzsantabarbara Thank you for the additional info, however on a conceptual level I am still confused. I may just be missing something obvious. How can fiber constitute a "moat" when it is merely a conduit without filtering abilities of its own? If a noisy signal enters a fiber run, isn't it delivered identically at the other end, noise and all? And if SFP fiber does in fact erect a "moat" protecting a system from noise, why wouldn't coaxial and toslink do the same? Fiber won't pick up noise along the way like copper might, but what about the noise that entered the signal upstream of the first endpoint?. Fiber audio networking is new to me, so these may be stupid questions. If so I do apologize. |
@devinplombier Fibre optical cables are made of glass and can be very long; cheap too.Fibre is used to transmit data across large distances reliably, Glass cannot carry analog noise that is in the network, a network is likely ethernet cable based for the most part, like my home network. I use fibre cable as the last bit before the DAC. I think jitter is another matter to be concerned with, but most competent DACs (low cost) can handle jitter these days. I do not know how that relates to streaming. I do not care since the DACs can deal with it. Toslink is likely also made of glass, but it is a different type of cable and cannot travel long distances. Toslink also has some issue related to digital transmission that I do not know enough to explain. I do use Toslink in my office system for 1 DAC input and SPDIF for another DAC input. The Toslink is for my noisy computer (YouTube and sports) and the SPDIF is for CD/SACD's. The SPDIF sounds great, as good as the streaming. The Toslink is not that great, nor is the source. I am just some person spewing an opinion here however, there are some heavy-duty DAC designers that are stating the same thing. PlayBack Designs Andreas Koch for one. BTW - Lumin were the first DAC company to support fibre natively, they actually did this after reading posts on an online forum years ago about the advantages of fibre.
|
@yyzsantabarbara - the problem with Toslink is that a) it is limited to 24/96 and b) there is no error detection or correction like with USB. USB is way more modern, I am running 15 ft USB just fine, it is not worse than a twisted pair. |
@yyzsantabarbara No! Most DACs can somewhat handle jitter, but most if not all DACs can significantly benefit from a DDC and/or external clock. Michael Lavorgna has written here recently how adding an external clock, even to a very accomplished DAC, can greatly improve performance. Most DACs do not even have an OCXO clock much less completely deal with jitter, so to say most low-cost DACs can just somehow “handle” jitter is just nonsensical and incorrect. You’re inappropriately minimizing a significant issue here that should not be minimized. |
- 151 posts total