Posts: 3
Joined: Apr 2019
Reputation:
0
I have a collection of home movies and would LOVE to tag family members as "actors" and then have them pull up my own personal bio of the family member/images into the extendedinfo actor panel. I know...sounds silly. Is there a way to bypass the various movie databases/scrapers for extendedinfo and just provide your own data? I provide all my own nfo files for Kodi so I know how to format XML for Kodi's scraping but I LOVE the extendedinfo panels for TV/Movies/Actors. Before I start digging through code, I thought I'd see if that's possible as a concept. I'm guessing the data would have to live in a Kodi database somewhere so I'm guessing my answer is no, but thought I'd give it some research.
Posts: 10
Joined: Aug 2019
Reputation:
0
Is there any update for this script? I tried to use it with the default (estuary) skin today, but i cant make it to work. I use Kodi Kodi v20.2 (Nexus).
ty
Posts: 243
Joined: Sep 2011
Reputation:
3
nonob
Senior Member
Posts: 243
Hi,
For my part, I never managed to get this script to work again and I switched to Embuary Info (see in my signature).
Bye
Posts: 1
Joined: Oct 2023
(2021-07-24, 22:09)scott967 Wrote: (2021-07-24, 03:35)Bungee_G Wrote: @scott967 have you seen the log ?
Also I don't understand why most of the skins use name=$INFO[ListItem.Title] while it's not accurate... dbid="$INFO[ListItem.DBID]" is.
Unfortunately your log shows plugin.video.venom installed, which is on the addon blacklist. So no further analysis can be given for that client.
However, I will advise that extendedinfo is working as designed. If extendedtvinfo is requested with a DBID, a query of the videodatabase is done to get the tmdb id for that DBID. If found the tmdb will be used to query tmdb site. If no tmdb id is in the database then the addon will not attempt to query tmdb for info.
In the case that extendedtvinfo is requested with the show title, the addon will query tmdb with the title and attempt to scrape the tmdb id. I don't know why the addon was designed this way; I assume there is a valid reason (my assumption is that if the show is in the database, it must have been scraped prior so the tmdb id should be available).
The tmdb v3 api query does allow for a tv "year first shown" query parameter and it is possible to add that as a parameter when skins request extendedtvinfo by adding year=$INFO[ListItem.Year]. I have added that for testing. It can also be used for movies, but in that case tmdb has 2 different year options: year, and first release year. Since Kodi only stores 1 premier value I assume that's first release year, but will have to look at the scraper code to verify.
scott s.
.
I assume this was never sorted out?
Or is there a fix available for Television info not being displayed?
Referring to when using Kodi 19.
Posts: 5,487
Joined: Jul 2012
Reputation:
385
I didn't get any notice that the previously key had expired, but I wasn't the dev who initially requested it. I was looking to see if any other tmdb scrapers had key problems, but didn't see any so I will probably submit a PR to the official repo this week with the new key.
scott s.
.
Posts: 5,487
Joined: Jul 2012
Reputation:
385
script.extendedinfo ver 6.0.7 was merged into official repo today 2024-01-21. This should resolve all tmdb api key issues. I changed the authentication method from passing the apikey in the query string to using the associated token in the http header. The script unique data is now in a hidden script setting. If you get an authentication fail please exit and try again as the setting needs to get pushed (by Kodi) to the userdata specific addon_data setting file.
I also tried to fix issues where the user tmdb session_id could be expired/refused by tmdb. I think this mostly applies if you logon to tmdb to save lists from within the script.
There's some possible issues with what responses from the sites get cached. Mostly not caching enough stuff. I don't think it is a user impact unless you are really hammering the sites with queries. I need to study more what needs to be cached per site.
I tried to make the script work a little better when user plays a youtube from the script video info dialog window. Problem is if the youtube fails to play for some reason -- age gate or no streams found for example. extendedinfo hides the dialog window while waiting for kodi to announce that the youtube has finished playing -- if the youtube never starts the script appears to hang. Now I have a hard-code 20 sec timer to wait for the youtube video to start; if it times out the dialog is restored. I think a full fix requires change to plugin.video.youtube.
Any other issues found please post here. There will be a ver 6.0.8 on my github for any beta / changes in work. When needed the next official ver will be 6.0.9.
scott s.
.
