Announce : BBC Sounds Plugin

[d6jg]

Well, to be fair, Material sometimes shows an empty area briefly - if a list is scrolled too fast, as the Javascript has no time to catchup (affects list more than grid). With Squeezer's 'Loading' issue, I reported that years ago (before starting on Material), and the simple fix was to fetch more items in one go. My issue is closed as fixed, but I still see it. Anyhow, this is off-topic for this thread.

Craig does himself a disservice. Material is vastly superior to other attempts at a decent modern UI. It also has the big advantage of being the same no matter what device you use it on.
I’ve always been a big fan of iPeng and I still use it a lot but now as a player only on iOS and control with Material on the same iOS device.
In the office I use Material as an app on my PC to control the Office players.
At home I use Material on my iOS devices to either control players plugged into HiFi etc or the iPeng instance on my iPhone (coupled with Audioquest Dragonfly and decent headphones) when SWMBO is watching carp TV.
There is a big + when every control point works the same way,

[The Groundsman]

Craig does himself a disservice. Material is vastly superior to other attempts at a decent modern UI.

100% agree. I too used to use Squeezer but the android APK for Material is quite excellent

[scooper]

No sound

I've been unable to get any programs to play on BBC Sounds running on a Synology LMS. Given that I know that isn't supported anymore, I have set up a Raspberry Pi 4 running piCorePlayer. I have LMS 8.1.1 and version 2.13.3 of the BBC Sounds app running. I am still unable to listen to any programming. Whilst I can browse the app, pick a program through Stations and Schedules and 'play', the time progress bar shows a time of 0.
Given that this was happening on a completely different setup, it feels like I am missing a step but really don't know what to try next (and I'm a numpty at the best of times!). In the US as that may be important. And I can run BBC Sounds on my phone and BT to a speaker but would love to get it working again so we can use our Booms.

[bpa]

I've been unable to get any programs to play on BBC Sounds running on a Synology LMS. Given that I know that isn't supported anymore, I have set up a Raspberry Pi 4 running piCorePlayer. I have LMS 8.1.1 and version 2.13.3 of the BBC Sounds app running.

What version of IO::Socket::SSL does LMS show in the WebUI Settings/Information tab

[expectingtofly]

I've been unable to get any programs to play on BBC Sounds running on a Synology LMS. Given that I know that isn't supported anymore, I have set up a Raspberry Pi 4 running piCorePlayer. I have LMS 8.1.1 and version 2.13.3 of the BBC Sounds app running. I am still unable to listen to any programming. Whilst I can browse the app, pick a program through Stations and Schedules and 'play', the time progress bar shows a time of 0.
Given that this was happening on a completely different setup, it feels like I am missing a step but really don't know what to try next (and I'm a numpty at the best of times!). In the US as that may be important. And I can run BBC Sounds on my phone and BT to a speaker but would love to get it working again so we can use our Booms.

It should run fine on that setup. Are there any errors in the server log?

[scooper]

Thank you for helping me with this. I got the following errors from the server log

[21-02-08 09:11:07.2304] Plugins::BBCSounds::ProtocolHandler::__ANON__ (1032) Failed to get AOD MPD
[21-02-08 09:11:07.2443] Slim::Utils::Timers::__ANON__ (272) Error: Timer Slim::Networking::Async::HTTP::_http_socket_error failed:

[scooper]

What version of IO::Socket::SSL does LMS show in the WebUI Settings/Information tab

This is what is shown
IO::Socket::SSL: 2.068

[expectingtofly]

Thank you for helping me with this. I got the following errors from the server log

[21-02-08 09:11:07.2304] Plugins::BBCSounds::ProtocolHandler::__ANON__ (1032) Failed to get AOD MPD
[21-02-08 09:11:07.2443] Slim::Utils::Timers::__ANON__ (272) Error: Timer Slim::Networking::Async::HTTP::_http_socket_error failed:

That seems a bit odd, your server is failing to connect/download to the information about the stream so that it can start streaming.

Please can you do the following, on settings->Advanced->logging :

- set "network.asynchttp" to logging level "debug"
- set "plugin.bbcsounds" to logging level "info"

then try and play another stream and send me the log file

you can then set the logging level back to "error" and "warn" respectively.

[scooper]

That seems a bit odd, your server is failing to connect/download to the information about the stream so that it can start streaming.

Please can you do the following, on settings->Advanced->logging :

- set "network.asynchttp" to logging level "debug"
- set "plugin.bbcsounds" to logging level "info"

then try and play another stream and send me the log file

you can then set the logging level back to "error" and "warn" respectively.

As an update for anyone else in the same position, after doing as Stuart suggested (changing the logging options, generating a log file, restoring logging options) I am now up and running again.

Once again, I am indebted to those, like Stuart, who keep these services alive.

[slartibartfast]

As an update for anyone else in the same position, after doing as Stuart suggested (changing the logging options, generating a log file, restoring logging options) I am now up and running again.

Once again, I am indebted to those, like Stuart, who keep these services alive.

So just changing logging settings fixed it? I am sure that wasn't the expected outcome [emoji3]

Sent from my Pixel 3a using Tapatalk

[expectingtofly]

As an update for anyone else in the same position, after doing as Stuart suggested (changing the logging options, generating a log file, restoring logging options) I am now up and running again.

Once again, I am indebted to those, like Stuart, who keep these services alive.

That's great news. Looking at the log file, it looks like it was just failing to connect to the bbc and timing out. Hopefully it was just a bit of downtime somewhere end will continue to work for you.

[scooper]

So just changing logging settings fixed it? I am sure that wasn't the expected outcome [emoji3]

Sent from my Pixel 3a using Tapatalk

It wasn't but I'll take it

[AlecSp]

100% agree. I too used to use Squeezer but the android APK for Material is quite excellent

Now then, that APK was the key for me. Having just tried it, I can now confirm that I've been quickly converted!

I actually still prefer the Default interface when using Windows, and hadn't twigged that I could have a best of both worlds. But I can! With the Material Skin plug-in and the app, I now realise what everyone else was raving about. I think Squeezer may no longer darken my door!

Thanks for the prompt to get me to take a look.

[expectingtofly]

Release 2.13.4

Release 2.13.4 is a minor release to clean up a few issues:

• Ensure Single item promotions that point to a live event are handled correctly
• Improved performance of menu rendering
• Fixed incorrect paging handling on My Sounds->Latest

[scooper]

Back again

Unfortunately, I'm having the same issue as yesterday and this time changing the logging settings didn't help.
Stuart - would my server log be helpful?