AIR1 v AIR2 v Spark

[AlexS]

For Antoine, you do not always need to know exactly what is happening "inside" to try to solve a problem. As I say sometimes, you do not need to be God to cure people.

I applaud your willingness to help but I'm staying out of this discussion, it's bad for my blood pressure. I've already seen too much nonsense and utter BS written on the AIR issues (which never plagued me BTW) and am seeing it again already.

Good luck to you all.

PS: I do agree with PhilP, the white noise issue is very unlikely a network issue but rather a timing/buffer corruption issue. Playback is the real time process, not the network part as that's only used to fill the buffer.

I would also like to register my agreement with Antoine and PhilP on this matter.
We should always differentiate white noise proper (continuous loud hissing sound, which does not self-correct itself, unless AIR is restarted) and occasional drop-outs/stutters. WN is not likely to be related to networking. I think we have the following evidence, which supports this hypothesis (at least, for Windows; I can't speak for the Mac):
1) The latest beta version of AIR improved things for, at least, some users, and that version changed the implementation of the timer (or rather how time is obtained from the Windows OS?)
2) Disabling the screen saver helped other users. But this has nothing to do with network traffic, but rather CPU load.
3) Others observed that migrating to Windows 10 fixed the problem.
To sum up, it's as if under certain conditions, perhaps involving extra CPU load (or maybe some background process like Windows Update kicking in, when it thinks the CPU is idle, and causing the processor to abruptly shift from the power saving state to the regular one), AIR starts sending gibberish to Devialet.