XMLTV Importer problem

[Peter Vogel]

I've modified the xmltv importer to accept a non-standard epg file format I have.

It seems to do the right sort of things, but the generated databse does not seem to be readable by SS. When I start the Guide I get "epg data low" message and all entries say "unavailable".

I wonder if it's to do with the date format being non-US (I'm in Australia). The long integers used for the date/time are yyyymmddhhmmss when written to the database.

Perhaps if I attach the databse I just built someone can spot what I've done wrong.

Many thanks,

Peter

[Peter Vogel]

Anyone got any suggestions on how I might proceed to debug this problem?

Perhaps someone has a document decribing the stucture of the SS database, so I can check that I've got it right.

It might also be helpful if someone could send me a sample database from their setup which is working (of course the contents would be nonsense where I live) so I can at least see how Snapstream looks with a working guide databse.

Thanks,

Peter

[mrphil]

Sorry didnt reply sooner, been away for a couple of weeks.

Anyway, in your database, the first thing I notice is that your channel numbers are not padded. Both TMSCHAN and STATIONNUM should be padded out to 3 digits, like this

011
012
015
003
009

If you do not pad to 3 digits it wont work. Make sure that stationnum in the station_table is identical to the corresponding entry in the episode_table. both fields must be "003" for channel 3.

[Peter Vogel]

Yes that was the problem. All's well now, except the epg shows channel 0 when there isn't one. Any ideas onthat?

Thanks,

Peter

[mrphil]

It will show channel 0 if you only have a certain number of channels, less than 6 I think. Its a known "feature" in PVS 3.

[Vuillard]

Originally posted by Peter Vogel
I've modified the xmltv importer to accept a non-standard epg file format I have.

Peter

Since you are in Australia I assume that you have modified this to download an Australian EPG and use it with Snapstream. Can you tell me how you did this? Is there a part of Snapstream that is easily modified to achieve this result?

Regards
James Marsh