home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 2
Plugin Development
Featured Plugins
Webradio
Webradio
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="chefkoch" data-source="post: 1035498" data-attributes="member: 10438"><p>That's a good idea the more people have a look at it and raise approvals or improvement suggestions the better it might be.</p><p></p><p>@[USER=73415]offbyone[/USER] can you take a look at the list file as well please? With OnlineVideos you are already have a good experience what might be needed for plugin providing access to online content from various site/sources ...</p><p></p><p></p><p></p><p>[CODE=XML] <Description></p><p> <!-- All Informations about the current Description --></p><p> <StreamDescriptions></p><p> <!-- The Code of the Language in which the Description --></p><p> <LngCode>DE</LngCode></p><p> <!-- The Description in particular Language --></p><p> <Description>Der beliebte Prviatsender aus Dänemark spielt auf dieser Welle frische Hits auf.</Description></p><p> </StreamDescriptions></p><p> <StreamDescriptions></p><p> <LngCode>EN</LngCode></p><p> <Description>The popular Prviatsender from Denmark plays on this fresh wave hits.</Description></p><p> </StreamDescriptions></p><p> </Description>[/CODE]</p><p>Having the description multi language might be nice to have for bigger stations, but would really be a rare use case imo. Either it is not being updated, not used or very inconsistent. I am not sure if this would be required. Especially looking at the file size of the complete list: It's already 2,63MB. Storing all stations in one xml which gets updated completely loaded for every new version. <Description><StreamDescriptions><Description> for a single description is much overhead plus the closing nodes.</p><p></p><p>Same goes for the Stream URLs. Maybe using attributes would make these more efficient.</p><p>Here is an example: It contains exactly the same information, but requires a lot less space:</p><p>[CODE=XML]<?xml version="1.0" encoding="utf-8"?></p><p><WebradioStreams xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"></p><p> <!-- Streamlistversion --></p><p> <Version>1</Version></p><p> <Streams></p><p> <!-- All Informations about the current Station --></p><p> <Stream id="10000" title="Radio 100FM" country="DK" city="Kopenhagen" ></p><p> <Description>Der beliebte Prviatsender aus Dänemark spielt auf dieser Welle frische Hits auf.</Description></p><p> <StreamUrls></p><p> <StreamUrl name="Orginal" format="mp3" bitrate="128 kbps">http://onair.100fmlive.dk/100fm_live.mp3</StreamUrl></p><p> <StreamUrl name="Stream 2" format="mp3" bitrate="256 kbps">http://onair.100fmlive.dk/100fm_live.mp3</StreamUrl></p><p> </StreamUrls></p><p> <!-- All Gengres of the current Station. (comma-separated) --></p><p> <Genres>Mainstream, Pop</Genres></p><p> <!-- Hompage of the current Station (not used yet) --></p><p> <Home>http://radio100fm.dk/</Home></p><p> <!-- Logo of the current Station --></p><p> <Logo>http://static.radio.de/images/broadcasts/4626_4.gif</Logo></p><p> </Stream></p><p> </Streams></p><p></WebradioStreams>[/CODE]</p><p>StreamURLs and StreamURL could also be URLs and URL.</p><p>Genres, Home, Logo are not changed yet, could be, but don't have to:</p><p></p><p>I am still not sure about the localizable description, might be a bit over-engineered.</p><p>The genres also can be multi-language, but don't have to.</p><p></p><p>What about the id? I expect this is required for defining the favourites, right?</p><p>Because it might become a bit tricky when adding new streams and there might be duplicated ones, or .... not sure if there is an alternative, the station name also can be duplicated easily across different countries/regions... so it might not be an alternative.</p><p></p><p>Regarding the stream selection in GUI, I would not prefer asking the user everytime. Maybe defining a priority list for formats, i.e. mp3 > ogg > aac.... within the plugin code and then using the best bitrate. If the playback fails, try the next one. If the playback is fine the user might have the option within the GUI (context menu or side menu) to switch manually to an alternative stream.</p><p>(but how storing the preferred stream by the user???)</p><p>He could either be able to change the format priority or for specific a station define the preferred stream.</p><p></p><p>So now the ultimate comfort solution <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /> :</p><p>After manually changing the stream to an alternative url, a successful start of playback and an additional timeout of 30secs the plugin asks the user whether he would like to prefer this stream for this station in the future as well. If the user confirms this preferred configuration of station and stream is stored in separated settings file. If the user does not answer the question, maybe after a timeout of 2 minutes, the dialog just disappears.</p><p></p><p>Should users be able to report broken streams from within the plugin like in OnlineVideos?</p><p></p><p>So these are the suggestions/thoughts from my side.</p><p></p><p>BTW: I hope it's okay I the xml in your post from attachment to the message, easier to read it for others <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /></p><p>Especially because the xml is not too much <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /></p></blockquote><p></p>
[QUOTE="chefkoch, post: 1035498, member: 10438"] That's a good idea the more people have a look at it and raise approvals or improvement suggestions the better it might be. @[USER=73415]offbyone[/USER] can you take a look at the list file as well please? With OnlineVideos you are already have a good experience what might be needed for plugin providing access to online content from various site/sources ... [CODE=XML] <Description> <!-- All Informations about the current Description --> <StreamDescriptions> <!-- The Code of the Language in which the Description --> <LngCode>DE</LngCode> <!-- The Description in particular Language --> <Description>Der beliebte Prviatsender aus Dänemark spielt auf dieser Welle frische Hits auf.</Description> </StreamDescriptions> <StreamDescriptions> <LngCode>EN</LngCode> <Description>The popular Prviatsender from Denmark plays on this fresh wave hits.</Description> </StreamDescriptions> </Description>[/CODE] Having the description multi language might be nice to have for bigger stations, but would really be a rare use case imo. Either it is not being updated, not used or very inconsistent. I am not sure if this would be required. Especially looking at the file size of the complete list: It's already 2,63MB. Storing all stations in one xml which gets updated completely loaded for every new version. <Description><StreamDescriptions><Description> for a single description is much overhead plus the closing nodes. Same goes for the Stream URLs. Maybe using attributes would make these more efficient. Here is an example: It contains exactly the same information, but requires a lot less space: [CODE=XML]<?xml version="1.0" encoding="utf-8"?> <WebradioStreams xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <!-- Streamlistversion --> <Version>1</Version> <Streams> <!-- All Informations about the current Station --> <Stream id="10000" title="Radio 100FM" country="DK" city="Kopenhagen" > <Description>Der beliebte Prviatsender aus Dänemark spielt auf dieser Welle frische Hits auf.</Description> <StreamUrls> <StreamUrl name="Orginal" format="mp3" bitrate="128 kbps">http://onair.100fmlive.dk/100fm_live.mp3</StreamUrl> <StreamUrl name="Stream 2" format="mp3" bitrate="256 kbps">http://onair.100fmlive.dk/100fm_live.mp3</StreamUrl> </StreamUrls> <!-- All Gengres of the current Station. (comma-separated) --> <Genres>Mainstream, Pop</Genres> <!-- Hompage of the current Station (not used yet) --> <Home>http://radio100fm.dk/</Home> <!-- Logo of the current Station --> <Logo>http://static.radio.de/images/broadcasts/4626_4.gif</Logo> </Stream> </Streams> </WebradioStreams>[/CODE] StreamURLs and StreamURL could also be URLs and URL. Genres, Home, Logo are not changed yet, could be, but don't have to: I am still not sure about the localizable description, might be a bit over-engineered. The genres also can be multi-language, but don't have to. What about the id? I expect this is required for defining the favourites, right? Because it might become a bit tricky when adding new streams and there might be duplicated ones, or .... not sure if there is an alternative, the station name also can be duplicated easily across different countries/regions... so it might not be an alternative. Regarding the stream selection in GUI, I would not prefer asking the user everytime. Maybe defining a priority list for formats, i.e. mp3 > ogg > aac.... within the plugin code and then using the best bitrate. If the playback fails, try the next one. If the playback is fine the user might have the option within the GUI (context menu or side menu) to switch manually to an alternative stream. (but how storing the preferred stream by the user???) He could either be able to change the format priority or for specific a station define the preferred stream. So now the ultimate comfort solution ;) : After manually changing the stream to an alternative url, a successful start of playback and an additional timeout of 30secs the plugin asks the user whether he would like to prefer this stream for this station in the future as well. If the user confirms this preferred configuration of station and stream is stored in separated settings file. If the user does not answer the question, maybe after a timeout of 2 minutes, the dialog just disappears. Should users be able to report broken streams from within the plugin like in OnlineVideos? So these are the suggestions/thoughts from my side. BTW: I hope it's okay I the xml in your post from attachment to the message, easier to read it for others ;) Especially because the xml is not too much ;) [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 2
Plugin Development
Featured Plugins
Webradio
Webradio
Contact us
RSS
Top
Bottom