This shows you the differences between two versions of the page.
servio_plugins [2012/06/18 21:42] ttguy [Installation] - where to find the place to configure the RSS feeds |
servio_plugins [2024/06/07 18:22] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Serviio Plugins ====== | ||
- | |||
- | Serviio plugins provide access to online sources such as Youtube or Regional Catchup TV services (e.g. BBC Iplayer). | ||
- | |||
- | This feature was made available as part of Serviio 0.6, the plugins [[http:// | ||
- | |||
- | Serviio doesn' | ||
- | * browse the [[http:// | ||
- | * make suggestions in the [[http:// | ||
- | * read the [[http:// | ||
- | |||
- | From version 0.6.1 Serviio supports plugins for **RSS/Atom feeds** and other **Web Resources**. Note some feeds that link directly to media require no plugin at all! | ||
- | |||
- | Plugins help Serviio locate the exact location of the media streams as the feed often links to html pages rather than the stream. | ||
- | |||
- | ====== Installation ====== | ||
- | 1. Download the plugin | ||
- | 2. Copy the plugin to the plugins folder (eg to / | ||
- | 3. Configure Serviio with at least one url to an RSS feed. This is done using the serviio console using the Online Source Tab which is found on the Library tab. | ||
- | |||
- | After up to 5 mins the streams should be available to view. On the DLNA client look for a new folder called " | ||
- | |||
- | ====== Development ====== | ||
- | |||
- | Read the [[http:// | ||
- | |||
- | Online content is usually served via **http** or **rtmp** protocol. The former is very easy to consume. The latter is mostly used by Adobe Flash servers and used in many online video services and FFmpeg compiled with [[http:// | ||
- | |||
- | Feed item URLs can expire with time, if that is the case you will have to provide the expiry date so that Serviio can re-run the URL extraction when that happens and get a valid URL when necessary. You can also define whether the content is a live stream or static content. | ||
- | |||
- | <note tip> | ||
- | * Look at existing plugins, there may be a plugins that can be adapted with only minor changes | ||
- | * The plugins can be largely tested outside of serviio (to speed up development). | ||
- | * Look at Youtube.groovy' | ||
- | * test1: does this plugin correctly identifies feeds it can and can't handle | ||
- | * test2: when given a link from an rss item, does the plugin correctly determine the media? | ||
- | * Once the tests above pass it's time to install the plugin and do some final testing | ||
- | </ | ||
- | |||
- | A plugin can be tested outside of groovy by running: | ||
- | |||
- | __On Windows:__ | ||
- | groovy -cp " | ||
- | |||
- | I suggest to create a MS-DOS batch file (ex: "{{ : | ||
- | < | ||
- | @echo off | ||
- | @ set ServiioPath=" | ||
- | @echo " | ||
- | %GROOVY_HOME%\bin\groovy.exe -cp " | ||
- | @pause | ||
- | </ | ||
- | |||
- | |||
- | |||
- | __On Linux:__ | ||
- | From your serviio install folder (eg / | ||
- | |||
- | groovy -cp lib/ | ||
- | |||
- | And of course you can use the [[http:// | ||
- | |||
- | ====== Logging ====== | ||
- | Logging is configured through conf/ | ||
- | |||
- | I've found adding the following gives me useful additional info for plugin development: | ||
- | |||
- | < | ||
- | < | ||
- | </ | ||
- | < | ||
- | < | ||
- | </ | ||
- | < | ||
- | < | ||
- | </ | ||
- | < | ||
- | < | ||
- | </ | ||
- | < | ||
- | < | ||
- | </ | ||
- | |||