Firmware 3.21 with BubbleUPnP: Update or not?
Posted by: gert on 26 August 2013
Hello,
back from holiday I wonder if I should update my uniti1 from firmware 3.16 to 3.21. Features and drawbacks I did collect from the forum:
* Party mode: I do not need it, as I only own 1 naim device.
* seek2time: I would love it, but it requires the N-Stream app, right? As I have read, it does not work with the Android BubbleUPnP app? (I still do not own an apple device. If I knew the android n-stream app took another half a year I would go and buy one.)
* I have read about an improvement in sound quality. Is it worth it?
* BubbleUPnP gapless support and responsiveness did not improve with the new firmware. Is this right?
* There are reports of errors ("Fault 36" and a micro gaps between tracks?)
So to sum things up: It is more a risk than a benefit for me to update? Did I forget something?
Greetings,
Gert
I use also bubble upnp with my nd5xs (still waiting for nstream for android).
Here is my overview with the new firmware 3.21 and bubbleupnp:
Volume control is still not working, seek to time is also not working.
For me the most important GAPLESS is now working with bubbleupnp, thanks naim for fixing it, but I am still waiting for the android app.
Greetings from Erlangen, Germany
Andi
This would be more than great! Ok, I have found a reason to try the update. Thank you for the info, Andi.
Gert
I use Bubbleupnp and have updated to 3.21. The volume slider works perfectly but seek to time still doesn't, not that I care about that. Any change in sound quality is too subtle for me to hear but as the DSP is updated as part of the package it could well be the case that there is some change.
I found that using Bubbleupnp server ironed out a lot of problems - free and worth checking out if you don't already use it.
I did the update meanwhile.
gapless playback works much better now with BubbleUPnP, but sometimes the track advancing does not work (in most cases after 5-8 played tracks). Either the playback does stop after a track, or a track is played twice then. It seems that this happens more often in case that the screen of the android device (Nexus 4 in my case) is turned off?!
Also there sometimes seems to be an issue with initializing the network or finding the UPnP server from my synology NAS now. If this happens the uniti 1 does not find the server and the BubbleUPnP controller does not see the uniti. After switching around between "CD" and "PC" with the naim remote several times everything returns to normal after maybe one minute.
Another issue was (this happened two times now) that the playback of a track did freeze in the middle of the track. I could not pause, stop or continue the track. After a time out of some seconds it did continue to play the track. As I had never such a problem before this might have to do with new firmware.
As last thing the web radio info screen does not display the played track in case of radio paradies 320k anymore. Other radio channels do not have this problem. Is this a new radio paradise issue that has nothing to do with the naim update?
Greetings,
Gert
Gert
I had some of the same issues as you re track advance and repeating and they were all fixed by installing Bubbleupnp server on my pc. Google for it.- It's a free download and easy to install and set up.
Pev, thanks, I already saw this bubbleupnp server somewhere but did not test it yet. I will check it out. But the drawback would be that I had to keep my PC running. One reason why I bought a NAS was, to not need to turn the PC on for playing music. But it might be an interesting test if it behaves somehow different with this server.
I also have found one reason why gapless play back does stop after some tracks: The Nexus 4 device that I am using does have a really big bug. If the display is turned off and the device falls to sleep, the wlan connection is somehow dropped. See this link (and some followup links in there) for more details:
http://code.google.com/p/andro...sues/detail?id=42272
If I connect the Nexus 4 to the power cable and configure the screen to not turn off, many more tracks are played gaplessly. My new record are 43 tracks without any problems.
But after track 43 (or while playing it?) the uniti did a kind of crashing. It suddenly did read "Streamer Update... Please Wait" on its display. Followed by "Streamer Update Finished. Please Switch OFF". I have to contact naim for this. Maybe it has to do with a problem I had when flashing the new firmware: I thought the uniti was connected via LAN, but it did use WLAN (because of some testings I did some weeks ago). The new firmware did change the WLAN settings, so the uniti could not connect to the network again after a reboot in the update process. So the update could not be finished correctly. This was the first time when I saw the "Streamer Update Finished. Please Switch OFF" message.
Because this message reoccured while watching TV and listening to the TV sound via the naim (so without any streaming involved) I did the firmware flashing again with the naim connected via LAN. This second update did work fine and completely automatically with rebooting the device and resetting the configuration (as it said, but all my settings were kept, so I had not to set up the radio channels again, etc.).
The radio paradise track display is back again btw. So these really seems to have been a RP problem.
What is annoying after the firmware update: The network initialization is really faulty now. It does not matter if connected to LAN (ok, that is using a WLAN bridge on its way) or WLAN directly. Sometimes I have to wait several minutes to get the network set up (while my smart phone has a good working WLAN connection). After switching off and on of the naim and/or switching between some input channels (digital 1, CD, webradio, PC) the network can be set up and the naim works ok again.
Does anybody else have such issues with the new firmware?
Greetings,
Gert
btw.: Which android devices are you using? Also a Nexus 4? Or something different?
I currently think about getting a new Nexus 7 (or because of all the problems and as naim does not give any android app time schedule information maybe an iPadMini after the new one is released the next weeks.)
I am very happy as it seems I could fix the problems described above by doing a reset to the factory settings. (I someone needs to do this: First find the information how to reconnect the remote control to the device ... from the NaimUniti Users Help Guide PDF: "To reset the remote control to the default system code point the remote at the NaimUniti and press the following buttons at the same time: aux, Info (i) and disp." or check this forum entry)
So I hope only the Nexus 4 problem is left...