Poll: Type of "white noise"
You do not have permission to vote in this poll.
I get constant density noise ONLY
22.22%
12 22.22%
I get dropouts ONLY
25.93%
14 25.93%
I get crackles ONLY
11.11%
6 11.11%
I get constant density noise AND dropouts BUT NOT crackles
16.67%
9 16.67%
I get constant density noise AND crackles BUT NOT dropouts
3.70%
2 3.70%
I get dropouts AND crackles BUT NOT constant density noise
11.11%
6 11.11%
I get constant density noise AND dropouts AND crackles
9.26%
5 9.26%
Total 54 vote(s) 100%
* You voted for this item. [Show Results]

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
A lot of hot AIR from Devialet - survey 2
#11
(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
IMac macOS 10.15.3 (no link to Devialet Sad ) / MacBook Pro Retina OS X 10.14.4 / Linn LP12 / Devialet 200 Wilson Benesch Discovery. 
Qobuz Desktop Latest Version / Audirvana 3.2.18 / Audirvana Remote / iTunes 12.9 / AIR 3.0.4 / Wi-Fi / FW 8.1.0 / SAM 50%
Cambridge, UK (Updated 27th February, 2020)
Reply
#12
(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.

Is this a software bug or timing error?

It depends on how the clocks are handled but if they are not locked, and differ in frequency, they may eventually get more than one buffer out of step after a certain time. I would then expect this sort of error message.
The length of time between starting to stream music and the first hesitation would then depend on the difference between the actual computer and Devialet clocks involved, and if they were almost the same maybe one would not get a dropout in any realistic length of listening session. If they differ more maybe there will be a dropout in every session, and even more frequent with HR files.
Devialet Original d'Atelier 44 Core, Job Pre/225, Goldmund PH2, Goldmund Reference/T3f /Ortofon A90, Goldmund Mimesis 36+ & Chord Blu, iMac/Air, Lynx Theta, Tune Audio Anima, Goldmund Epilog 1&2, REL Studio. Dialog, Silver Phantoms, Branch stands, copper cables (mainly).
Oxfordshire

Reply
#13
My main problem is dropouts with 24/192 tracks, 24/96 plays ok.

i have once had white noise after 3 hours but rarely listen so long in one session.

cheers

Chris
Reply
#14
(24-Mar-2015, 13:50)Chris Marshall Wrote: My main problem is dropouts with 24/192 tracks, 24/96 plays ok.

i have once had white noise after 3 hours but rarely listen so long in one session.

cheers

Chris

Hi Chris can you make sure you vote in survey 1 please? Thanks!  Smile

If anyone else hasn't yet voted in survey one please do so ASAP. 

http://devialetchat.com/showthread.php?tid=939

We need a LOT more people to vote. 

Guillaume
Industry disclosure: UK distributor for Shunyata Research

220 PRO, totaldac d1 server with additional external power supply, totaldac d1-seven, Echole PSU for Totaldac, Wilson Audio Sasha 2, Shunyata Research cables, Shunyata Hydra Alpha A10 + DPC-6 v3, Various Entreq ground boxes and cables, Entreq Athena level 3 rack, 2 X SOtM sNH-10G with sCLK-EX + 10MHz Master Clock input + sPS-500 PSU, i5 sonicTransporter w/ 1TB SSD

UK
Reply
#15
(24-Mar-2015, 10:41)Rufus McDufus Wrote:
(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.

That is very interesting. The errors do coincide with the dropouts do they? Googling this seems to be a fairly common problem with programs that perform sound card interaction, but it's odd that the AIR issue is also happening on Windows too. Could it be quite low level close to the sound card drivers? it implies underlying code common between Mac and PC.
I've never managed to get any kind of error log messages on Windows.

I think they are using Qt so yes there is most certainly a lot of common code between the MacOS and the Windows solutions.
MacBook Air M2 -> RAAT/Air -> WiFi -> PLC -> Ethernet -> Devialet 220pro with Core Infinity (upgraded from 120) -> AperturA Armonia
France
Reply
#16
(24-Mar-2015, 10:51)PhilP Wrote:
(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
Yes I have told them and gave them some traces.

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
Reply
#17
(24-Mar-2015, 13:37)f1eng Wrote:
(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.

Is this a software bug or timing error?

It depends on how the clocks are handled but if they are not locked, and differ in frequency, they may eventually get more than one buffer out of step after a certain time. I would then expect this sort of error message.
The length of time between starting to stream music and the first hesitation would then depend on the difference between the actual computer and Devialet clocks involved, and if they were almost the same maybe one would not get a dropout in any realistic length of listening session. If they differ more maybe there will be a dropout in every session, and even more frequent with HR files.

To me this is a software bug that does not handle correctly timing variation and probably encounter some race condition.

I have done real-time development myself, and I can tell you that the vast majority of people, including realtime developers are not handling this kind of problem correctly and do not implement robust solutions.

So I am not that surprise that Apple is in that case.
MacBook Air M2 -> RAAT/Air -> WiFi -> PLC -> Ethernet -> Devialet 220pro with Core Infinity (upgraded from 120) -> AperturA Armonia
France
Reply
#18
I think the sad thing for me is that it has taken a little bit of the buzz I have away from my 200 purchase.
I decided to invest in a new laptop , JRiver and a better ethernet cable as I was looking to use AIR as my primary source until funds become available for a possible streamer solution.

If i had known about the AIR issues I would have gone a different route. To be honest once I had the 200 at home no one was ever going to take it away as i love it.

I am just frustrated that even before I bought the unit I had contacted support a few times with regards to the best way of setting up my 200....at no stage did they alert me to the "white noise " issue. It would not have stopped me going for the 200, but I would have avoided AIR. So I do feel a little let down.

But yes it still sounds WONDERFUL........
Devialet 200 -- Roon Nucleus-- Sonus Faber Olympica 2 -- Tellurium Q Black Speaker Cables --
Chord Qutest -- Niimbus US5 Pro Headphone amp —HifiMan HEK, Abyss 1266TC
Newcastle upon Tyne, England
Reply
#19
Wifi and Ethernet both have cracking issue, sometime it happens quickly (within 15 mins of playback) sometime within hours. Once happen the only solution is to disable then re-enable AIR. NAS and Mac connected via wire. Any combination of Bit perfect and buffer time doesn't matter, I can reproduce the problem with any combination.

Using 2008 Macbook, latest OS, latest firmware for Devialet, latest AIR.


Sent from my iPhone using Tapatalk
Reply
#20
(30-Mar-2015, 23:50)Sevenwong Wrote: Wifi and Ethernet both have cracking issue, sometime it happens quickly (within 15 mins of playback) sometime within hours. Once happen the only solution is to disable then re-enable AIR. NAS and Mac connected via wire. Any combination of Bit perfect and buffer time doesn't matter, I can reproduce the problem with any combination.

Using 2008 Macbook, latest OS, latest firmware for Devialet, latest AIR.


Sent from my iPhone using Tapatalk
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)