Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Version: Firmware 13.1.3 + DOS 2.2.4 Date: 2019-02-12
(28-Feb-2019, 06:19)Chris Marshall Wrote:
(28-Feb-2019, 02:48)awkaplan Wrote:
(26-Feb-2019, 23:47)iamwappie Wrote: It happens only with DSP on. I convert to DSD. Over AIR not an issue but over RAAT the first part of a track is not audible


Yes, I'm still having the same issue (first second or so of track is clipped) and have also noticed some distortion when increasing or decreasing the volume using the ROON remote app.  Resetting my wireless router fixed the distortion issue today.  So far, RAAT has been almost flawless, with AIR a very close second.  I really wish the Devialet could display the dBm wireless signal value in one of the settings menus; the engineers have confirmed there is no way to retrieve the signal strength value from the Devialet.  Slowly tweaking my small wireless network to perfection.


Agreed, some way to see the signal strength would help a lot with setting up decent WiFi.

I used InSSIDer on my laptop to check the strength of the WiFi in the area of the devialet as the best estimate.  It also helps finding the clearest channel to use.

I’m actually using a dedicated WiFi access point at 5Ghz for the Devialet which only it uses, done by using a Netgear EX7300 wireless extender as an access point connected to the main network by Ethernet.  Everything is connected to the same router so it all sees each other no problem.  This has so far been rock solid and since the move to RAAT it happily streams anything including DSD or 24/192.

I’ve probably made too many changes at the same time to be 100% but I’m pretty certain that the sound is no worse than Ethernet at least.

Cheers

Chris

Smart moves.  Unfortunately, using the internal wireless chipset of a laptop or mobile device is a poor indicator of the strength of the signal received by the Devialet, partly due to the Devialet's antenna placement (underneath the metal cover) and general disposition.  I've tried to get chipset and other specs from Devialet, but was simply told (as is stated in the help section) to aim for a signal stronger than -55dBm.  Wireshark seems to identify the chipset as coming from Foxconn. 

The provided router/fiber gateway from AT&T actually provides the RSSI (well, in dBm) of clients and pretty sophisticated packet statistics.  It's a shame that it has a garbage internal antenna and is generally inferior to even the most budget of budget wireless routers.  I was getting -65dBm +/- when using it about 5m from the Devialet with a direct, unobstructed line of sight. 

After disappointment with a much more expensive Netgear Nighthawk with four antennae and the whole works (the router software is criminal), I went back to using the provided wireless gateway briefly (a 3x3 dual band), placing all devices on the 2.4ghz radio (set to 50% power) except for the Devialet, which held the 5ghz channel to itself (100% power).  It worked, but would seemingly cause an "overload" every day or two, requiring a reset of the 5ghz radio.

On a whim, I picked up a fairly basic AC1200 Nighthawk this time, low enough power draw to use an ultra-low-noise wall wart, but has "beamforming" for what it's worth and two external antennas, QoS, and so on.  Same uninformative firmware, and non-DD-WRT compatible.  I shut the gateway radios off and attached the new Nighthawk, replacing the ethernet cables connected to the gateway with shielded Cat6a from Blue Jeans (including from the fiber access point to the gateway) and plugging my ROON NUC into the Nighthawk with an AQ Pearl 0.75m for the time being.  I have this little network cluster raised somewhat but tucked away in a utility closet obstructed by a thin door, against better advice.                 

I have relatively few wireless devices—Nest thermostat, laptop, iPhone, Devialet.  I threw everything except the Devialet on 2.4, Devialet on 5 fixed on channel 161, and it seems to just work, particularly with RAAT (save for the occasional cutoff of the start of a track).  Devialet and NUC are given QoS priority.  That said, it seems all I can do is monitor packets with Wireshark or ping and check for packet loss to estimate the health of the network, besides using my ears.  ROON remote works quickly, but I do get the occasional stutter if I use AIR. 

I may look for a DD-WRT compatible router if I'll be able to get the statistics I want (packet loss tracking, signal strength of client), plus the added ability to auto-reboot daily to stay fresh.  I haven't been able to compare ethernet to wifi sound quality, but prefer the sound of wifi over AIR/RAAT to the USB input using AQ Cinnamon.  If anyone has any suggestions as to how I can judge the quality of my wifi situation, I'm open to them.
Reply


Messages In This Thread
RE: Version: Firmware 13.1.3 + DOS 2.2.4 Date: 2019-02-12 - by awkaplan - 28-Feb-2019, 10:02

Forum Jump:


Users browsing this thread: 4 Guest(s)