Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Mac AIR v MiND 180 v Auralic ARIES v totaldac d1 server
#47
Hi

@Antoine (and others...)

Of course, I do not know the details of AIR. Maybe Devialet has found a way to get rid of a mandatory clock on the emitter side.

In any current and known audio protocol using computers, an external clock cannot handle the processor, the Operating System, Ethernet, software, etc. needs for a clock.

As I said above, the external clock masters the transfer process with a "time definition" that goes though the same media as data, in the opposite way, but it cannot master the needed clock for Audivarna, iTunes or Jriver, the Operating System, etc.

This is explained here:

http://www.edn.com/design/consumer/43761...-USB-Audio

for asynchronous USB by Principal Technologist at Xmos.

Among others, the important words, in my opinion, in this article are In order to ensure that the host sends the right amount of data, and not too much or too little...

In my opinion, the fact that this about USB does not make it less relevant for any audio flux transfer protocol.

If the emitter clock was not involved, you should not get any difference between Audivarna/iTunes/Jriver and different Operating Systems.

I apologize for being a bit harsh about those subjects: asynchronous and external clock being the magic bullet for computer audio is, in my opinion, not true. It may improve result, but marketing does not say the whole technical truth about it.

Cheers
Thierry
S1:  Totaldac d1-server, Trinnov ST2-H, Ayon S5, Orpheus Lab 3M, Klinger Favre D56
S2: Trinnov Amethyst,  Ayon Odin III, TAD Evolution One
Reply


Messages In This Thread
CuBox - by Kunter - 31-Aug-2014, 13:49
RE: Mac AIR v MiND 180 v Auralic ARIES v totaldac d1 server - by ThierryNK - 31-Aug-2014, 19:55

Forum Jump:


Users browsing this thread: 7 Guest(s)