I tried the new Air 2.1.3 with the same settings I used before - at very low volume, and as soon as I switched to a 24/96 track the dreaded noise returned. I put ethernet setting to maximum 5000ms and restarted Jriver and Air, and started a new 24-96 track and miraculously it played through until the following (16-44) random song where it spat out another continuous stream of spitting music and noise.
Back to USB and/or Moon Mind 180 until a fix is found.
Cheers,
Graeme
(01-Nov-2014, 09:30)Riddo Wrote: [ -> ]I tried the new Air 2.1.3 with the same settings I used before - at very low volume, and as soon as I switched to a 24/96 track the dreaded noise returned. I put ethernet setting to maximum 5000ms and restarted Jriver and Air, and started a new 24-96 track and miraculously it played through until the following (16-44) random song where it spat out another continuous stream of pink noise.
Back to USB and/or Moon Mind 180 until a fix is found.
Cheers,
Graeme
Graeme, are you playing with WASAPI enabled, or do you manually change the default bit rate in AIR?
How ironic, I didn't have ANY issues with AIR and switched to USB anyway...
(01-Nov-2014, 23:39)AlexS Wrote: [ -> ] (01-Nov-2014, 09:30)Riddo Wrote: [ -> ]I tried the new Air 2.1.3 with the same settings I used before - at very low volume, and as soon as I switched to a 24/96 track the dreaded noise returned. I put ethernet setting to maximum 5000ms and restarted Jriver and Air, and started a new 24-96 track and miraculously it played through until the following (16-44) random song where it spat out another continuous stream of pink noise.
Back to USB and/or Moon Mind 180 until a fix is found.
Cheers,
Graeme
Graeme, are you playing with WASAPI enabled, or do you manually change the default bit rate in AIR?
WASAPI enabled and AIR set at default of 24/192
I have spent much of my weekend trying the new AIR 2.1.3, as well as a short time trying the beta version. The following are my observation, as summarised and sent to Devialet for there further consideration.
In summary, both (2.1.3 & beta version) still suffer the white noise issue. I do have some observations, which may be useful.
For your information, I am using a 3 months old Hewlet Packard "all in one" touch screen PC. This machine is used for general computing duties, as well as for providing music files for the Devialet. This PC is completely standard specification, and has hot been "audio optimised" in any way. Some times I use iTunes, sometimes JRiver MC19. (The point here being that this machine is about as standard as you can get in the PC world) AIR buffer 1000ms
Recently, to avoid white noise, I have been using iTunes, with the sound card GUI set to 16/44.1 and AIR also set to 16/44.1. I loaded 2.1.3, restarted the PC for good order, set everything to 24/192. I then listened to exclusively 16/44.1 material, via iTunes, for maybe two hours, no issues. I then switched to JRiver WASAPI and played a selection of 24 bit material (a mixture of 44.1 / 48 / 96 / 192), after an hour or so, the white noise came.
I restarted the PC, and ran a selection of 24 bit songs using JRiver WASAPI. These were in a playlist, I touched nothing, just let the music play, white noise came in 1 hour 6 minutes. I repeated this, and got white noise in 1 hour 27 minutes.
Out of interest, I tried the "beta" version. Again with 24 bit material from a playlist, white noise in 1 hour 25 minutes. Interestingly, I restarted AIR, and then got white noise in 10 minutes, restarted AIR again, AIR in 10 minutes, this was repeatable endlessly, and the white noise coincided with the PC going into screen saver mode (hence the 10 minutes). I then reloaded the website version of 2.1.3, rebooted, tried the same playlist, white noise in 56 minutes. (the longer sessions have nothing to do with the screen saver mode, as this would have been invoked a considerable period of time earlier) This time with a fuzzy "half white noise half music", which then recovered to normal music, full white noise followed in 10 minutes.
Then I gave up and returned to my 16/44.1 iTunes "safe mode"
One other interesting observation. The first time I ran the new 2.1.3 with JRIver / WASAPI, there was an issue that at the start of a new track, the volume on the Devialet would change to -17. Change the volume, say to -25, then at the start of a new track, the Devialet is set back to -17. Very odd! I looked at the various volume settings in JRiver, the volume control was disabled in JRiver but in the JRiver "Audio Device", "Options". "Devialet AIR WASAPI" "Maximise device volume during playback" was ticked. I un-ticked this, and the issue went away. This must have been selected during my use with the previous AIR, but I had not noticed any issues as it did not appear to do anything. (Curious?)
So, it does not look like the white noise issue is cured......
I also still have an issue with the dual mono configurator. So all in all, not very happy
Disappointing to hear that the white noise problem obviously hasn't been fixed.
(02-Nov-2014, 15:49)Confused Wrote: [ -> ]This time with a fuzzy "half white noise half music"...
Possibly white noise on one channel, with music on the other? Or a half-and-half mixture on both?
(02-Nov-2014, 15:55)thumb5 Wrote: [ -> ]Possibly white noise on one channel, with music on the other? Or a half-and-half mixture on both?
No, just nasty distorted semi white noise stuff on both channels.
@
Confused, you should work for Devialet: if they used this vigorous, multi-variant testing approach, the problem would be fixed by now.
So, the noise scenario seems to be limited to WASAPI, and much exacerbated by higher bit rates. Nothing new here.
Regarding the frequent recurrences, after the white noise happens for the 1st time: it looks like it's not enough to restart AIR; both AIR and the player must be restarted, for a full reset.
My own observations: with WASAPI enabled and 16/44 material, I have not yet run into the issue, with listening sessions up to 90 mins. That being said, the same was the case for me with the prior version of AIR: I only ran into white noise, after putting Windows to sleep with AIR or the player running.
(02-Nov-2014, 16:50)AlexS Wrote: [ -> ]@Confused, you should work for Devialet:
I think I am at the moment, it's an odd deal though, no salary but I do get to pay £20K for a system that doesn't work properly.
(02-Nov-2014, 16:53)Confused Wrote: [ -> ] (02-Nov-2014, 16:50)AlexS Wrote: [ -> ]@Confused, you should work for Devialet:
I think I am at the moment, it's an odd deal though, no salary but I do get to pay £20K for a system that doesn't work properly.
Well, just imagine: if the white noise went away for good, and this thread became useless (which it apparently is, anyway, but in a different sense), I for one would stop posting at this forum. What else is there to discuss? Devialet sounds great, and no one will convince me that SAM makes it better
Back to the white noise. To complete the picture, have you tried 16/44 with JRiver and WASAPI for an extensive period of time? I wonder if this combination behaves worse for you than iTunes with WASAPI off.
BTW, the release notes for AIR 2.1.3 don't explicitly mention any white noise bug fixes. So, it seems Devialet should be immune from criticism...