Bugzilla – Bug 10212
Live365 no longer works in SqueezeNetwork
Last modified: 2008-12-16 11:29:20 UTC
Since last night's SN change: - Live365 no longer available as a menu item in the SN Menu configuration screen, to add to the players' menus - Live365 doesn't work in SN: get "Missing or invalid SqueezeNetwork account. Please check your settings and try again." even though it's still there under "Accounts" and I can access the Live365 site fine using the same user ID and password as before - Live365 removed from top level of "Browse" navigation option -- appears only under "More" (this may have been a design decision on your part, but one I'm curious about -- are you drifting apart from them?) - Perhaps related: the SBB decided to update its firmware all by itself last night, which resulted in the alarm not going off this morning. The alarm wasn't pointing to a Live365 station, so maybe that's an unrelated bug about how you distribute upgrades, and their effect on the Boom (?) Thanks.
Same exact situation for me, on all points. The revamped menu on my SB3 is a huge step backward for SqueezeNetwork. I want to be able to include my favorite music services (not just individual streams) to the top-level menu, just like I could before the SN change. This (for me) includes Live365 and Radioio. Having to access these each time through sub-sub-sub menus and endless scrolling actually subverts my whole intention of buying two SBs in the first place: the ability to browse through hundreds of Internet radio streams with ease. Now it's a chore, not a joy. Perhaps Radioio and Live365 aren't on some sort of payola-style "partners list" with Logitech. So, fine, don't include them in the default menu. But let your users move such services to the main menu as they please.
*** Bug 10348 has been marked as a duplicate of this bug. ***
Browsing of Shoutcast/Live365 fixed in r5316.
Verified fixed in r5316/r24301
I'd like to leave this open because the other half of this bug is still not fixed (able to add Live365 to the top-level menu).
Wouldn't that be covered by bug 10347
No, because it is a regression.