Tosh.0 (2 Viewers)

[shuck]

For some reason, I am unable to import Tosh.0. It exists on thetvdb.com, but even when trying a custom search for "Tosh" it returns empty. All of my other series (4000+ files) seem to import fine. Has anyone else had this problem? Has anyone had success importing Tosh.0 episodes?

Thanks!

 

[ltfearme]

Could be because the thetvdb is having problems at the moment. Been going up and down the last few days.

 

[ryan20021982]

I had to do them manually on all clients about a month ago

 

[RoChess]

For some reason, I am unable to import Tosh.0. It exists on thetvdb.com, but even when trying a custom search for "Tosh" it returns empty. All of my other series (4000+ files) seem to import fine. Has anyone else had this problem? Has anyone had success importing Tosh.0 episodes?

Thanks!

Please provide more details, I can't test to see if there is a mistake in the regular expression because you did not provide full filename, nor MP-TVSeries and MediaPortal versions you use, nor import path details, any settings that could cause a problem such as custom string replacement rules, or tons of other things that might be a reason.

If a program has 10 settings it means there are 3,628,800 different combinations possible, if a program has 11 settings there are 39,916,800 combinations possible, if a program has 12 settings there are 479,001,600 combinations possible.... well there are 50+ settings on MP-TVSeries, so you do the math.

MediaPortal and MP-TVSeries exact version numbers = MediaPortal v1.1.0.0
Import Path = <drive>:\<folder> or \\UNC\Share
Full problem file location = <drive>:\<folder>\folder\file or \\UNC\Share\folder\file
non-default string replacements = .... (use 'reset' otherwise to ensure you are using default ones)
non-default regular expressions = .... (use 'reset' otherwise to ensure you are using default ones)

And the final kicker, provide: MediaPortal.log and MP-TVSeries.log in debug mode (so they actually show useful info)

The above makes actual help possible, otherwise it's a guessing game.

 

[shuck]

Here is an update:

The importer was properly parsing the episode file names. The problem was two-fold.

1) thetvdb.com was having trouble, which was making it hard to truly determine this source of the problem.

2) when the string "tosh.0" is passed to thetvdb.com, it comes back empty, but if you manually change the name (or change your filenames) to "tosh0" then it finds "tosh.0" on the server and downloads the correct info.

I didn't provide the log files because I was pretty sure the problem was with how thetvdb.com was handling an epxression with a "." in it. The main purpose of my post wasn't to report a bug, but to see if anyone else had had this particular problem with this series since the name has some non-alpha characters in it.

 

[RoChess]

2) when the string "tosh.0" is passed to thetvdb.com, it comes back empty, but if you manually change the name (or change your filenames) to "tosh0" then it finds "tosh.0" on the server and downloads the correct info.

That doesn't make any sense, because:

http://www.thetvdb.com/api/GetSeries.php?seriesname=Tosh.0

Gives the right results back as expected. The log files would have showed what really went wrong (provided they are configured in the right mode).

The whole idea behind MP-TVSeries is to run as much automatic as possible. So if 'Tosh.0' or any other show is not properly matched, that is a bug, and it needs to be fixed. Provided of couse it is a bug in the program and not something unique to your setup.

If TheTVdB.com has problems and it ends up causing things to go wrong, then extra code will need to be added to ignore the bad data and instead display a message "There seems to be a problem with TheTVdB, please try again later". But it requires a high amount of Artificial Intelligence to be able to determine what 'correct' is. And unless SkyNet is for real, we are still far away from that level of computer intelligence. The best a developer can do is compensate for as many variables as possible.

The problem then is, that when they never see such problems, they can not solve it. That's what log files are for, allowing a developer to see what their code is doing on your system, the one having the problem. But this can only work if the user is willing to do the following:

1. Reproduce the problem (otherwise how can it be verified that the problem is fixed?)
2. Explain the configuration of their system (step #4 can do most of this)
3. Explain the steps they took to cause the problem (in as few steps as possible to make it easier to locate the cause)
4. Provide the log files in the right mode, debug or debug+SQL, so they reveal exactly what was going on

Enjoy.