Announce: BBCiPlayer Plugin (UK only)

[mobileadam]

Hi,

I posted about the sync player bug recently but haven't had time to work out how to post my logs etc but I see Owen has helped and Alan (the developer?) has now posted a fix. I'm not sure how this sort of thing works (I had assumed there was a big team of developers at Logitech working on new features and fixing bugs on some sort of schedule) how I must admit to be thrilled with this quick response. While not normally using beta software I have downloaded the 'nightly' version and installed it and have yet to have a re-occurance of the problem.

Given the complexities of the systems we have (internet connection, routers, WiFI, local servers and devices, BBC servers or whatever) it is great to see that the problem was identified (thanks to Triode) and then quickly resolved once further information was available.

Over the years with Squeezebox stuff I have seen my fair share of things being improved (and probably a few quirks) but given the pleasure it gives me as a whole system never do I want to get rid of it and dump it in favour of something else - although I might drop my Spotify premium account but that I feel is unrelated to LMS in anyway

So thanks everyone

Adam

[Owen Smith]

I posted about the sync player bug recently but haven't had time to work out how to post my logs etc but I see Owen has helped and Alan (the developer?) has now posted a fix. I'm not sure how this sort of thing works (I had assumed there was a big team of developers at Logitech working on new features and fixing bugs on some sort of schedule)

I think you'll find Logitech have a small team of LMS developers, for some definition of "small". Alan is indeed one of those Logitech developers.

To post your logs you would create a userid on the LMS Bugzilla site (links to the bug in previous postings) and then Attach the logfile (preferrably zipped) to the bug with a comment saying what you were doing at the time etc.

Triode identified that the bug was in the core server but was misled by potentially misleading logging as to excactly where it was. But between Triode, Alan and myself I feel we got there quite quickly for what is actually quite a subtle bug.

And I note Alan analysed my logs and submitted a fix at the weekend, so big thanks from me for that. Don't forget to take a break from time to time Alan :-).

[mobileadam]

Well I used iPlayer extensively today. I didn't need to restart at any time. Even when using Listen Again I did get 3 re-buffering episodes but after each one the players both continued the stream which was fantastic.

The joy of a reliable service.

thanks again

[trautigan]

Seems a shame to rain on your self-congratulatory parade...(remember that this was a bug introduced by Logitech then fixed, not a found bug - BIG DIFFERENCE)

Firstly - here's a suggestion:

If someone raises a bug on Bugzilla, why not notify then via email when the bug is 'fixed'?
I can assure you that didn't happen with Bug 17877.

Secondly - a clue as to how to find this fixed version would be more than welcome.
Do I have to download a nightly build?
Or is it included in an automatic software update?
Is there a sticky post somewhere with all this info in? If not, may I suggest you do this.

So, from my jaundiced perspective - I have not done any tests as I don't know whether I am testing a version with the fix in or not and don't want to waste (more) time testing Logitech's software for them.

When you provide some of the above clues, I'll do that.

Until then I don't know if you have actually fixed it or not.

[Triode]

Secondly - a clue as to how to find this fixed version would be more than welcome.

http://downloads.slimdevices.com/nightly/?ver=7.7

Can I suggest we keen this thread to discussions of the BBCiPlayer plugin and applet please.

[Owen Smith]

If someone raises a bug on Bugzilla, why not notify then via email when the bug is 'fixed'?
I can assure you that didn't happen with Bug 17877.

On the bug you can request email notifications for any change to the bug. I did so and was emailed every time anyone made any update, including Alan submitting the fix. If you wanted to be notified you should have added yourself to the notification list. I suggest you do so next time you raise a bug.

As Triode says hopefully we can now return to scheduled iPlayer service on this forum.

[finemind]

Hi
I have been using the iPlayer plugin on my Squeezebox Radio for a year with no problems but for the last few days I have had no access to listen again programmes. When I press on certain BBC stations I get 'empty' instead of the usual list. 1Xtra, Radio 3 and Radio 7 are fine, the rest are 'empty'. The iPlayer extras plugin is working fine.

I am running Logitech Media Server 7.7.1 r9557 using Squeezeplug Debian on a Sheevaplug. I am not in the UK.

I have restarted and reinstalled everything but no luck. I notice someone had a similar problem on this thread last year. This person solved it after noticing "that the date was set to 7th Oct on the server! Corrected and now all is well".

Is that the solution and if so, how do I correct the date on the server?

Many thanks in advance for any help.

Matt

[mobileadam]

Seems a shame to rain on your self-congratulatory parade...(remember that this was a bug introduced by Logitech then fixed, not a found bug - BIG DIFFERENCE)

Firstly - here's a suggestion:

If someone raises a bug on Bugzilla, why not notify then via email when the bug is 'fixed'?
I can assure you that didn't happen with Bug 17877.

Secondly - a clue as to how to find this fixed version would be more than welcome.
Do I have to download a nightly build?
Or is it included in an automatic software update?
Is there a sticky post somewhere with all this info in? If not, may I suggest you do this.

So, from my jaundiced perspective - I have not done any tests as I don't know whether I am testing a version with the fix in or not and don't want to waste (more) time testing Logitech's software for them.

When you provide some of the above clues, I'll do that.

Until then I don't know if you have actually fixed it or not.

With my basic and limited understanding of 'BUGS' they are a pain if they affect my normal daily operation regardless of whether they have been 'introduced' or 'found'. In this situation I was pleasantly surprised to see the user community helping to locate, identify, resolve and then test new versions of the code so that the majority can have a reliable service. I'm still happy to congratulate those involved, I'm sure there are lots of bugs being found or whatever and fixed, from my perspective this was one that impacted my daily use of LMS was my first experience and for me seems to be resolved in a very timely manner.

I assumed that a nightly (BETA) build would contain the fix so for the first time ever installed (at my own risk) a BETA version of the software so I can try it out. I would expect the a 'released' version of the software will be available in the future and at the point your instance of LMS will prompt you to download it.

[mrw]

Suggest you have a play with this. I think we can rewrite that bit to parse incrementally as the xml arrives, but will require chaning how the code is called from xmlbrowser. I'll look at this at somepoint soon.

I've drafted up something that seems to be working. At present it is constructed as a separate module which can be used by simply replacing a 'use XML::Simple' with a 'use XML::Simple_with_IdleStreams'. Horrid name & should be renamed anyway if included in a plugin.

It does add overhead (about 10% or more) to the existing XMLin call. That might be reduced if more carefully coded.


My goal would be to turn this into something that replaces XML::Simple system-wide, if it's worth pursuing. Perhaps a plugin to supply as an optional component. But that will take some more study of how module loading works - I'm not sure how advisable it would be to tinker with an existing module's symbol table (if that's what it tales).

Alternatively the logic could be simply unrolled into an existing XML::Simple, e.g. as a patch, or replacement.

Anyway, I shall run with it for a few weeks and see how it fares.

[murkle]

[snip]
Anyway, I shall run with it for a few weeks and see how it fares.

Thanks for posting this, I will too and report back. I've also been noticing drop outs from my SqueezePlug server.