16 posts in this topic

Quote

 

Xepg version 0.7.0.0 is available:

If you upgrade from Xepg 0.6.x.x it is a MUST to read the changelog.


 

Quote

 

XgrabDMS version 0.1.1.0 is available:

Study the new EPG structure inside the DVBViewer Media Server in detail

 

 

Details at a123.dk  and in the changelogs of DVBViewer 6.0 / DVBViewer Media Server 2.00

 

Share this post


Link to post

Posted (edited)

Many thanks for your great and valuable tool - it's an important chain member in my media center! :original:

 

I just wanted to let you know, I was upgrading from version 0.5.1.4 to 0.7.0.0 and first I was no longer able to do the import because of the following error:

Xepg Version: 0.7.0.0
IMPORT LOG
DESTINATION: DVBViewer Media Server
...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Processing: C:\Temp\xmltv\xepg\xmltv.xml

ERROR TYPE: Unknown Importing EPG

EXCEPTION MESSAGE---EVariantTypeCastError:Could not convert variant of type (Null) into type (OleStr)
Error on importing EPG
ERROR: Unknown Importing EPG

The reason is easy: Xepg no longer accepts a pretty-print formatted EPGFormat XML file, i.e. it doesn't like line breaks in the EPG format XML file.

 

OK:

<?xml version="1.0" encoding="UTF-8"?><settings><section name="WhereToDisplay"><entry name="1">1050</entry><entry name="2">1044</entry>

No longer accepted in 0.7.0.0:

<?xml version="1.0" encoding="UTF-8"?>
<settings>
	<section name="WhereToDisplay">
		<entry name="1">1050</entry>
		<entry name="2">1044</entry>
		<entry name="4">1024,1031,1049,1025,1028,1033,1040,1042,1053,1054</entry>
...

hth. best regards

Edited by mrphlox

Share this post


Link to post

So, you have manually edited the EPG Format file, right?

I use Microsoft MSXML DOM (TXMLDocument in Delphi) to read and write the file. If that fails, the file is with 99,9999% probability not well-formed (illegal).

 

Try to open the file in Internet Explorer.

Share this post


Link to post

First of all: Nope, there's no need for manual changes, reformatting Default.xml is enough and XML is still well-formatted, IE opens it without complains.

Default -formatted.xml

Share this post


Link to post

Posted (edited)

You are right. The problem is described here:

 

http://stackoverflow.com/questions/16865979/delphi-exception-when-preserving-whitespace-in-txmldocument

 

I now remember: A user requested a way to insert a blank line into the EPG. I suggested to use the "Some Text" with a space and then insert that to an empty StartParagraphX in the EPG Format Editor. At least it will look as a blank line. To avoid the space to be ignored by the xml parser I had to add the line

 

  XMLDoc.ParseOptions := XMLDoc.ParseOptions + [poPreserveWhiteSpace];

 

I am sure this happened somewhere between  versions 0.5.1.4 (very old ;)) and 0.7.0.0

 

I suggest to leave things as is. CONCLUSION: Don't edit xml files created by Xepg.:)

 

Thanks for the feedback.

Edited by Delphi
add conclusion

Share this post


Link to post

Just a bit more information:

 

The extra code line for preserving whitespace was introduced in version 0.5.2.0. An unwanted side effect was that pretty-print xml is no longer accepted in settings files. It is accepted in the XMLTV files ofcourse.

 

Xepg (TXMLDocument) never creates pretty-print xml files. You MUST have edited the file somehow, sometime in the past.

 

Well, never mind. I do not like that Xepg cannot read an xml file that is actually valid. It's not that easy to fix, unless preserving whitespace is turned off again.

Or: use another xml parser like OXml/EasyXml. For now I will leave it as is.

 

 

 

Share this post


Link to post

Thanks for your answers.

 

In fact, there's no need to format / edit the EPG format file - if one knows. I can't remember why I then reformatted it (it has been working fine at this time), but I guess I was just curious to see how it's structured. No problem for me if you leave it as is, but maybe the error message could be improved, indicating that the format file can't be parsed, not the xmltv file, as I thought for a while.

 

 

Share this post


Link to post
6 minutes ago, mrphlox said:

but maybe the error message could be improved

 

This is allready on my TODO list. Whatever I decide to do, a more meaningfull error message is needed in any case. Thanks again  for the feedback, it was usefull.

Share this post


Link to post

Hello, I set up xepg, pair my channels, and then download and import the epg into DVBViewer.

This works great on the first use. Then the second use it is all corrupt and trying to download

and import gives me an empty epg. If I check the channel pairings, instead of the channel

name it's just a random string of characters again and I have to repair all channels. This is very

annoying as my epg provider only offers a 3day epg so I need to repair channels every 3 days.

Does anyone know whats going on and why it's becoming corrupt? I've attached a pic of the

issue. Thanks in Advance.

 

 

cprrupt.png

Share this post


Link to post

Here is some of my Pairings.xml file:

Pairings.jpg.fec37639bf08769ddcc973c35f519dea.jpg

 

The 2310.honeybee.it is an XMLTV ID. Those should be the same between downloads.

From my XMLTV guide (honeybee.xml):

<channel id="2310.honeybee.it">
    
  <display-name lang="da">TV SYD</display-name>

  <url>https://honeybee.it/channel/tv-syd</url>

</channel>

 and later in honeybee.xml:

<programme start="20170510060100 +0200" stop="20170510063000 +0200" channel="2310.honeybee.it">

Try to check this out as a first attempt. The XMLTV IDs MUST be the same between downloads.

 

 

Share this post


Link to post

Is the source code for the tools available?

Share this post


Link to post
8 hours ago, DetlefM said:

 

Is the source code for the tools available?

 

No, sorry.  However. I shall be happy to answer any questions you may have. That's best done in the other thread raw-epg-values

Share this post


Link to post
Quote

 

Xepg version 0.7.1.0 is available

Fixed an error and added the option for inserting line breaks in the EPG Format Editor. Details in the changelog.

 

 


 

Quote

 

XGrabDMS version 0.1.1.1 is available

Fix: Forgot to UTF-8 encode the .LOG files created in invisible mode.
To upgrade: just replace the XgrabDMS.exe with the new one in your installation.


 

 

 

LineBreaks.jpg.787d627863a3ae29a37686c2f7891db9.jpg

 

 

 


 

Share this post


Link to post
Quote

 

Xepg version 0.7.1.1 is available

Fix: Too many blank lines in the output in some cases. Details in the changelog.


 

If you have upgraded to the 0.7.1.0 this upgrade is a must have. Sorry for the inconvenience:blush:

Share this post


Link to post

Is there any way to backup and restore the pairings?. I need to reinstall my OS soon and ive had to remap everything from scratch every time i reinstall the system. 

Share this post


Link to post

Yes, click link Xepg Data Folder in Xepg main window. Read the text file TheFiles.rtf for a description. The pairings are in the Pairings.xml and Config.ini is the Xepg settings.

1 person likes this

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Similar Content

    • ccristal
      By ccristal
      Hi!
      Is there any way to use the Recording Service to serve EPG data in XMLTV format to another device on my local network?
       
      Thank you!
       
      ccristal
    • ö-r-rf
      By ö-r-rf
      Ich fände es sehr nützlich wenn man die API des Recording Service so erweitern könnte dass man auch direkt EPG-Daten im XMLTV-Format abrufen könnte.
       
      Das würde den Austausch mit anderen Tools sehr vereinfachen.
       
       
       
      Alternativ könnte man die Daten auch templatebasiert auch noch in anderen Varianten verfügbar machen.
       
       
      Oder gibt es schon andere Wege an die Rohdaten heranzukommen um sie mit weniger Aufwand konvertieren zu können?