Drop outs on all services after update 3.16.1
Completed
As per title, did all the usual troubleshooting, reset router and remove power from the node then reconnect node.
None of the steps solves the dropouts, so the update has caused this.
-
Official comment
UPDATED OFFICIAL COMMENT
Thank you for your continued patience. Look for an update to BluOS 3.16.2 in the next 24-72 hours. Please upgrade to this version and disable Audio Clock Trim in the NODE N130 audio settings.
If problems persist, please select Help, Send Support Request for assistance but we are confident this should resolve the issue.
Thank you for your patience and we aplogise for the inconvenience.
-
I updated my NAD M10 about an hour ago and so far I'm not experiencing any dropouts. However my NAD M10 is using the wired network connection, not wireless so that may be the reason. I didn't see anything in the release notes that might be causing this either. I would try power cycling the node if you haven't done this already to see if it helps. You also didn't mention which music service you were using when you experienced it so you can try another music service just to see if it may be that. I've been listening some over Spotify, Amazon, and Tidal so far since the update.
-Skip
0 -
I updated my Node 2i earlier today after being prompted.
Was listening to a station on TuneIn before updating, no issues.
After updating I now experience drop outs and it is apparent on any service tried, and have also tried the troubleshooting reset router and remove power from the node then reconnect node.Edit: Wired connection to router
1 -
Hi Paul
CHeck your phone or tablet and ensure it is connected to the network, kill and relaunch the App. If problems persist, please e-mail support@bluesound.com
0 -
Dropouts after update to 3.16.1 - ditto: https://support1.bluesound.com/hc/en-us/requests/250615
0 -
Steve - PERFECT! Thank you so much for sending your event log to us - Our Support Crew will reach out to you as quickly as possible to help if all the standard router reset steps are not working.
0 -
This a weird one indeed tried all the troubleshooting options even uninstalling and reinstalling the BluOS app on my android device, that actually made the problem worse instead of random drop outs my dac was losing lock with the node. The node is connected to the dac using a coax cable the cable was checked and worked as it should
Now for the weird part, changing the jitter rejection settings on my dac seems to have "cured" the problem. Still that's not a good sign as the jitter option was set to automatic and now. it's set to high, my TV had drop outs and setting jitter rejection to high solved that.
Luckily my dac has independent jitter settings for each input just odd that an update could cause the node to have issues with jitter that it didn't have before.
0 -
Hi Paul
reinstalling the BluOS app on my android device, that actually made the problem worse
That is coincidental or not related - the App has no control over Player playback. It is merely a remote control providing API commands to the player.
I have not seen any changes to audio processing in the internal notes of the release regarding the NODE (as the NODE does not support DOLBY). That being said - the more log files we receive, the easier it will be for our QA team to see if something is going on.
0 -
Paul's comments about jitter are a concern, and would fit in with what I'm seeing with a higher rate of drop-outs on one system than the other. Unfortunately neither of my two (different) DACs is able to set the jitter rejection level, so I can't test this myself. On the other hand if the jitter characteristics have in fact been degraded by the update, I'm not sure I'd want to cater for it by 'allowing' higher jitter levels.
Any chance of providing (on request?) the previous firmware version while this gets fixed? It would also serve as confirmation or otherwise that it is indeed the update that broke it.
1 -
Hi Steve
Please work with our Support Crew - they will be in touch
0 -
I experienced dropouts on TuneIn stations before, especially after replacing my Node N100 with a NAD T 778 (I am also running two Flex 2i). I was hoping that this would be fixed with the update, but it seems that after upgrading to 3.16.1 there are even more dropouts than before - sometimes there is no problem at all for several hours, but sometimes I even have to restart the T 778...
0 -
@Tony W
This has nothing to do with dolby or my TV, it was merely an example of a device that has poor jitter performance and requires high jitter rejection to stop audio dropouts.
My node N130 is used purely as a transport into my dac from the coax output on the Node to my dac. It was the problem that my TV had that made me think maybe changing the jitter rejection settings on my dac may help and it did.
I was basically trying to find a solution to solve this problem as I'd tried every other method of troubleshooting, reset the router reset the node check all cables and inputs etc
I don't use WiFi as the node is wired by ethernet cable directly to my router, anyway the node is now playing dropout free and I'm back to being a happy node user.
One more thing, the random front light problem seems to have been solved by this update and that wasn't even part of 3.16.1. So it just goes to show that updates can have unexpected consequences.
0 -
Wonderful news Paul - as mentioned Audio Dropouts are almost always network throughput experience but we do want to make sure.
One more thing, the random front light problem seems to have been solved by this update and that wasn't even part of 3.16.1. So it just goes to show that updates can have unexpected consequences.
...or expected ones. It was something our Product Development Team was hoping to resolve for this release. Thanks for #LivingHiFi
0 -
If I may, it would be good if the release notes were more comprehensive to better reflect the hard work your PD team put in rather than hide their light under a bushel.
Anyway thanks for you input.
Now back to the music.
0 -
To confirm Paul's results re. jitter, I briefly borrowed an Audiolab MDAC+ from a friend - this has the required jitter rejection settings available - and was able to eliminate the dropouts by swapping out one of my own DACS and setting the jitter rejection to High. Alas, the MDAC+ is already back with its owner.
I also notice on my own DAC, an Audiolab MDAC (not +), that when there is a dropout, the displayed sampling rate also drops down, though it's too brief to see by how much (it's 44.0nn where nn changes too quickly to read). Otherwise it sits happily at 44.101 Hz.
0 -
Any news when this will be fixed or is a manual downgrade possible?
Since the update to 3.16.1 my Node130 is now totally unusable.1 -
Solution: Manual downgrade to FW 3.14.31
WARNING! I have only tested this on my N130 with FW 3.16.1 installed.- Downgrade to FW 3.14.31 via USB (N130_usb_stick_3.14.31.img)
- In your DNS, router, etc..
Block the following domains to stop the automatic updater (strip out the regex if needed)
- (\.|^)nadelectronics\.com$
- (\.|^)bluos\.net$
0 -
@ R S: Thanks for the info.
Unfortunately this process would be more difficult on my NAD T778 as I found out that manual firmware installation is done via RS232 (seriously, who still has such a cable?). So I hope that there will be a new update soon... My impression is that the NAD is more "affected" by 3.16.1 then my two Pulse Flex 2i, but it's quite difficult to find out because the dropouts are not consistent. As a test I switched off the NAD, and it seemed that the two remaining grouped Flex speakers were running fine, but as I said maybe the problem would have reappeared after some time... Maybe I should have kept my old Node N100 instead of spending 3000€ for the NAD :-(
0 -
@Heinz R
Sadly I can't recommend downgrading any of your units since I don't own any own these models.
There is always a risk of bricking your device, so please keep that in mind.
A USB -> RS232 adapter (and also a RS232 -> RJ45) is always handy to have at home! :-)
Your local electronics dealer should have one in store if they're well sorted.
Some adapters/chipsets are better than others, so you might have to try a couple of USB-adapters before you find one that works if you're unlucky.
For TFTP my weapon of choice is still Solarwinds.
..and here's my informal bug report for the N130
In my case the whole unit was affected and I started wondering what was going on when the HDMI ARC started stuttering directly after the upgrade.
On 3.14.31 HDMI ARC was flawless and I had no lipsync issues at all (Samsung Q9FN).
The stuttering could easily be reproduced with Tidal Connect och Tidal directly via the BluOS app.
I only use the Node as a transport with S/PDIF and for HDMI ARC with an external DAC and I have to admit I didn't bother to test the analog output, Toslink or any other service.0 -
@R S
Completely agree... I definitely won't try to downgrade anything. That could turn out to be very expensive ;-)
0 -
Rather than try to downgrade your player,, which we do not support in any way, as mentioned in the official comment, please follow our recommended troubleshooting steps, namely;
- Reboot your network router
- Wait 5 minutes <- this is vital
- Reboot any (optional) Wi-Fi extenders
- Wait another 5 minutes
- Reboot your Player
- Wait 5 minutes
- Try playing content
- If problems persist, select Help, Send Support Request in the BluOS App
This way we can help resolve the immediate issue, or if it is a larger, unknown, widespread problem, identify the root cause.
Thank you for your patience and understanding.
-1 -
Thank you all for your Support Requests - they have been very helpful.
Our Quality Assurance team has identified a timing issue with digital output that seems to be affecting, but not limited to COAX output in conjunction with older model DACs. They have passed their findings along to our Product Development Team who is investigating. We will be pushing out an updated release as quickly as possible to resolve this issue in BluOS 3.16.1 along with other muting ticks and pops you were hearing in previous releases of BluOS - which this is intended to fix.
Please continue to follow this thread for more updates as they become available.
We do apologise for the inconvienence but thank you for your patience.
1 -
@ Tony W
Thank you for the update!1 -
Tony, thanks for the info! Let‘s hope for the best ;-)
0 -
Thanks Tony. Sounds promising. Was about to dig my old squeezeboxes out of storage.
0 -
I am experiencing dropouts on a brand new topping d90se that I just received today. Node to d90se on both optical and coax. It’s not just older dacs.
0 -
Audiolab 6000A build in DAC has same issues. It's pretty bad. Switched to AUX in for now.
0 -
It's pretty rough on the Burson Conductor as well
1 -
This confirms my experience with a NAD T 778 which definitely is not an old model.
0 -
Thank you all for your feedback - just to clarify;
...seems to be affecting, but not limited to...
That being said, I spoke with our Quality Assurance Team early this afternoon. The Product Development Team has been able to find the root cause of the problem. Our Quality Assurance team is testing possible solutions in hopes of resolving the issue as quickly as possible.
We again thank you for your patience.
0
Post is closed for comments.
Comments
35 comments