e.g.

e.g.

5. Feed tags

For feeds that are well formatted xml (e.g. rss, atom), the contents of the feed are read by specifying the tag names for each attribute that we are interested in inside the parser section of the definition. Each of those tag names is specified in one of the following definition tags;

• programTag. This specifies the name of the program top level tag
• episodeTag. Optional. This is the tag in which the episode name is held
• programTitleTag. This is the tag in which the program name is held
• programDescriptionTag. Optional. This is the tag in which the program description is held

dateTag. Optional. This is the tag in which the broadcast date is held

• linkTag. This is the tag in which the link to the web page displaying the program is held
• programIdTag. This is the tag in which a unique identifier for the program is held. This is used to track which programs have been watched, so it can be any unique text
• programIconTag. Optional. This is the tag in which the program thumbnail icon is held
• namespace. Optional. If your xml requires namespaces to parse, specify each namespace in a tag with an attribute of name to specify the namespace, e.g. <namespace name=”video”>http://www.google.com/schemas/sitemap-video/1.1</namespace>. You can have as many namespace tags as required.
• channelPrefixTag. If your feed contains multiple channels in one XML file, you can specify which tag contains a channel name and prefix this to the code from the channel definition to create multiple channels from one stream. You can add dummy channels with empty feed strings to the channel list to specify channel icons for each prefixed channel.

If the value you need to get from the xml is the tag value (e.g. <id>123</id>, simply specify the tag name in the definition (e.g. <programIdTag>id</programIdTag>).

If the value you need is in an attribute of the tag (e.g. <id val=”123″/>), specify the attribute name in the “attr” attribute of the definition (e.g. <programIdTag attr=”val”>id</programIdTag>).

If there are multiple nodes with the same name in the feed, you will need to pick one of them e.g.

<link rel=”self” href=”http://dj.rte.ie/vodfeeds/feedgenerator/videos/show/?id=1050152″ />
<link rel=”alternate” href=”http://www.rte.ie/player/#v=1050152″ />

you tell the system which one to pick by using the findAttr and findAttrVal attributes. findAttr is the name of the attribute to look for, and findAttrVal is the value in that attribute that needs to be matched (e.g. <linkTag attr=”href” findAttr=”rel” findAttrVal=”alternate”>link</linkTag>)

To read the date format, also specify a date mask in C# .NET format, e.g.  <dateFormat>ddd, dd MMM yyyy HH:mm:ss</dateFormat>. Your date string may contain information that you don’t want to parse at the end, e.g a timezone. To ignore that, simply don’t specify the whole date format string – the date will be truncated to the length of the format string before parsing.

6. Feed parsing

For content that cannot easily be defined as an xml tag, you can define a start and end string to search for. The value will be taken as the content between the start and end tag, e.g. if we wanted to get the program name from the text “programName=Doctor Who,episodeName=..” then we would define

<programStart>programName=</programStart>
<programEnd>,</programEnd>

If you need to search for multiple strings to find the exact position, i.e. find the first occurrence of string 2 after string 1. For example, when searching in the following “tag=programName,value=DoctorWho,tag=episodeName,value=…” you could specify the following;

<programStart>tag=programName</programStart>
<programStart2>value=</programStart2>
<programEnd>,</programEnd>

The tags that you can use for this are;

programStart
titleStart
episodeStart
dateStart
dateFormat
linkStart
programTitleStart
programDescriptionStart
programIconStart
programIdStart

programEnd
titleEnd
episodeEnd
dateEnd
dateFormat
linkEnd
programTitleEnd
programDescriptionEnd
programIconEnd
programIdEnd

programStart2
titleStart2
episodeStart2
dateStart2
dateFormat
linkStart2
programTitleStart2
programDescriptionStart2
programIconStart2
programIdStart2

programEnd2
titleEnd2
episodeEnd2
dateEnd2
dateFormat
linkEnd2
programTitleEnd2
programDescriptionEnd2
programIconEnd2
programIdEnd2

7. Displaying the video

7.1 WMV and WMA

WMV and WMA content can be displayed directly within media center, so no further options are required for this.

7.2 Web based video

For web based video (flash and silverlight), there are two options for displaying the video. Option 1 is  a new method for displaying the video in a standalone player, and is the suggested technique. Option 2 is an older method, and is included here for reference. Option 2 works fine for most web pages, but not those which cannot be displayed in an iframe, whereas Option 1 should work for everything

Option 1 – PLAYER

Option 1 will display the web page containing the video in a standalone application. The web page is manipulated to make the video full screen, but you must provide information about the web page to enable it to do that. When you set the programType to PLAYER, TunerFreeMCE will look for another file in your plugin folder called player_config.xml. This file contains some parameters required to manipulate the video. They are;

 

• playerWidth, playerHeight  – the original width and height of the component that plays the video
• play00X, play00Y – the first points to click when first playing the video (optional)
• play0X, play0Y – the second points to click when first playing the video (optional)
• play1X, play1Y,  – the third points to click when first playing the video. (optional)
• FSX, FSY – the click points to send the video full screen (optional – only use if the video cannot be scaled in css)
• playFSX, playFSY – the play/pause location while playing (optional)
• play00Delay – the time in seconds to wait before clicking play00 (optional – defaults to 5s)
• playDelay  – the time in seconds to wait before clicking play0 (optional – defaults to 5s)
• zoomedId – the css tag to identify the components to be scaled to full screen (optional)
• movedId – the css tag to identify the components to be moved to the top left of the screen (optional)
• widenedId – the css tag to identify the components to be widened to the width of the screen (optional)
• backgroundId – the css tag of any background components to be blanked out (optional)
• hiddenId – the css tag of any items to be completely hidden (optional)
• extraCSS – any extra css required to make the screen display correctly (optional)
• deleteCache – true if the browser cache should be deleted before playing. A flash bug means that you should set this to True for most flash content, or it will only display once (optional)

Here’s a complete example from channel 5. Things to note are the player size is originally 640×360. The initial play button is at 318,169, and the play button while playing is at 218,354. The video is in a container with the id “video_box”, so that is zoomed and moved to the top left of the screen (the # at the start tells css to look for the item with the id that follows). The background is the “body” tag, and all “div”, “form” items are hidden as well as anything with a class of “ad” (the . before ad tells css to look for anything with a class of the name that follows). The cache is deleted before playing each time, and the extra css shown is added to move the video box to the top of the stack and to make sure it is visible

<?xml version="1.0" encoding="utf-8"?><PlayerConfig xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <playerWidth>640</playerWidth> <playerHeight>360</playerHeight> <play0X>318</play0X> <play0Y>169</play0Y> <playFSX>218</playFSX> <playFSY>354</playFSY> <zoomedId>#video_box</zoomedId> <movedId>#video_box</movedId> <backgroundId>body</backgroundId> <hiddenId>.ad, div,form</hiddenId> <deleteCache>true</deleteCache> <extraCSS>#video_box{visibility: visible !important; z-index: 9999 !important;} </extraCSS> </PlayerConfig>

Here’s another complete example, this time for the 4OD plugin. Key points to note are the player size is 640×363. It needs to go full screen because it cannot scale the video in the window, to the FSX and FSY are specified. The player is still moved to the top left so that the clicks can occur, but the player is not zoomed (because that won’t work on this page).

<?xml version="1.0" encoding="utf-8"?><PlayerConfig xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <playerWidth>640</playerWidth> <playerHeight>363</playerHeight> <FSX>625</FSX> <FSY>350</FSY> <playFSX>10</playFSX> <playFSY>360</playFSY> <movedId>#watch-player</movedId> <backgroundId>body</backgroundId> <hiddenId>div,span,img,p,iframe,table,a</hiddenId> <deleteCache>true</deleteCache> <extraCSS>#watch-player{visibility: visible !important;} #movie_player {z-index:9999 !important;}</extraCSS> </PlayerConfig>

In each case you may need to play with the settings to see what effect it has – different sites use different css and javascript tricks that mean there is no simple solution. An easy way to test though is to run the player standalone, passing in the parameters of what you want it to do. Here is an example;

"C:\Program Files (x86)\MillieSoft\TunerFreeMCE\TunerFreeMCEWebBrowser.exe " "http://www.bbc.co.uk/iplayer/tv/bbc_one_london/watchlive" "C:\Users\Bob\myplugin\player_config.xml" "Windows Media Center"

Option 2 – FLASH

Option 2 will display the video in a from in a web page within media center. The software will click on the appropriate points on the page to make the video play and go full screen. You need to tell the software where to click by giving the X and Y coordinates of a number of possible click points. You can include basic calculations using +, – and * and the constants H (screen height), H2 (half screen height), W (screen width) and W2 (half screen width). So, if the play button is 300 pixels to the left of the middle of the screen, specify it as “W2-300”. If a click is not applicable, specify the coordinates as 0,0.

The tags are;

• StartPlay. This is the location to be clicked to start playback first time.
• PlayNonFS. Play when not in full screen
• RevNonFS. Jump to start when not in full screen
• FS. Go to full screen
• PlayFS. Play when in full screen
• RevFS, Jump to start when in full screen
• HighRes. Toggle high resolution/low resolution

e.g.

To calculate the click positions, I put media center in to full screen, navigate to a page and then take a screenshot. I then paste that in to Paint and use that to find the co-ordinates of points on the screen. When not in full screen, the Y positions tend to be a fixed number, and the X positions tend to be plus or minus a fixed amount from the middle of the screen. In full screen, the Y position tends to be a fraction of the screen height, and the X positions again tend to be plus or minus a fixed amount from the middle of the screen, but are sometimes a fraction of the screen width.

using System; using System.Net; using System.Text.RegularExpressions; using TunerFreeMCECore;  namespace DaveParser {     [Serializable]     public class DaveParser :BaseParser     {          override  public TVProgram populateProgramLink(TVProgram program)         {            program.programLink="http://"+;            /* logic to get the program link */             return program;         }           override public TVProgramList parsePrograms(TVProgramList listIn, String currentDirectory)         {             removed=listIn.thePrograms.RemoveAll(delegate(TVProgram p1) { return p1.ProgramProvider.Equals("Dave"); });             added = 0;             total = 0;             pageCount = 0;             using (WebClient w1 = new WebClient())             {                 w1.Encoding = System.Text.UTF8Encoding.UTF8;                 String showList = w1.DownloadString("http://video.uktv.co.uk/dave/programmes/a-z/see-all");                 string[] showComponents = showList.Replace("<div class=\"promo\">", "¬class=\"promo\">").Split('¬');                     foreach (string show in showComponents)                     { // do all of the processing to get the show details from the web page                                            listIn.thePrograms.Add(new TVProgram(showTitle,showURL,episodeName,showImage,showSummary,"Dave","",DateTime.Now,"DAVE","file://"+currentDirectory+"\\dave.jpg",showURL,"PLAYER","Dave"));                                          added = added + 1;                                          total = total + 1;                                          pageCount = pageCount + 1;                      }                 }             }             return listIn;         }     } }

10. Testing

To test your plugin, put it in the C:/ProgramData/MillieSoft/TunerFreeMCE/additional_plugins folder. This folder is used to pick up any plugins that are not installed directly via the plugins page in TunerFreeMCE.

After you have created your plugin, run TunerFreeMCECacheBuilder.exe to pick up your programs. If you run the code with a -debug flag, some additional information will be outputted that may help you if you are having problems.

11. Publishing

After you have created your plugin, email me at martin@milliesoft.co.uk to get your plugin added to the list of plugins shown within TunerFreeMCE. If your plugin includes a dll parser, please also include the source code for review. We need to do that to avoid malicious code.