(04-Oct-2014, 21:39)ogs Wrote: [ -> ]I opened my 250 today to look at the wifi card. I believe it is the same card I had in the D-Premier. Attaching pictures of the duet card and wifi.
EDIT: I had to reduce the size of the photos to attach them to the post so there is lack of detail. A bit difficult to read text on the various components.
EDIT 2: There is a BB SRC4392I sample rate converter two hops from the XMOS chip. I wonder what that is used for...
Devialet certainly love their SHARCs… Is that a WIZnet Ethernet chip near the XMOS USB device?
(05-Oct-2014, 21:20)thumb5 Wrote: [ -> ]Devialet certainly love their SHARCs… Is that a WIZnet Ethernet chip near the XMOS USB device?
Yes it says iEthernet W5300 - PG082-011 1346
Gentlemen,
1) why are you even looking at the Wi-Fi card? Is it somehow utilized by the Ethernet input?
2) I have very little faith in that tuning the power saving settings of the network adapter might help with this issue. All the evidence I possess indirectly points to a memory corruption issue in either AIR itself, or some shared WASAPI buffer used by both AIR and the player. My reasoning: many of us observed that when the problem happens, unless you reboot the PC (or restart both AIR and the player?), it's likely to happen again within a SHORTER than usual time interval. I personally observed that in most of the instances the problem happened to me, I had forgotten to quit either AIR or the player (FooBar in my cases), prior to putting Windows to sleep, and did not restart them after waking it up. My conclusion: when those apps are awoken from sleep, some of the underlying WASAPI-related memory they're using gets corrupted. Also, to many this problem happens during long listening sessions. Again, this does NOT support the theory of configuration issues, but rather points to memory management. I know this is speculative, but makes more sense to me than the other theories, given the patterns of the problem.
(07-Oct-2014, 15:35)AlexS Wrote: [ -> ]Gentlemen,
1) why are you even looking at the Wi-Fi card? Is it somehow utilized by the Ethernet input?
2) I have very little faith in that tuning the power saving settings of the network adapter might help with this issue. All the evidence I possess indirectly points to a memory corruption issue in either AIR itself, or some shared WASAPI buffer used by both AIR and the player. My reasoning: many of us observed that when the problem happens, unless you reboot the PC (or restart both AIR and the player?), it's likely to happen again within a SHORTER than usual time interval. I personally observed that in most of the instances the problem happened to me, I had forgotten to quit either AIR or the player (FooBar in my cases), prior to putting Windows to sleep, and did not restart them after waking it up. My conclusion: when those apps are awoken from sleep, some of the underlying WASAPI-related memory they're using gets corrupted. Also, to many this problem happens during long listening sessions. Again, this does NOT support the theory of configuration issues, but rather points to memory management. I know this is speculative, but makes more sense to me than the other theories, given the patterns of the problem.
I tend to agree with AlexS on this one. I restart AIR and the player (MC20) before every listening session. I've disabled Windows sleep. I still get the white noise. Only reason I look into the card settings is that Antoine does not experience white noise, but he has a direct ethernet connection to his Devialet. Mine is connected to the main network.
Sigh...I was just looking for differences between my setup and those of the people that experience the white noise. The AIR software isn't a difference, it's the only constant.
Also I've never experienced the white noise, not while using a direct connection, not using WiFi or when connected through a switch. (I've used all three extensively)
Some time ago I've read that to use AIR ethernet you have to have the WiFi card installed. I'm not sure if it's actually used actively/in the signal path when using ethernet.
Good luck in the further troubleshooting process. I'm out.
(07-Oct-2014, 19:06)Antoine Wrote: [ -> ]Sigh...I was just looking for differences between my setup and those of the people that experience the white noise. The AIR software isn't a difference, it's the only constant.
I agree with this
Quote:Also I've never experienced the white noise, not while using a direct connection, not using WiFi or when connected through a switch. (I've used all three extensively)
Then you are quite lucky! And we have good reason to compare settings. Devialet seems to use "forever" so fix this.
Quote:Some time ago I've read that to use AIR ethernet you have to have the WiFi card installed. I'm not sure if it's actually used actively/in the signal path when using ethernet.
I have read the same about the wifi card. Maybe some of the processing is performed by code running on that card, but independent from wifi as such.
Thanks for your effort. I haven't had time to check and compare NIC settings yet.
(07-Oct-2014, 16:21)ogs Wrote: [ -> ]I restart AIR and the player (MC20) before every listening session. [...] I still get the white noise.
@
ogs, now this does contradict my theory, as restarting AIR and the player seem to help me.
What is your pattern? Do you get the white noise only with long listening session (e.g. over two hours long)?
(08-Oct-2014, 15:34)AlexS Wrote: [ -> ]What is your pattern? Do you get the white noise only with long listening session (e.g. over two hours long)?
Not the same every time unfortunately. It can be within 30 min or more than 2 hours. What seems to be a rule is that white noise is more likely if there is a pause/stop of, say, more than 10 min in a session. If the pause/stop is long, i.e. I forget to restart AIR and player from a session the previous evening, I'll have the noise just seconds after I start playing
(08-Oct-2014, 15:47)ogs Wrote: [ -> ]What seems to be a rule is that white noise is more likely if there is a pause/stop of, say, more than 10 min in a session. If the pause/stop is long, i.e. I forget to restart AIR and player from a session the previous evening, I'll have the noise just seconds after I start playing
Yes, I also experienced it once after a relatively long pause (several mins), but was not sure if it was not a pure coincidence. It seems now it was not. Have you reported this to Devialet? It's an interesting piece of information.
(09-Oct-2014, 16:07)AlexS Wrote: [ -> ]Yes, I also experienced it once after a relatively long pause (several mins), but was not sure if it was not a pure coincidence. It seems now it was not. Have you reported this to Devialet? It's an interesting piece of information.
No, I have not had any communication with Devialet on this subject other than what I refer to in post 105 of this thread.