Streaming with Radio Paradise and Spotify stuttering with BlueOS 4.10.13 (Node 2i)
Beantwortet
With the latest update, streaming audio with Radio Paradise or Sptify is unusable. Connections are constantly dropping and the streamer is often bad to reach with the app.
Before the update everything was fine.
Did reset the streamer and wifi without any effect.
No collisions or problems on wifi.
-
Offizieller Kommentar
UPDATED OFFICIAL COMMENT
Thank you all for your patience. Look for an update to BluOS 4.10.19 in the next 48-72 hours. Included in this maintenance release is a resolution to both RadiParadise playback issues and to Spotify not resolving certain file resolutions.
Thanks for your patience and understanding and we do apologise for the inconvenience.
-
Hi Arie
Likely caused by an error in your main router NAT table. BluOS Players reboot twice during the software update process, depending how your router DHCP leases work, this may cause confusion.
Please reboot your router, wait 5 minutes, reboot your BluOS Players, wait 5 more minutes and then relaunch the Apps on your phone.
If problems persist, then please e-mail support@bluesound.com. We can assist with further troubleshooting and give you some pointers on DHCP reservations.
0 -
The player does have a reservation and is restarted several times. The Sophos firewall in front of the network does not indicate any network related errors. Wifi signal is good and used in AP mode only, no collisions.
Just now,, using the desktop app all is fine, the phone could not reach the Node.
After restarting the phone it is fine. I'll try to figure out if the phone app could be
coursing the problem.0 -
Thanks for this - I have escalated you to our Support Crew. They will reach out via e-mail to give you a hand.
0 -
I have submitted a report, i saw this system load that does not appear normal to me.
uptime
15:48:31 up 5:18, 0 users, load average: 7.75, 8.57, 6.50Another problem is that handeling the Streamer with a controller app
becomes almost impossible, whether it's on windows or a phone.Restarted the whole network and changed the chanel. The signal strength
is the same, link rate is ~400Mbps0 -
Hi, i have the same problem. Resetting does not solve the problem. Spotify keeps skipping 30-40 seconds in a single, every 10-15 seconds and the streaming of radio is now impossible, it just keeps looping. Basically the whole system is unusable now. This has been a not so very well tested firmware upgrade to put it mildly…
1 -
Exactly that, and the longer the device is running, the more unusable it gets. Even playing local usb conneted music becomes impossible. It's lile the devive is choking itself.
0 -
The longer the device is running, the weaker the signal gets. It's like wifi is getting fried by the latest software.
It starts at 60db 400Mbps and now is on 72db 292Mbps.
0 -
At this moment it is okay after removing the digital IR input from the device.
Music keeps on streaming and the interface stays responsive.
1 -
Same problem here, also with a Node 2i. It worked perfectly for years, but since the 4.10.13 update it shows the same symptoms as described by Arie and Erik Boerma above.
I rebooted the Node 2i, and my router, and other devices. After restarting the Node 2i, it works for about 1-2 hours, but then suddenly streaming is interrupted, and eventually also broken. Remote control with the app is heavily delayed and eventually does not work at all. Until the next reboot.
I reproduced this with Spotify and mp3 files from a local network drive.
0 -
Same as above. I can’t connect an Ethernet cable as the router is in the basement. I’ve been troubleshooting ever since 4.10.13 was installed on my 2i. I bought a new wifi extender, even switched internet providers (to gigabit service). Nothing has worked, I will try with the IR remote option switched off.
*Update (24hrs later) Still loses connection after 2-3 hours.0 -
Same here; the device cannot be used to stream internet radio anymore.
0 -
If there is a extra device connected, like at my device IR-Digital, try to remove the device and restart the player. To me this works and it is acknowledged as a problem that could be fixe in a future update.
0 -
Unfortunately I do not have any external devices connected. Only an external DAC via the Toslink cable, but that won't help it I think :-)
0 -
Are there any updates for this? I am not happy we are left with an unusable expensive brick in our stereo racks because of an untested firmware update.
0 -
Exactly. If it's not going to be fixed please let us at least know how to rollback to the previous version. Currently it's a sticky (due to the production failures with the plastic cover long time ago) brick.
1 -
Would a factory reset be a workaround? Then, choose only the upgrades prior to 4.10.13? Is that even possible?
0 -
Hi Frank
From the app Home screen, select Settings, Check for Update.
0 -
I updated the player and so far everything looks good.
It's playing internet radio for 2 hours now and it's not stuttering anymore!Update:
I didn't test it long enough. I just left the player on during my workday, and after a few hours the problems appeared again. So no fix so far.0 -
Just wait a few days, Bluesound has confirmed the problem an an update should be available. v4.10.19 is the latest available version now.
- Resolved issues with Context Menus on Custom Stations
- Resolved AutoFill not completing on local library playlists
- Resolved numerous PULSE SUB+ pairing issues with SOUNDBAR+ and POWERNODE
- Resolved secondary players in a group not playing Audio when source is a digital auxiliary input on Primary Player
- Restored Playlist sorting defaults from previous BluOS revisions
- Restored links to recently selected TIDAL and Napster search results
- Resolved issue with incomplete listing of Composers and Works in IDAGIO
- Amazon Music Searches resulted in "Couldn't Load Content Error" now being played
- Resolved issue with Presets being displayed timely when selecting the HomePage in the App
- Resolved RadioParadise playback Issues
- Folders with special characters now displayed when browsing Local Library\Folders
- C700 now waking from StandBy with correct front panel display
-
Playlists which include filenames with special characters now being completed and migrated properly
1 -
Nope. 4.10.19 still doesn’t resolve this issue for me. RP still dropping out.
1 -
Hi Tony W,
Can you give us an update on this one please? Is the issue still being looked at, as the player still not usable at the moment.
Is there any way to rollback the update, as it basically broke a fully functional system.FYI: I updated the player to V4.10.19. It's now a bit better than before, but after a few hours the system becomes unusable. If you need anything to debug this issue I'm more than happy to assist.
0 -
We have made changes in BluOS 4.10.19. In speaking with our Quality Assurance Team, further investigation shows problems are still occurring if you have an optical input device connected to your Player and Auto-Sense Optical enabled.
In Settings, Player, Customize Sources, Optical Input, try disabling Auto-Sense until we resolve this long term.
If you continue to have problems after this, please let our Support Crew know via Settings, Send Support Request.
0 -
I have the same problem with Qobuz and TuneIN. My node 2i only works if I remove the optical input from my node (Connected to my TV). I have Auto-sense disabled. Support discovered a cpu utilization of 96 % in the log files with the optical input connected. BluOS 4.10.19 did not solve the problem.
1 -
So far this temporary workaround seems to be, well, working. I’ve been listening to (mostly) RP for the past 3 days without the symptoms described above, and with my BluOS IR remote enabled. I assume the next update will reinstate the optical input, as I use that to connect my TV.
0 -
The workaround provided by Tony helped me.
The "Auto-Sense Optical" setting was already disabled for me, and my TV was connected to the optical input. I went to Settings -> Player -> Customize Sources -> Optical Input and enabled the setting first and then disabled it again (so: it was disabled to start with!). But somehow this did do something in the player. Now it works properly again.
1 -
I have the same problem but I don't have anything connected to the optical input. Occurs on 4.10.19 as well as earlier versions.
In my case on 4.10.19 once the stop/start begins and after a short while the player becomes totally unresponsive. The app is disconnected and doesn't find the player and none of the buttons on the top (Node N130) do anything. It is essentially frozen and the only way to get it going is to power cycle it.
I only have the HDMI input connected but I did have auto-sense enabled for that input. I've disabled auto-sense and it has worked for several hours. I will monitor it and report back if that hasn't resolved it.
The important point is this bug doesn't appear to require anything connected to the optical input. I've submitted a support ticket with this info
0 -
I have tested 4.10.19 over the past days and everything works for now after the update. The IR/TV is reconnected again days after the update with autosense on IR = off. Spotifi, radio paradise and the interface keeps working. Hope it stays this way.
0 -
@Tony W
Is there any update on this issue? I can reproduce it on 4.10.19 and it does not require anything connected to the optical input. In my setup it occurs when Auto Sense is enabled on the HDMI input
0 -
Autosense could stil be a problem. I leave it of, because the port (IR) with a connected TV works better this way, itś always visible now.
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
30 Kommentare