Bug 2941 - XMLBrowser: Get additional details about streams
: XMLBrowser: Get additional details about streams
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Plugin
: 6.5b1
: All Other
: P2 normal (vote)
: ---
Assigned To: Andy Grundman
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-02-06 15:53 UTC by Fred
Modified: 2008-09-15 14:38 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fred 2006-02-06 15:53:55 UTC
It seems getting info on a radioio stream is broken, no info is returned. Playing the stream works fine. Sounds like the method used by the plugin (open the stream temporarily) does not update the DB as it should. Bitrate is 0 and the radio name is not there.

The same works fine on 6.2.x so radioio problems are not in case here.
Comment 1 Fred 2006-02-25 18:00:03 UTC
In the plugin code, it seems the $stream info has the right data (bitrate and title) but it is never added to the track... Could use $stream data but not sure how to access it. The *$ notation used to get the socket is unknown to me.
Comment 2 Blackketter Dean 2006-02-25 18:43:02 UTC
Andy's working on radioIO improvements
Comment 3 Andy Grundman 2006-04-22 22:11:25 UTC
Renaming because this should be something that works for all XML streams to get more info than just the title and URL.  This may have to be a 6.5 feature though, I am not sure how difficult it will be.

One thing we can do at least for LMA/Shoutcast/Live365 is include this data as additional attributes in the OPML file so SlimServer doesn't have to connect to the stream.
Comment 4 Andy Grundman 2006-05-26 14:11:44 UTC
Marking this fixed for now.  We support additional attributes in OPML files for content providers who choose to provide them:

bitrate
listeners
current_track
genre
source

These are currently used in the Shoutcast and LMA data.  RadioIO supports bitrate.
Comment 5 Chris Owens 2006-06-27 14:21:33 UTC
This bug fix is now part of a released version, and so has been marked closed. If you are still experiencing this problem, please reopen the bug.