dzenc using the patchfile here on the loadAR60001.sh or the updated loadAR6000.sh both fail as the patch on the squeezebox thinks it is already applied. I don't know why really, but
I'm gonna do it by hand I think. Just in case someone with less knowledge on linux etc comes across this step :-)...
Announcement
Collapse
No announcement yet.
User Profile
Collapse
-
ralphy my Squeezebox Radio directory looks a bit different than the one from the other test candidate:
Code:# ls -lt /lib/atheros -rw-r--r-- 1 root root 150975 Jan 1 1970 ar6000.ko -rw-r--r-- 1 root root 177073 Jan 1 1970 athwlan.bin -rwxr-xr-x
Leave a comment:
-
Debug Log for Napster tracks says:
Code:Slim::Plugin::RhapsodyDirect::ProtocolHandler::__A NON__ (344) getTrackInfo ok: { ... trackPlaybackFormat => { bitRate => 320, "format" => "AAC", radVersion => 0 },
Leave a comment:
-
Hey, that is pretty cool news moving forward. I can also try "alpha" testing. Knowledge on linux / ssh / etc etc is there, so I could also try to "upgrade" one of my two baby devices.
Just to make sure, dzenc - I only need to follow the instructions in https://forums.slim...
- Likes 1
Leave a comment:
-
ralphy Regarding the Napster streams - yesterday, I also started a playlist playback. The effect was not happening as the next title was played. So, in this case, it does not restarting the streams as it seems. Even though it is another playback URI.
Maybe this observation helps a bit to narrow...
Leave a comment:
-
As I just brought back one Squeezebox Radio yesterday to 8.x community firmware, in general it is working. Enabled the plugin, also for clearing my server log rebooted the server and waited approximately ~1 hour. Afterwards, the firmware update was offered by the server and choosing the firmware update...
Leave a comment:
-
I've send you a video via the dropbox. That illustrates the issue better I hope.
Yes, the 8.x Community Firmware gets stuck a bit after starting a title.
The Stock Firmware (in this case downgraded to 7.7.3 for the test on the "white" squeezebox) shows no issue.
Leave a comment:
-
No. Longer answer:
Stock Firmware works without removing https://github.com/Logitech/slimserv...r.pm#L182-L189
community firmware works now after commenting out the Lines 182 to 189 - with...
Leave a comment:
-
Yep, that solves the issue, mherger . Great.
I've just commented the lines out in the LMS-docker image, restarted it and enabled community firmware again. Installed 8.0.1-r16916 on one of the "baby" devices.
The only issue is: The first 10-15 seconds are sounding...
Leave a comment:
-
I'll send the IP via PN, upload is done. I've restarted the LMS to clean up the 90 MB last server.log ;-)...
Leave a comment:
-
mherger I will upload a server.zip, sure. But just that the "right" data is included, which loggers / parts shall I set to debug before upload? If setting the Rhapsody to debug, there is not much more than these in a repeated manner per title:
[23-05-18 19:40:04.3362] Slim::Plugin::RhapsodyDirect::ProtocolHandler::_go...
Leave a comment:
-
Hm, is there any connection to the RhapsodyDirect Plugin not working since two days ago?
Logfile on Napster / Rhapsody reports 503 errors for two days now.
[23-05-17 17:58:06.8950] Slim::Plugin::RhapsodyDirect::ProtocolHandler::__A NON__ (337) getTrackInfo failed: 503 Service Unavailable...
Leave a comment:
No activity results to display
Show More
Leave a comment: