XMLTV problems

henk99 · #1 01-28-2005, 06:48 PM

Hi all

Since i have been using SageTV, i have also used the xmltv grabber (tv_grab_nl_wolf). This worked fine untill a few days ago. The site from Wolf stopped updating the xml files, so there was no more to download. However, there is also another grabber file called tv_grab_nl. This is a lot less detailed as the wolf version, so i'd rather not use that one.
Then, i found one by Amontillado, which downloads the data perfectly, but there appears to be someting wrong with the xml format, that gives an error that says 'unparseable'. I think i found out why that is.

Piece of Amontillado's version:

Quote:

- <programme start="20050128083000" stop="20050128084000" channel="1">
<title>NOS-Journaal</title>
<category>Nieuws/actualiteiten</category>
<url>http://www.nosnieuws.nl</url>
</programme>

Piece of Wolf's version:

Quote:

- <programme start="200501280730 +0100" stop="200501280740 +0100" channel="nederland1.omroep.nl" clumpidx="0/1">
<title>NOS-Journaal</title>
- <credits>
<adapter>NOS</adapter>
</credits>
<category>Nieuws/actualiteiten</category>
</programme>

The problem is in the +0100 part as far as i can tell. The importer appears to require this addition, that Amontillado's version doesn't have.

Amontillado mentions in his help file that a timezone can be set, like '+0100' and i also did so. However, this did not change the format of the file.

Can any of you guys help out here? I was ok with Wolf's version, but it stopped updating on his site. The normal version is just not detailed enough for me. Amontillado's version would be great, so i would love to get that working.

Henk99

nielm · #2 01-29-2005, 01:13 AM

The wolf version should be fixed shortly...
http://thread.gmane.org/gmane.comp.tv.xmltv.devel/4717

henk99 · #3 01-29-2005, 03:15 AM

Quote:

Originally Posted by nielm

The wolf version should be fixed shortly...
http://thread.gmane.org/gmane.comp.tv.xmltv.devel/4717

Hmmm..i can't make out that it will soon be fixed though......

In the meanwhile i have no epg data, so i would need a working alternative if possible. You know of one Nielm? Or perhaps a fix for amontillado's version?

Henk99

peter · #4 01-29-2005, 04:00 AM

You can use the following parameters with tv_grab_nl
--slow it will get detailed information
--offset days not to grab starting from today
--days number of days to get
It grabs 7 days including today. example xmltv tv_grab_nl --slow --offset 6 --days 1 grabs next friday.

Peter

nielm · #5 01-29-2005, 12:01 PM

Quote:

Originally Posted by henk99

Hmmm..i can't make out that it will soon be fixed though......

because Carlo is very quick at fixing things

a fix to ammontillado's could be done by post processing the data in tv_grep -- save the following in a bat file

Code:

xmltv tv_grep --eval "if ( ${$_}{start} =~ /^[0-9]{12,14}$/ ) { ${$_}{start} .=' +0100'; }  1" epgdata.xml > tmp.xml
xmltv tv_grep --eval "if ( ${$_}{stop} =~ /^[0-9]{12,14}$/ ) { ${$_}{stop} .=' +0100'; }  1" tmp.xml > epgdata.xml

(I hope this works -- I wrote it a while back for bad uk data!)

henk99 · #6 01-30-2005, 01:05 PM

Quote:

Originally Posted by peter

You can use the following parameters with tv_grab_nl
--slow it will get detailed information
--offset days not to grab starting from today
--days number of days to get
It grabs 7 days including today. example xmltv tv_grab_nl --slow --offset 6 --days 1 grabs next friday.

Peter

Hi Peter

Thanks for your info. I didn't know that function yet. However, i tried it and the option --slow is dead on

Veeeeery slow...lol

It did work however, so it is a good alternative for wolfs (for the time being).

Henk99

henk99 · #7 01-30-2005, 01:07 PM

Quote:

Originally Posted by nielm

because Carlo is very quick at fixing things

a fix to ammontillado's could be done by post processing the data in tv_grep -- save the following in a bat file

Code:

xmltv tv_grep --eval "if ( ${$_}{start} =~ /^[0-9]{12,14}$/ ) { ${$_}{start} .=' +0100'; }  1" epgdata.xml > tmp.xml
xmltv tv_grep --eval "if ( ${$_}{stop} =~ /^[0-9]{12,14}$/ ) { ${$_}{stop} .=' +0100'; }  1" tmp.xml > epgdata.xml

(I hope this works -- I wrote it a while back for bad uk data!)

lol Nielm, you probably know him, but i am still very new at this. However, your fix for Amontillado's version worked great. I imported it in sagetv and it displayed very good and detailed info.

A lot of thanks for this!

Henk99

nielm · #8 01-30-2005, 02:43 PM

I don't know him, but follow the XMLTV mailing lists, and see him reply quite quickly to problems... Glad the fix helped!

nielm · #9 01-31-2005, 04:26 AM

Just FYI: Looks like tv_grab_nl_wolf will work again now...

henk99 · #10 01-31-2005, 05:45 AM

Yep...i saw

His method does work a lot faster the the other options. However, when it stopped last week i had to look for something else. Glad it is working again.

Henk99

Amontillado · #11 01-31-2005, 03:40 PM

Quote:

The problem is in the +0100 part as far as i can tell. The importer appears to require this addition, that Amontillado's version doesn't have.

Amontillado mentions in his help file that a timezone can be set, like '+0100' and i also did so. However, this did not change the format of the file.

I just checked the grabber if this function got broken somehow, but it does still work on my pc.

I know you are using the wolf grabber again, but if you want you can send me the .ini and xml files so i can figure out what went wrong.

PS. please try the latest build (64) first to make sure you have the same problem with the current one (please note that if you are using a rather old version you can't copy the old ini, but you'll need to adjust the new one according to you needs).
http://www.cask-of-amontillado.com/f...ids_to_xml.zip

henk99 · #12 02-01-2005, 06:10 AM

Quote:

Originally Posted by Amontillado

I just checked the grabber if this function got broken somehow, but it does still work on my pc.

I know you are using the wolf grabber again, but if you want you can send me the .ini and xml files so i can figure out what went wrong.

PS. please try the latest build (64) first to make sure you have the same problem with the current one (please note that if you are using a rather old version you can't copy the old ini, but you'll need to adjust the new one according to you needs).
http://www.cask-of-amontillado.com/f...ids_to_xml.zip

Hi Amontillado

I am actually still using your grabber. I am usings Nielm's line to correct it. However, i would like to have it fixed. Because your grabber doesn't rely on files to be present for downloading like wolf's version. I have the latest build already in use. I would like to send it to you, but i don't know how

I don't know if i can through a PM, and this board won't let me e-mail it. So, perhaps you can send me a PM with your adres?

Henk99

Amontillado · #13 02-01-2005, 07:19 AM

Just pm-ed you the email adres, thanks for helping to figure out what is wrong.

Amontillado · #14 02-01-2005, 01:19 PM

henk99,

You now have

Code:

Timezone=0100

, this should be

Code:

Timezone=+0100

(only the + needs to be added)

One thing is important though, since the grabber can reuse previously downloaded data a change in the timezone will only affect the data downloaded after that change.
This means you need to delete the dayfiles once (the ones you have in the [CURRENTDIR]\Dagelijks\), after that the newly downloaded data will contain the correct timezone info.

Ps, since a complete download takes a while you might want to use fastmode once to test if it works now.

henk99 · #15 02-01-2005, 04:10 PM

Quote:

Originally Posted by Amontillado

henk99,

You now have

Code:

Timezone=0100

, this should be

Code:

Timezone=+0100

(only the + needs to be added)

One thing is important though, since the grabber can reuse previously downloaded data a change in the timezone will only affect the data downloaded after that change.
This means you need to delete the dayfiles once (the ones you have in the [CURRENTDIR]\Dagelijks\), after that the newly downloaded data will contain the correct timezone info.

Ps, since a complete download takes a while you might want to use fastmode once to test if it works now.

Weeeeeeeeeee...that worked!

I still know how i used it in the beginning. The first time i ran it, i used the default 9999 setting in the ini file. Later i thought...hmmmm..that might be wrong, so i set it to +0100. However, daily files were already made, so it didn't change the new files by adding the +0100. I then changed the +0100 to 0100 to see if that made any difference...off course it didn't.
After you wrote this i deleted the daily files and after that all went well

Amontillado · #16 02-02-2005, 02:14 AM

good to hear you got it working, let me know if something else comes up (or if there are any requests)

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)