[mythtv-users] metadata

jam at tigger.ws jam at tigger.ws
Mon Dec 10 03:44:55 UTC 2018


Before I bug the dev list will try here to see if anyone here can help …

I run mythmetdatalookup in debug mode:

2018-12-10 11:01:46.753301 I  All grabbers tested and working.  Continuing...
2018-12-10 11:01:46.757768 I  MythCoreContext::ConnectCommandSocket(): Connecting to backend server: (try 1 of 1)
2018-12-10 11:01:46.759350 I  MythCoreContext::CheckProtoVersion(): Using protocol version 91 BuzzOff
2018-12-10 11:01:46.762151 I  Looking up artwork for recording rule: Default (Template)
2018-12-10 11:01:46.853772 I  Running Grabber: /usr/share/mythtv/metadata/Movie/tmdb3.py -l en -a US -M Default (Template)
2018-12-10 11:01:48.558200 I  Running Grabber: /usr/share/mythtv/metadata/Television/ttvdb.py -l en -a US -M Default (Template)
2018-12-10 11:01:50.512894 I  Metadata Lookup Failed: No Results Default (Template) 0 0
2018-12-10 11:01:51.774389 N  MythMetadataLookup run complete.

I don’t have, and don’t understand why I would have metadata enabled in a recording rule.
From the source it is clear (and the log shows this) that if recording rule lookup fails then the run terminates before the lookup on videos starts.
What dummy record rule can I try that will proceed beyond this point.

I see the grabbers produce xml output that seems good.


More information about the mythtv-users mailing list