My Mu-so debacle
Posted by: robhiston on 29 January 2017
I'm a long term Naim user (currently 250/282/CDX2) and an occasional lurker on this forum.
I thought I would share my recent Mu-so experience here, in the hope that someone could shed some light on why it turned out to be so painful.
I had been intending to enter the world of high quality streaming for some time. My idea was to start with a (semi) portable quality streaming solution which I could move from room to room at home or other venues as required. As I had a bit of rare free time between Xmas and New Year I went along to my nearest Naim dealer to have a listen to the Mu-so. I liked what I heard. The problem was they did not have any new stock, and was advised by the dealer that ordering a new one to arrive in the New Year would involve a £100 price increase. So, somewhat against my normal judgement, I decided to take their offer of purchasing the demo machine.
At home, I first tried it as an AirPlay speaker from my iPad and the good news was that it sounded so much better than my existing portable AirPlay solution.
However, as I started putting the Mu-so through its paces using the various advertised modes and sources, there were numerous problems.
1. I could not pair it successfully from any Bluetooth device I tried - the Mu-so appeared to be announcing itself as an ARM processor rather than a Mu-so. This was eventually solved by doing a factory reset on the Mu-so, when it suddenly began to announce itself as a Mu-so, and began to accept Bluetooth connections.
2. The Naim app on iPad frequently disconnected from the Mu-so, and then "No rooms found". Recovery was sometimes possible by putting Mu-so into and out of standby using the control on the Mu-so. However, sometimes it appeared that the Mu-so had "hung", as it was unresponsive to any control, so a power cycle was necessary to restore function.
3. Streaming from the Tidal service, controlled from the Naim app on the iPad, frequently stopped half way through a track and would not resume. This was often, but not always, accompanied by the app disconnecting from the Mu-so, as above.
4. Streaming internet radio was somewhat more reliable, but was still prone to random app disconnects and mu-so hangs.
The Mu-so on purchase was not running the latest firmware. Assuming a firmware upgrade was probably the key to get it working properly, I tried to update it. But the system would not respond to the upgrade button. I took it back to the dealer, and they, with some difficulty, managed to get it to upgrade. We tested it on the dealer's network with Tidal and it all seemed to work, with no halted streaming and no app disconnects.
Hoping it was now sorted, back at home I was deeply disappointed to find the problems 2. 3. 4. above persisted. These problems occurred whether Mu-so was connected via Ethernet cable or Wi-Fi.
I assumed now it must be a problem with my home network so I therefore decided to try it on two other completely different home networks located at completely different physical locations. However, to my dismay, the results were broadly similar.
After the firmware upgrade, the Mu-so would not stream directly from Tidal at any quality setting. In fact the problem had become worse since the upgrade. The sound stopped exactly half way through any and every track I tried. And I literally mean half way in duration - to the nearest second. However, I could stream from my Tidal account to the Tidal native app on my iPad, and use AirPlay to the mu-so and it worked fine. (I could even stream from Tidal over a 3G internet connection to my iPhone and iPad any AirPlay to the Mu-so and it worked reliably.)
Internet radio would stream to the Mu-so for quite lengthy periods but would eventually fail, sometimes with the app disconnect, sometimes also with a Mu-so hang. (I have two other internet radio capable devices on my home network, a Pure Evoke Flow and a Marantz M-CR611 and these can both play internet radio streams on my home network without problems.)
The network environments on which the Mu-so failed were as follows:
First network (my home network): Router: Billion BiPac 7800N, ISP: Zen Internet ADSL over copper wires. This typically performs at > 17Mbps download.
Second network: Router: BT hub. ISP: BT ADSL over copper wires.
Third network: Router: Virgin Superhub 3. ISP: Virgin high speed fibre optic cable broadband.
I had been intending to enter the world of high quality streaming for some time. My idea was to start with a (semi) portable quality streaming solution which I could move from room to room at home or other venues as required. As I had a bit of rare free time between Xmas and New Year I went along to my nearest Naim dealer to have a listen to the Mu-so. I liked what I heard. The problem was they did not have any new stock, and was advised by the dealer that ordering a new one to arrive in the New Year would involve a £100 price increase. So, somewhat against my normal judgement, I decided to take their offer of purchasing the demo machine.
At home, I first tried it as an AirPlay speaker from my iPad and the good news was that it sounded so much better than my existing portable AirPlay solution.
However, as I started putting the Mu-so through its paces using the various advertised modes and sources, there were numerous problems.
1. I could not pair it successfully from any Bluetooth device I tried - the Mu-so appeared to be announcing itself as an ARM processor rather than a Mu-so. This was eventually solved by doing a factory reset on the Mu-so, when it suddenly began to announce itself as a Mu-so, and began to accept Bluetooth connections.
2. The Naim app on iPad frequently disconnected from the Mu-so, and then "No rooms found". Recovery was sometimes possible by putting Mu-so into and out of standby using the control on the Mu-so. However, sometimes it appeared that the Mu-so had "hung", as it was unresponsive to any control, so a power cycle was necessary to restore function.
3. Streaming from the Tidal service, controlled from the Naim app on the iPad, frequently stopped half way through a track and would not resume. This was often, but not always, accompanied by the app disconnecting from the Mu-so, as above.
4. Streaming internet radio was somewhat more reliable, but was still prone to random app disconnects and mu-so hangs.
The Mu-so on purchase was not running the latest firmware. Assuming a firmware upgrade was probably the key to get it working properly, I tried to update it. But the system would not respond to the upgrade button. I took it back to the dealer, and they, with some difficulty, managed to get it to upgrade. We tested it on the dealer's network with Tidal and it all seemed to work, with no halted streaming and no app disconnects.
Hoping it was now sorted, back at home I was deeply disappointed to find the problems 2. 3. 4. above persisted. These problems occurred whether Mu-so was connected via Ethernet cable or Wi-Fi.
I assumed now it must be a problem with my home network so I therefore decided to try it on two other completely different home networks located at completely different physical locations. However, to my dismay, the results were broadly similar.
After the firmware upgrade, the Mu-so would not stream directly from Tidal at any quality setting. In fact the problem had become worse since the upgrade. The sound stopped exactly half way through any and every track I tried. And I literally mean half way in duration - to the nearest second. However, I could stream from my Tidal account to the Tidal native app on my iPad, and use AirPlay to the mu-so and it worked fine. (I could even stream from Tidal over a 3G internet connection to my iPhone and iPad any AirPlay to the Mu-so and it worked reliably.)
Internet radio would stream to the Mu-so for quite lengthy periods but would eventually fail, sometimes with the app disconnect, sometimes also with a Mu-so hang. (I have two other internet radio capable devices on my home network, a Pure Evoke Flow and a Marantz M-CR611 and these can both play internet radio streams on my home network without problems.)
The network environments on which the Mu-so failed were as follows:
First network (my home network): Router: Billion BiPac 7800N, ISP: Zen Internet ADSL over copper wires. This typically performs at > 17Mbps download.
Second network: Router: BT hub. ISP: BT ADSL over copper wires.
Third network: Router: Virgin Superhub 3. ISP: Virgin high speed fibre optic cable broadband.
These networks all have single point of access and no dodgy range extenders or Ethernet over mains devices. Wireless tests were conducted with the Mu-so within a few feet of the router.
I phoned my dealer and reported the ongoing problems and asked how I should proceed. After some iteration, they told me to phone Naim's Mu-so helpline which I did. After two separate calls, involving lengthy waits on hold and over two hours on the phone with two separate Naim support engineers, during which I was taken through what seemed just about every conceivable combination of reboot, re-install and reset, and was interrogated about my network and internet connection, they eventually conceded the Mu-so must be faulty, and that I should return it to my dealer and exchange for a replacement unit. When I phoned my dealer with this news, again there was some iteration, and the story was there was no new stock available and I would have to wait for new stock to come into the country. Then, to my consternation. I was advised that, as my Mu-so was an ex-demo machine, it was not covered by a manufacturer's warranty at all and Naim would not replace it. Apparently Naim would take my machine back for repair, but only if the faults reported could be reproduced in the dealer's premises. So I was off again to my dealer and the Mu-so was set up on the dealer's network. Lo and behold, it appeared to work perfectly, both with a wired and wireless internet connection.
The only choice presented to me by my dealer at this point was to return the machine and accept a refund of the purchase price. Very reluctantly, as I really wanted the Mu-so to work, I accepted this.
I have to say I have been totally dismayed by this experience with the Mu-so. To find that it works on only one of the four networks I tried in on (and that one just happens to be the dealer's) is extremely dispiriting. As was Naim's seeming reluctance finally to accept responsibility for getting a customer up and running. As a result, my confidence in the Naim brand has taken a severe knock.
I am wondering if my experience is unique. Did I get a faulty unit? Or can a streaming device from a high quality brand like Naim really be so sensitive to network environment, when my other, far cheaper devices, seem quite happy to stream consistently and reliably from the same sources?
I'd be interested in the thoughts and views of those experienced in these matters (though please be gentle as I'm no technical expert in these matters).
I phoned my dealer and reported the ongoing problems and asked how I should proceed. After some iteration, they told me to phone Naim's Mu-so helpline which I did. After two separate calls, involving lengthy waits on hold and over two hours on the phone with two separate Naim support engineers, during which I was taken through what seemed just about every conceivable combination of reboot, re-install and reset, and was interrogated about my network and internet connection, they eventually conceded the Mu-so must be faulty, and that I should return it to my dealer and exchange for a replacement unit. When I phoned my dealer with this news, again there was some iteration, and the story was there was no new stock available and I would have to wait for new stock to come into the country. Then, to my consternation. I was advised that, as my Mu-so was an ex-demo machine, it was not covered by a manufacturer's warranty at all and Naim would not replace it. Apparently Naim would take my machine back for repair, but only if the faults reported could be reproduced in the dealer's premises. So I was off again to my dealer and the Mu-so was set up on the dealer's network. Lo and behold, it appeared to work perfectly, both with a wired and wireless internet connection.
The only choice presented to me by my dealer at this point was to return the machine and accept a refund of the purchase price. Very reluctantly, as I really wanted the Mu-so to work, I accepted this.
I have to say I have been totally dismayed by this experience with the Mu-so. To find that it works on only one of the four networks I tried in on (and that one just happens to be the dealer's) is extremely dispiriting. As was Naim's seeming reluctance finally to accept responsibility for getting a customer up and running. As a result, my confidence in the Naim brand has taken a severe knock.
I am wondering if my experience is unique. Did I get a faulty unit? Or can a streaming device from a high quality brand like Naim really be so sensitive to network environment, when my other, far cheaper devices, seem quite happy to stream consistently and reliably from the same sources?
I'd be interested in the thoughts and views of those experienced in these matters (though please be gentle as I'm no technical expert in these matters).