USB on the other hand, gives me the most flexibility here. I have some nice DSD128 that I really love…
I really believe that they know exactly what they are doing (because this is ALL they do)… it’s their ONE core competency.Ĭoming back to placing an optical break in the Ethernet feed: By using Matrix and I2S, this is not necessary the case (and who takes care of the Ethernet implementation?) Also, going optical on the Matrix (Toslink) will limit my possibilities streaming DSD files. The opticalRendu is Sonore’s third generation of audio optimized streaming platforms (not counting the SonicorbiterSE). So you should hand this problem over to people, who do have deep knowledge of the problem and deal with Ethernet based audio streaming for years (experience). Looking at the statements from Ted, it seems that having a rock solid Ethernet solution, that fits audiophile requirements, is absolute key. By focussing on the ONE core competency, you have full control of the product. No cumbersome additional software.Ĭontrol. Having separate devices per function will also increase flexibility. Implementing Bridge functions means dealing with additional software complexity (server/player software, Roon endpoint etc.). Keep it as far away from the DAC as possible or when used as service interface, allow it to be disabled.Ĭomplexity. Get rid of every component, that could introduce noise. This is my own speculation, but I believe that there are the following reasons for leaving Bridge functions out of the future TSS DAC:
#Ploy sinc xtr vs closed form hqplayer upgrade#
It will be able to be disabled in the hardware for people that don’t want the associated noise (or hassle.) Conversely there will be an option to use it to upgrade the software, one again optional and controlled by the user. There will be an optional Ethernet connection to the display. Paul definitely likes the idea of an app as well.