24-Mar-2015, 14:57
(24-Mar-2015, 10:51)PhilP Wrote:Yes I have told them and gave them some traces.(24-Mar-2015, 08:09)Jean-Marie Wrote: I have short drop outs only, quite infrequent: no more than once of twice a day for a 5 to 6 hours listening.
Everytime, I have been able to relate that to the known bug in MacOS related to "kernel[0]: IOAudioStream[0x4d83000]::clipIfNecessary() - Error: attempting to clip to a position more than one buffer ahead of last clip position (d24,39)->(d57,3b5)"
This is frustrating because the problem belongs to Apple but they ignored it for years (it is known to appear on some USB interfaces as well as firewire) and therefore, unless Apple corrects it which is unlikely, the only solution for Devialet is to work around it.
Jean-Marie,
I wondered whether you had told Devialet about this Apple bug and if so what their response was?
Philip
This is not something easy because it is probably related to the relative scheduling between the driver in the kernel and core-audio. Probably some race condition, but if I understand correctly there is not much you can do as a driver developer because it is all handled by the OS.
MacBook Air M2 -> RAAT/Air -> WiFi -> PLC -> Ethernet -> Devialet 220pro with Core Infinity (upgraded from 120) -> AperturA Armonia
France
France