(10-Jul-2014, 22:25)Confused Wrote: [ -> ]@Antoine - Understood! I too have the occasional "serious" listening session, but no, I couldn't do it over 3 hours! However, if you could run a 4 hours "background music" session without problems, this would provide useful information. Your feedback would be much appreciated.
Also, I am intrigued by your use of the memory playback option. I can see the logic in using this, and will certainly be giving this a try at the weekend. Thanks for the tip!
I was also thinking of trying Foobar2000, but almost everyone on this forum appears to be running Jriver, and happy with it I'm wondering if trying Foobar would be just be a waste of time?
Sorry it took so long (the post above is on page 2 of this topic!
), but today I have been able to test AIR over ethernet (direct connection PC->Devialet) using JRiver MC 19 on Windows 8.1 Pro again, over a much longer duration. I have been playing music for over 5 hours now and no white noise or other issues, everything is still playing perfectly fine while I type this.
During the first two to three hours I've played files of different bit rates/sample freqs, single songs and full albums and paused plus seeked in songs so I haven't been "careful".
I have no idea where the fault lies in your setups if your PC's and networks are otherwise stable. Did one of you that experience the issue and use Windows reinstall Windows again so in effect start fresh? I know the old AIR installations didn't remove the drivers during an uninstall or upgrade so these could maybe interfere.
Forgot to add: WiFi in the 250 is turned off as is DHCP.
(31-Jul-2014, 18:14)Antoine Wrote: [ -> ]I know the old AIR installations didn't remove the drivers during an uninstall or upgrade so these could maybe interfere.
An interesting idea and easy enough to try. I'll manually delete everything and reinstall AIR. Who knows?
(31-Jul-2014, 18:29)Confused Wrote: [ -> ] (31-Jul-2014, 18:14)Antoine Wrote: [ -> ]I know the old AIR installations didn't remove the drivers during an uninstall or upgrade so these could maybe interfere.
An interesting idea and easy enough to try. I'll manually delete everything and reinstall AIR. Who knows?
I'd like to try that myself. Are all the .dll files under the DevialetAIR folder? I guess we'll also need to delete all the related registry keys.
Antoine, you basically tried what we'd considered a sure recipe for the white noise: a long listening sessions with pausing tracks. The one remaining question I have is: did you pause tracks for a long time? It may sound like a silly question, but I recall that I once got the white noise after pausing the track for several minutes (not immeidately after that, but after a while). Another potential theory is stand-by time, when both Devialet and AIR are on and connected, but no music is playing. (I know this may not sound plausible).
Be careful! I have just tried this, all was going fine, tried to re-install AIR and got Windows "Error code 1006". The "new" copy of AIR just would not install. I must have deleted something I shouldn't have! (I can be very brave sometimes!)
Just spent the last hour trying to get everything back, which due to powers of genius (and much luck), I have. All is well now. (Phew!) Thinking about it, this PC is so new I don't think I have ever had anything other than the latest version of AIR on it! So that was an evening well spent.
@
Confused going to bed before he has a chance to do anything really stupid! (I'll save that one for tomorrow)
@
Antoine - Am I right in inferring that by "direct connection PC->Devialet" you simply have a single Ethernet cable connection direct from the PC to the Devialet, rather than via, say, a switch box that may be connected to a smart TV, Bluray player or anything else? If so, this is interesting, because it is the one thing you are doing differently to myself, and I think @
AlexS also. (correct me if I'm wrong)
I think the set up of users who do not have the issue might prove to be more interesting than those that do!
(31-Jul-2014, 23:29)Confused Wrote: [ -> ]@Antoine - Am I right in inferring that by "direct connection PC->Devialet" you simply have a single Ethernet cable connection direct from the PC to the Devialet, rather than via, say, a switch box that may be connected to a smart TV, Bluray player or anything else? If so, this is interesting, because it is the one thing you are doing differently to myself, and I think @AlexS also. (correct me if I'm wrong)
I think the set up of users who do not have the issue might prove to be more interesting than those that do!
We have users here who have a direct PC --> Devialet connection, but still experienced the problem (see this thread some pages back). So, this can't be it.
@
AlexS, tegarding the pausing of tracks I did, the pauses were short, <1 minute.
@
Confused, yes, you're right about the direct connection; one single cable between playback PC and Devialet. No routers/switches.
What I have not mentioned yet is that I 'tuned' the Windows 8.1 playback machine as much as I could. I however did not record all the changes I made and there have been a lot. There's a minimum of active processes and drivers active. I've disabled or removed everything I don't need in Windows and the BIOS and disabled most of the power saving features of devices except for C1/C3 CPU power states to keep the heat down (my case is a passive cooled case).
Most of the things I did can be found here:
http://www.computeraudiodesign.com/computer-setup/ and here:
http://www.tirnahifi.org/forum/viewtopic...=15&t=2456 Although I didn't blindly follow all their ideas or simply run the scripts. I made a selection to suit my needs.
It may be that if your machines are 100% stable one of those changes "did the trick" here in my situation but I would in no way imply that they should be necessary. Devialet of course has to create a solution that works on a vast range of machines, out of the box and "untuned".
As I said before, I'm running 2012r2 with High End Audio PC. This package turns off everything it can : it even removes the GUI. The major advantage of Antoine's approach is that he knows what happens on his system. The major advantage of buying high end audio pc's solution is that you have a very good supported software, with regular updates. It turns everything off that is not really needed (with a lot of possible selections).
On my system, the tuning did nothing to remove the white noise system. It is too soon to draw conclusions but I'm now playing approx 6 hours in MC19 kernel mode.
As it is Kernel mode, I understand that is always bit perfect, so I switched the Bitperfect setting in AIR-settings. (Please correct me if I'm wrong).
Could some repeat this on her or his system, and give feedback ? Thanks !
I don't think our problem here is related to PC configuration at all (although it's probably a good thing to optimize it for playing music, for other reasons).
Let me put it this way: I did not have the white noise for over a month, with streaming sessions up to about 80 minutes. Then, one day, I keep my Devialet and AIR on and connected for about 5 hours, play music for over 3 hours, and pause tracks (sometimes longer than a minute). And I get the white noise. Can't be a pure coincidence. The PC configuration, which lasted me for a month without any issues, suddenly turns problematic? Highly unlikely.
Antoine's experiment proves it's not the duration of the listening session itself. So, it must be something correlated with long listening sessions. Pausing tracks for a long time? (I do remember that 2 times out of 3 I did pause tracks for a long time, but in one case it took an extra hour of playing to make the problem happen - so, my own hypothesis does not completely convince me).
The theory with obselete drivers was an interesting one, but @Confused's recollection that AIR 2.1.2 was the only version installed on his PC puts it to rest.
George, is Kernel mode the same as ASIO? I did not think Devialet AIR supported ASIO. But I think you can easily verify this:
a) Set the preferred format to 16/44
b) Play high resolution music
c) Check the actual sampling rate in Devialet (I think by long-pressing the source button).
I received an update from Devialet regarding this issue. They stated that they are still working on the issue and that they are gathering information and usage date from customers. I wonder where from, maybe here? So keep the reports coming in, just in case.
It's good to hear Devialet are looking into this one.
Thanks for the update. good to know they're looking into it.
Matt