New Firmware 10.1.0

[thumb5]

This had perhaps be moved to another thread, because it is heading way off topic, but...

First thump5 is right. Jitter is present on every signal path in a computer but the 'normal' programs don't care because they have a protocol to check if every bit that was sent was also received. Nothing is lost but sometimes the programs have to wait until another process/service that interferes with higher priority got its job done. In this scenario some bits/bytes may be delivered later/ealier than it was meant to be. But they just fit in as time is not important.

Hold on a moment: I didn't say anything like that.  In fact I disagree with almost everything you said there.  In particular, time is of vital importance for all digital electronics to work properly - just take a look at the specification of an SDRAM (computer memory) device, for example.  That's why I asked you to explain exactly what /you/ meant by jitter.

On the other hand time is one of the most important things when an audio signal is sent. It has to be a continuous stream. If some bits/bytes come before/after they were meant to arrive the 'tone (or part of it)' is extended over time. We recognise this as distortion/hiss/boomy sound...the tone is stretched...the 'S' in a singers voice becomes a 'SSSS' that's the hiss.

Are you saying that distortion, hiss, boomy sound and sibilance are all caused by timing errors?

My understanding of AIR is that everything that reaches the AIR-Driver (the front door of AIR) is afterwards sorted and send jitterfree/timecorrect through every signalpath of the computer and the network until it reaches the front door of the Dxxx. Then it is converted back into a stream without a time correcting protocol and therefor is prone to jitter again.
The problem as I see it is the signal path from the HDD/SSD up to the front door of AIR. I don't think there is a jitterfree time dependent protocol that holds jitter off this signalpath. But once this jitter contaminated signal passes the front door of AIR the AIR-software takes it as an original signal. The induced jitter can not be seen by AIR.

I don't see why or how you draw a distinction between what happens "in front of" or "within" AIR: it's all computer hardware and software, it all works in the digital domain, and it is all either bit perfect or not.  As Confused said rather concisely, the audio samples can arrive at the Devialet more or less any time relative to each other so long as they are in the correct order and not missing, both of which errors can be detected, and the Devialet will re-clock them synchronously to it's own internal clock.  So no inter-sample time variation before the re-clocking should make a difference to the output from the amplifier.