MceEpg2XmlTv

[nbarsley]

Ok thanks.

[zehd]

I've released the latest version of the GUI and the Utilities provided by whurlston.

I've updated the wiki, and hope that it is a bit easier to understand...

If you are using the GUI, don't install or configure the separate utilities. They will be installed with the GUI and placed where the GUI needs them.

Don't hand edit files outside of using the GUI. When you open a file inside the GUI, it uses the correct filename and path, so it all works together.

The installer should be overwriting any files that previously exist. However, some files like the import.txt or export.txt may have to be moved. Please see the topic from the wiki page
http://gbpvr.com/pmwiki/pmwiki.php/Utili...mlTv#toc16

New Features:

• GUI for new options - click 'Edit Config.ini'
  
• Includes: New Show Markers, Marker Text, Repeat-After x days,
  
• Fix Channels and Update GB-PVR EPG - to update the EPG without leaving the GUI.
  
• Enhance Listings - Currently only adds Original Air Date to Programme Description
  

[dennit]

Normally a program would not care as to the order of the tags. There is no indication in the XMLTv spec that a particular order was necessary.

It would be interesting to know what happens when that program hits a tag that I provide that is not part of the XMLTv spec such as <joined-in-progress />

I'm not really sure why it worries about the order. This is the main XMLTV.pm file from the XMLTV project and the commented code that triggers a warn is:

# Search for a handler - from $handler_pos onwards. But
# first, just warn if somebody is trying to use an element in
# the wrong place (trying to go backwards in the list).
#
my $found_pos;
foreach my $i (0 .. $handler_pos - 1) {
if ($name eq $handlers->[$i]->[0]) {
warn "element $name not expected here";


At the top of the code I see:
# The ordering of the subelements list gives the order in which these
# elements must appear in the DTD. In fact, these lists just
# duplicate information in the DTD and add details of what handlers
# to call.

The ordered list is:
our @Programme_Handlers =
(
[ 'title', 'with-lang', '+' ],
[ 'sub-title', 'with-lang', '*' ],
[ 'desc', 'with-lang/m', '*' ],
[ 'credits', 'credits', '?' ],
[ 'date', 'scalar', '?' ],
[ 'category', 'with-lang', '*' ],
[ 'language', 'with-lang', '?' ],
[ 'orig-language', 'with-lang', '?' ],
[ 'length', 'length', '?' ],
[ 'icon', 'icon', '*' ],
[ 'url', 'scalar', '*' ],
[ 'country', 'with-lang', '*' ],
[ 'episode-num', 'episode-num', '*' ],
[ 'video', 'video', '?' ],
[ 'audio', 'audio', '?' ],
[ 'previously-shown', 'previously-shown', '?' ],
[ 'premiere', 'with-lang/em', '?' ],
[ 'last-chance', 'with-lang/em', '?' ],
[ 'new', 'presence', '?' ],
[ 'subtitles', 'subtitles', '*' ],
[ 'rating', 'rating', '*' ],
[ 'star-rating', 'star-rating', '?' ],
);

It appears to work OK, despite the warnings. I've temporarily reordered the list just to kill all the warnings, but it wasn't clear to me whether XMLTV's dtd required a specific order.

As for "<joined-in-progress />" it also spits a warning. I don't use it so I'm filtering it now.

I'm not asking for you to change anything, but thought you might want to know what I'm seeing when using tv_extractinfo_en of the XMLTV package to process the XMLTV format output.

[dennit]

The GUI is a fancy batch file. That's it.

I set up the command line tools, then compared to the GUI. I want the enhanced listings (* or new for new showings and original air date in desc.) Am I correct in thinking that these are only in the GUI? It looks like a lot more than a fancy batch. After running both command line and GUI, I'm seeing lots of diffs in the output. The big one for me is that the command line (and Oz's old Yahoo Go TV) used the following for the xml file:
<channel id="0002">

while for the same channel the GUI is using:
<channel id="28457075">

Is there a switch for this? I'd like the enhancements of the GUI, and I can change my processing (as long as the channel id's remain constant) but if there's a simple way to get the same channel id's that the command line uses, I'd appreciate it if someone could tell me.

BTW, thanks to all authors for these programs.

[whurlston]

Use the GUI installer to install the latest command line utilities. You don't have to use the GUI, everything's just included in one package. As for the change in the channel ID, only one display-name field was being output previously so the ID was used to specify the channel number. It is now outputting all display-name fields so the channel ID is now the actual ID.

[zehd]

Use the GUI installer to install the latest command line utilities. You don't have to use the GUI, everything's just included in one package. As for the change in the channel ID, only one display-name field was being output previously so the ID was used to specify the channel number. It is now outputting all display-name fields so the channel ID is now the actual ID.

As whurlston said, you don't need to use the GUI, if you're using the command line tools. And shouldn't. The two ways use slightly different installations and configurations and could prove incompatible.

Most notably, with the GUI, there must be a 'config.ini' in the same path as the app, and inside the 'config.ini', the 'file = myfile.xml' MUST have a semi colon in front, to disable that item. (Already done for you in release)

You would have to un-comment that line and change it to suit you, if you do not want to use the GUI.

But downloading and installing everything in the same package is essential. Keeps it all up to date so you're not comparing apples to oranges.

The 'Enhance Listings' function in the GUI, is the only feature that available only in the GUI. (for now)

The New Show Marker was added in this release to whurlston's utils. I incorporated the feature into the New GUI

[mvallevand]

while for the same channel the GUI is using:
<channel id="28457075">

Is there a switch for this? I'd like the enhancements of the GUI, and I can change my processing (as long as the channel id's remain constant) but if there's a simple way to get the same channel id's that the command line uses, I'd appreciate it if someone could tell me.

I didn't notice any difference with this, the channel id seems to be used internally, the channel number stayed the same.

Martin

[dennit]

As whurlston said, ...

The 'Enhance Listings' function in the GUI, is the only feature that available only in the GUI. (for now)

The New Show Marker was added in this release to whurlston's utils. I incorporated the feature into the New GUI

OK, thanks for this info from both of you. I was not using both, just trying to see if there was any reason to use one or the other. Since I want the enhanced listings (only in the GUI), and the channel id change was made to both ( I didn't realize that since I was comparing the output of the previous command line version to the output of the new GUI), I'll modify my stuff to use the new format for the channel id and use the GUI.

Thanks again, your work is much appreciated.

[zehd]

I've made a patch to the GUI which I will release here.

I've added a button "Write Batch File" that will make a very basic batch file that will call the commandline tools.

You can use the GUI to configure, but still have the UpdateEPG.bat call the batch file and not the GUI...

(The new Enhance Listings feature is not used when using only the batch file)

If you click the debug check box before clicking 'Write Batch File' the batch file will have several 'pause' statements added, for troublshooting...

The feature creates a very basic batch file called 'BasicEPG.bat' in the GUI's folder.

To use with GB-PVR's UpdateEPG.bat remove references to the GUI and add a reference to the Batch file..

Code:

change:
"C:\EPG\MCE2XML_GUI.exe" auto

to
call "C:\EPG\BasicEPG.bat"

Be sure that the batch file does not contain 'Pause' statements before you decide to use it regularly with GB-PVR.

[mk000]

Does this epg application run on vista business?