YahooXMLTv (requires Go for TV)

[Jim_]

I’ve updated I-xmltv and the new show marker and many other things appear to be working fine using your xml files. After I bug test it (I-xmltv) a little more, I’ll post it in a different thread (not to take this thread off-track) and post a link here for people who want to try it.

Sweet cause it's working great. With the I-XMLtv i'll be able to get like the aired and new things

Most of the data is in the exported file. Jim_ is working on an update for I-XMLtv to take advantage of it.

The updated I-xmltv is posted here.
http://forums.nextpvr.com/showthread.php...post207845

Initial testing looks good <fingers crossed>

[tiger66]

Hi Whurlston. Thanks for the great app!

I'm having a small problem with it, though. The name of my listings file has spaces (or could it be the parentheses?) and I believe it's causing the application to crash. Here's the output:

C:\YahooXMLTv>YahooXMLTv.exe days=5
07/09/2007 20:52:54 -- Starting Update.
07/09/2007 20:52:54 -- Processing Lineups.
07/09/2007 20:52:54 -- Lineup 1 of 1: Comcast Forsyth/Bartow (Atlanta)
07/09/2007 20:52:54 -- Downloading new listings. Attempt 1 of 3.
07/09/2007 20:54:13 -- Download successful. Processing new listings.
07/09/2007 20:54:13 -- Found 68 channels.
07/09/2007 20:54:14 -- Channels processed.
07/09/2007 20:54:14 -- Found 9674 programs for 5 days.
07/09/2007 20:56:07 -- Programs processed.
07/09/2007 20:56:07 -- Saving Xml.

[COLOR="Red"]Unhandled Exception: System.IO.DirectoryNotFoundException: Could not find a part
of the path 'C:\YahooXMLTv\Comcast Forsyth\Bartow (Atlanta).xml'.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, I
nt32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions o
ptions, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)[/COLOR]
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access,
FileShare share)
at System.Xml.XmlWriter.Create(String outputFileName, XmlWriterSettings setti
ngs)
at YahooXMLTv.Program.ProcessLineups()
at YahooXMLTv.Program.Main(String[] args)

Or am I just doing something wrong?

Thanks!

Aha! I should have looked closer. It appears that the forward slash in the Forsyth/Bartow is being re-interpreted by the utility to be a backslash and is being used as part of the path specification. Any easy way to fix this (like allowing an output filename as a parameter)?

Thanks!

[whurlston]

Aha! I should have looked closer. It appears that the forward slash in the Forsyth/Bartow is being re-interpreted by the utility to be a backslash and is being used as part of the path specification. Any easy way to fix this (like allowing an output filename as a parameter)?

Thanks!

I wondered if any names would cause a problem. I'll post a fix tomorrow. In the meantime, you can try adding a subdirectory called "Comcast Forsyth".

[jim08127]

Hmmm, yesterday I had 12 days worth of listings through 7/20. And this morning I have 11 days worth through 7/20. The xml file is being modified though as it is dated today. Obviously there is a problem, is there a log file I can look at to see what is happening?

[tiger66]

I wondered if any names would cause a problem. I'll post a fix tomorrow. In the meantime, you can try adding a subdirectory called "Comcast Forsyth".

Duh... I should have thought of that. I guess I got in kind of a hurry last night. At first I didn't realize the "backslash" problem... I thought it was spaces or the parentheses. After I realized the real problem, I just did a quick post to follow up without thoroughly thinking about it. Sorry.

Anyway, thanks! I appreciate the help.

[whurlston]

Hmmm, yesterday I had 12 days worth of listings through 7/20. And this morning I have 11 days worth through 7/20. The xml file is being modified though as it is dated today. Obviously there is a problem, is there a log file I can look at to see what is happening?

All messages are sent to the console. You would have to redirect them to a file. But the only information that you would get from the messages that somewhat relates to this is the number of programs if processes.

I would open the Y! database in SQL Admin and see if there are any listings in it beyond 7/20.

[mulletback]

I'm using the latest (?) version of the YahooXMLTv app to get EPG - I'm seeing stuff like this in the guide: The OCC crew continues work on the &quot;Caddyshack&quote; bike (italics are mine) - it appears this way in the xml file itself. In the web version of the guide it renders this way: The OCC crew continues work on the "Caddyshack&quote; bike(again, my italics). Obviously, &quote; is simply wrong in the xml, but what's up with &quot; failing to render in the on-screen guide?

[eoren1]

I installed Yahoo TV to go and set it up.
Downloaded the YahooXMLTv program and extracted to devnz/gbpvr/XMLTv directory
Ran successfully
Opened gbpvr settings and changed to direct recording plugin and xmltv plugin and pointed to xml file created
Channels populated correctly in settings program
Opened gbpvr and the TV guide shows the channels on the left but the listings are blank.
I've tried this several time with emptying and reloading. Also ran through listing forward and back 7 days but no listings...
Any thoughts?
Thanks,
E

[whurlston]

I'm using the latest (?) version of the YahooXMLTv app to get EPG - I'm seeing stuff like this in the guide: The OCC crew continues work on the &quot;Caddyshack&quote; bike (italics are mine) - it appears this way in the xml file itself. In the web version of the guide it renders this way: The OCC crew continues work on the "Caddyshack&quote; bike(again, my italics). Obviously, &quote; is simply wrong in the xml, but what's up with &quot; failing to render in the on-screen guide?

It did not fail to render in your example. &quot; is the " character. &quot; should not have an e on the end. I have a couple of other changes to make so I will fix that while I'm doing them.

[mulletback]

It did not fail to render in your example. &quot; is the " character. &quot; should not have an e on the end. I have a couple of other changes to make so I will fix that while I'm doing them.

No, you're not following me - in the normal gbpvr guide, or in search guide, &quot; is showing up as &quot;, not as ". In the web interface to the guide, where a browser is rendering html, &quot; does show up as ". Is gbpvr seeing and rendering &quot; properly?