Metadata Tools 4.0 Beta Thread (aka BMT 4.0)

[silkshadow]

Wow, MitchSchaft not cool man. Sean, if I had 2 grand laying around it would be yours.

[bikesquid]

I've got an issue that's got me stumped. ANY ideas would be hugely appreciated.

There are a few tv shows that I can't seem to get BMT data to stick.
from the BMT browser I go through a view till I find Murphy's law, Episodes S01E03, S02E02, S03E02 just show up as blank (all others are perfect). Sage recording is checked, media type is listed as Movie. Everything else is blank down to External ID, which in the case of the first one above is "MF1511313". Very different the the others that are more like "EPmt73425S01E01". Renaming to Murphy's Law - S01E03a gets the same external ID. If I go through the normal find metadata routine, it does find the right episode data from thetvdb and populates fields. When I hit save everything goes blank except Sage Recording, Genres and ExternalID... and the info stuff below that. I've tried renaming the file with the same result. There are 3-4 other series that have an episode that behaves the same and I've got no idea how to stuff the right data.... I don't think this is new behavior since the latest update as the .properties files did exist and were showing "0" for most of the info. I deleted them, and I have removed the video file and told sage to do a rescan with the root folder check set to true to try and eliminate carry forward. .properties aren't being created for these files when I put them back with a new name and either rescan or maually try and update via the webUI.

Anyone have any suggestions?

[stuckless]

I can't say why it would happen like this... but I've seen this happen myself. Sometimes the sage database just doesn't stick. I'd need to see the logs (logs/phoenix.log and logs/phoenix-metadata.log) to see if there was anything else happening.

Originally Posted by bikesquid

I've got an issue that's got me stumped. ANY ideas would be hugely appreciated.

There are a few tv shows that I can't seem to get BMT data to stick.
from the BMT browser I go through a view till I find Murphy's law, Episodes S01E03, S02E02, S03E02 just show up as blank (all others are perfect). Sage recording is checked, media type is listed as Movie. Everything else is blank down to External ID, which in the case of the first one above is "MF1511313". Very different the the others that are more like "EPmt73425S01E01". Renaming to Murphy's Law - S01E03a gets the same external ID. If I go through the normal find metadata routine, it does find the right episode data from thetvdb and populates fields. When I hit save everything goes blank except Sage Recording, Genres and ExternalID... and the info stuff below that. I've tried renaming the file with the same result. There are 3-4 other series that have an episode that behaves the same and I've got no idea how to stuff the right data.... I don't think this is new behavior since the latest update as the .properties files did exist and were showing "0" for most of the info. I deleted them, and I have removed the video file and told sage to do a rescan with the root folder check set to true to try and eliminate carry forward. .properties aren't being created for these files when I put them back with a new name and either rescan or maually try and update via the webUI.

Anyone have any suggestions?

[bikesquid]

Originally Posted by stuckless

I can't say why it would happen like this... but I've seen this happen myself. Sometimes the sage database just doesn't stick. I'd need to see the logs (logs/phoenix.log and logs/phoenix-metadata.log) to see if there was anything else happening.

Thx stuckless. Here's the logs referenced. I've seen similar issues when I tell BMT that something is media type TV and try to save it without a season or episode #, it then reverts back to a Movie and all title data disappears, but this problem seems tied to the sagedb and the show rather than what BMT is doing... as it just seems to happen with these specific shows regardless of the file name or the data I provide... I seem to be able to update other shows that I've tried. Granted this is my uneducated wild guess. If any other info is useful just lmk.

Any thoughts or ideas for a work around to get the files to show up correctly within sage greatly appreciated!

[stuckless]

Originally Posted by bikesquid

Thx stuckless. Here's the logs referenced. I've seen similar issues when I tell BMT that something is media type TV and try to save it without a season or episode #, it then reverts back to a Movie and all title data disappears, but this problem seems tied to the sagedb and the show rather than what BMT is doing... as it just seems to happen with these specific shows regardless of the file name or the data I provide... I seem to be able to update other shows that I've tried. Granted this is my uneducated wild guess. If any other info is useful just lmk.

Any thoughts or ideas for a work around to get the files to show up correctly within sage greatly appreciated!

Unfortunately, the log files show that everything updated without errors So, I'm not sure why the update wouldn't persist Do you have the option turned on to create .properties (it's on by default, unless you expliticly turned it off). If it is turned off, then try turning it on, and running your test again. Also does it fail the same way if "Import as Sage Recording" is toggled (ie, or or off)

[bikesquid]

Originally Posted by stuckless

Do you have the option turned on to create .properties

Yes, .properties should be (and are for all other files) created. For these I get nothing.

Originally Posted by stuckless

Also does it fail the same way if "Import as Sage Recording" is toggled (ie, or or off)

Tried that too, didn't make a difference.....

Could it be a corrupt video file? I renamed the first of the offending file, copied one of the 'working' ones to that non-working name and now the data takes. Did I just figure something out??

I've no idea why a jacked up video file would affect sage in that way, and haven't been able to test other offending files yet. Do you think it's possible?

[stuckless]

Originally Posted by bikesquid

Yes, .properties should be (and are for all other files) created. For these I get nothing.


Tried that too, didn't make a difference.....

Could it be a corrupt video file? I renamed the first of the offending file, copied one of the 'working' ones to that non-working name and now the data takes. Did I just figure something out??

I've no idea why a jacked up video file would affect sage in that way, and haven't been able to test other offending files yet. Do you think it's possible?

I can't say for sure, but I have seen where a "bad" video file can cause sagetv to behave badly... I once had a corrupt video file that prevented sagetv from starting So, anything is possible.

[bikesquid]

It's confirmed. I found 6 files that weren't updating in BMT. They wouldn't open or play in any of the various players I've got access too. Copy one suspected bad file over one of the others and same 'nothing' result. When coping 'good' files over the same name as a 'bad' file they updated just fine on an automatic scan, .properties created and everything is fine. Worked on all the suspect files. Now I've just got to wait for some obscure shows to come around again on the tele.

Would be great if there was a check/message when Sage finds a file is screwed up.... Clearly Sage is doing some test or trying to gather some info from the video file itself and failing... wonder if there is any api info in the docs about it. I'll take a look, but I'm usually outsmarted by the docs.

I realize BMT isn't the priority at the moment but I'll let U know if I do find something. This is likely useful for other projects in development/support.

Thx for taking a look at the problem, much appreciated!

[stuckless]

Originally Posted by bikesquid

It's confirmed. I found 6 files that weren't updating in BMT. They wouldn't open or play in any of the various players I've got access too. Copy one suspected bad file over one of the others and same 'nothing' result. When coping 'good' files over the same name as a 'bad' file they updated just fine on an automatic scan, .properties created and everything is fine. Worked on all the suspect files. Now I've just got to wait for some obscure shows to come around again on the tele.

Would be great if there was a check/message when Sage finds a file is screwed up.... Clearly Sage is doing some test or trying to gather some info from the video file itself and failing... wonder if there is any api info in the docs about it. I'll take a look, but I'm usually outsmarted by the docs.

I realize BMT isn't the priority at the moment but I'll let U know if I do find something. This is likely useful for other projects in development/support.

Thx for taking a look at the problem, much appreciated!

If you find something, let me know... the good news is that while I don't spend any time on BMT... all the metadata stuff is actually in Phoenix, and I spend time on Phoenix

[Taddeusz]

I'm not sure when it started but recently I've had the issue where retrieving metadata from tmdb is not working. It always gives the error "Unable to get Metatdata". TV lookups through tvdb work fine.

[stuckless]

Originally Posted by Taddeusz

I'm not sure when it started but recently I've had the issue where retrieving metadata from tmdb is not working. It always gives the error "Unable to get Metatdata". TV lookups through tvdb work fine.

could you send me the logs? (SAGE_HOME/logs/phoenix*.log)

Also, does it fail, using BMT web ui, or just the automatic update?

[Taddeusz]

Originally Posted by stuckless

could you send me the logs? (SAGE_HOME/logs/phoenix*.log)

Also, does it fail, using BMT web ui, or just the automatic update?

There is nothing in the log. It fails on both the automatic update and using the web ui.

[Taddeusz]

Oops. It did write something to the log. Here it is.

[stuckless]

Originally Posted by Taddeusz

Oops. It did write something to the log. Here it is.

The log files is showing that it is updating (no errors). That is very odd.

[Taddeusz]

Originally Posted by stuckless

The log files is showing that it is updating (no errors). That is very odd.

Yea, here is the error screen just to show that it does happen.

[stuckless]

Originally Posted by Taddeusz

Yea, here is the error screen just to show that it does happen.

oki... zip up all the logs in the logs/ directory and add in the sagetv_0.txt log file as well, and send me those. Maybe there's an error in another log file somewhere.

[mxg]

Originally Posted by Taddeusz

I'm not sure when it started but recently I've had the issue where retrieving metadata from tmdb is not working. It always gives the error "Unable to get Metatdata". TV lookups through tvdb work fine.

I'm observing the same thing. TV shows and Movies imports. Even manual updates via BMT come back with "Unable to get Metatdata". I noticed the issue this past week. It seem to have started after a phoenix core update I think? Just sharing the info for what's it worth..

[stuckless]

Originally Posted by mxg

I'm observing the same thing. TV shows and Movies imports. Even manual updates via BMT come back with "Unable to get Metatdata". I noticed the issue this past week. It seem to have started after a phoenix core update I think? Just sharing the info for what's it worth..

I just updated my main server to run the absolute latest phoenix (yeah, even though I develop Phoenix... I don't always run the latest on the main server )... And I did do a few tests and I was able to update a bunch of movies using bmt.

You can always use the Help -> Create Support Request option in BMT which creates a .zip of your log files and email to me. (address provided in the support dialog).

What I suspect is happening, is that the SageTV plugin system is NOT extracting all the required libraries for Phoenix and as a result tmdb isn't working... but the complete log set should hoperfully shed some light on this.

[adone36]

If the changes were supposed to affect the IMDB lookup in the BMT GUI, They didn't. It still finds the film but returns "unable to fetch" when you select something.

TheMovieDB is not working either, but it also does not work from their own web site. You get an "error 500".

[Taddeusz]

Sorry it took me so long. Busy weekend. Finally submitted a support request for the "unable to get metadata" problem.