Episode Names and Descriptions

[can3gxw]

Please let me know if this is NOT a BMT question, but since it's SO good at what it does, I am wondering if perhaps there might be something amiss here...

I have been seeing, as of lately, that I am not getting the full metadata for my imported tv shows. I have TVRENAME running to ensure that the filename is "perfect", and it's been working perfectly until sometime in the recent past (can't be exactly sure when). Maybe something got changed that I can't find, which is why I am throwing this to the forum.

I can go to TVDB and look up the details on a specific episode of a show, and the full episode name and description are there, but the metadata will just not download to Sage. I know that all changes made to TVDB only actually update the server about once every half hour or so, but episodes that have been on TVDB for a few days won't even always come down.

I say "not always", only because I haven't been able to reproduce it all the time...

Anyone have any ideas what's happening and why I can't always get ALL the information from the TVDB?

[stuckless]

I've seen a few "timeout" errors with tvdb lately. BMT should retry on a timeout error, but it will eventually give up.

Do you see anything interesting in the phoenix-metadata.log or the phoenix.log?

[can3gxw]

Where are those logs hiding? I can certainly take a look the next time something doesn't work right....

Is there a "wait for xx seconds (or minutes) after scan complete to download the information"? I get it that if I am updating a LOT of files it could take a while, but if it's only a half dozen I wouldn't think it would be that long.

But again, I'd like a little more insight into what does what behind the scenes so that I don't hit the alarm too soon. If BMT takes on average 5 seconds per file, then if I look 2 or 3 minutes later, it should be done. If it takes 1 minute per file, I'll check it again in, say, 5 minutes.

But yes, I also get that everything is dependent on TVDB actually working.

[stuckless]

all the logs are in the SAGE_HOME/logs/ folder... The next time something fails, just check the phoenix-metadata.log and the phoenix.log and see if you notice anything interesting... or zip them up and send them my way

[can3gxw]

Will do. Thanks!

[can3gxw]

It happened this morning...

- Great Food Truck Race S02E06 - worked perfectly
- Charlies Angels (new series) was pulled wrong as a movie... ? whatever... LOL (not too worried - just added a MATCHER for it... we'll see what happens next week)
- Person of Interest - S01E01 - did not extract anything or update any metadata (auto SAGE refresh). When I used BMT web, I was able to manually search for the metadata and update it, but it only updated the series name (not the episode or episode description).

Here are the logs for you to look at... let me know if you see something, or if there's something else that I should be setting.

[stuckless]

Originally Posted by can3gxw

It happened this morning...

- Great Food Truck Race S02E06 - worked perfectly
- Charlies Angels (new series) was pulled wrong as a movie... ? whatever... LOL (not too worried - just added a MATCHER for it... we'll see what happens next week)
- Person of Interest - S01E01 - did not extract anything or update any metadata (auto SAGE refresh). When I used BMT web, I was able to manually search for the metadata and update it, but it only updated the series name (not the episode or episode description).

Here are the logs for you to look at... let me know if you see something, or if there's something else that I should be setting.

I'm seeing a lot of

com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 1 of 1-byte UTF-8 sequence.

Errors in the log when it's parsing the xml from TVDB... it looks as if tvdb is giving back the incorrect xml... OR... BMT/Pheonix has a corrupted file in the cache.

You can try to delete the userdata/Phoenix/cache/url/ folder and then try the person of interest again to see what happens.

I'll open a bug to look at this in more detail.

[can3gxw]

I just went into the web interface and ran a manual "find metadata" and it returned all the right information... weird.... don't know what to say now.

Since I have my "tvrename" and "sage scan" in a batch file, would it do any harm to delete all the contents in the CACHE before running a scan? Do you think it might help?

And by "userdata", you're referring to the %userdata% in the "HTPC" user's Windows profile, correct?

[can3gxw]

NM - found the userdata deep in the SageTV folder.....

[stuckless]

FYI... I have confirmed that is a bug in the Phoenix/BMT url caching code... Until I get a fix out (which will be a few weeks), you can manually avoid the issue by cleaning out the SAGE_HOME/userdata/Phoenix/cache/url/ folder.

[skiingwiz]

Originally Posted by stuckless

FYI... I have confirmed that is a bug in the Phoenix/BMT url caching code... Until I get a fix out (which will be a few weeks), you can manually avoid the issue by cleaning out the SAGE_HOME/userdata/Phoenix/cache/url/ folder.

I had the same issue with thetvdb, but my finding was different. As it turns out, they are sometimes (not always, frustratingly) sending the data GZip compressed. I had found a forum post about it at http://forums.thetvdb.com but it seems that currently their developers forum is offline.

I fixed my issue by wrapping the URL's InputStream in a GZipInputSream (whenever I saw this exception).

I just thought I'd post in case it turns out that you are having the same issue.