Jump to content

Grabbing the wrong movie cover after changing it on the server


BasJaspers

Recommended Posts

BasJaspers

The problem is a bit hard for me describe but I will do my best to make it is as logical as possible.

 

I added the movie "The perfume" to my movie library. This movie was indexed wrong by the Emby server so I indexed the correct with the meta data manager. No problem so far.

When i look in Kodi all is correct: Meta data is correct and the cover is correct.

 

But when I fetch the cover trough JSON I still get the wrong cover. I double checked the string I received trough JSON and checked the cover on my PC to be sure that it was no cash problem on my tablet. But also on my PC i get the wrong image.

 

To fetch the covers i use the following method:

{"jsonrpc":"2.0","method":"VideoLibrary.GetMovieDetails","params":{"movieid":20,"properties":["thumbnail"]},"id":2}

This results in the cover string. In my case:

image://http%3a%2f%2f172.16.63.31%3a8096%2femby%2fItems%2ff702bdc264c8cb272a77390cd6596180%2fImages%2fPrimary%2f0%3fMaxWidth%3d10000%26MaxHeight%3d10000%26Format%3doriginal%26Tag%3d5194b09b9b665a60fe92bd03688068d6

From this string i remove the information which results in the following string:

image://http%3a%2f%2f172.16.63.31%3a8096%2femby%2fItems%2ff702bdc264c8cb272a77390cd6596180%2fImages%2fPrimary%2f0%3f

Then I URL encode the string resulting (This is necessary for Kodi to push a thumbnail):

image%3A%2F%2Fhttp%253a%252f%252f172.16.63.31%253a8096%252femby%252fItems%252ff702bdc264c8cb272a77390cd6596180%252fImages%252fPrimary%252f0%253f

And as a last step I add the path of the Kodi client so my tablet can reach it:

http://172.16.63.163:8080/image/image%3A%2F%2Fhttp%253a%252f%252f172.16.63.31%253a8096%252femby%252fItems%252ff702bdc264c8cb272a77390cd6596180%252fImages%252fPrimary%252f0%253f

This all works fine but now I am getting the wrong cover image on my tablet while Kodi is displaying the correct one within the movie information page. This seems to be related to the Kodi database as far as I understand, but I am not that familiar with databases.

 

I hope someone can help me fix this problem.




			
		
Link to comment
Share on other sites

CharleyVarrick

In similar situation, here's what I do.

1) I remove the movie folder (and all included files) out of emby monitored folder

2) delete all art and nfo

3) drink half a beer, the top half preferably (wait 2 minutes)

4) import back movie folder (including movie file only) back to original monitored location

5) let emby and kodi do their magic

Edited by jlr19
  • Like 1
Link to comment
Share on other sites

BasJaspers

When it was just one kodi client I would say this is a reasonable option. But with 6 clients this is no fun. Especially if it happens once every 20 movies or so that are uploaded.

Before I used emby I had this problem with all meta data. Now the problem only remains for covers.

But I just remembered that I am using direct paths maybe it works correct with indirect paths. I wil give it try tomorrow and post the result.

Link to comment
Share on other sites

BasJaspers

I tested with Emby (default) path instead of indirect paths, but the result is the same.

Is there an other way than re syncing the database every time you change a cover?

Link to comment
Share on other sites

BasJaspers

Made a workaround to fix the problem. Still wondering why in default it does not work as intended.

 

What I did is the following:

 

The string that i already receive:

image://http%3a%2f%2f172.16.63.31%3a8096%2femby%2fItems%2ff702bdc264c8cb272a77390cd6596180%2fImages%2fPrimary%2f0%3f

Remove "image://"

URL decode the string what results in:

http://172.16.63.31:8096/emby/Items/f702bdc264c8cb272a77390cd6596180/Images/Primary/0?

So now I am not longer using the Kodi webhost and thumb generator but the emby version.

Link to comment
Share on other sites

CharleyVarrick

When it was just one kodi client I would say this is a reasonable option. But with 6 clients this is no fun

I have only 2 Kodi clients, but my suggestion should fix issue for any number of clients as the action is done on Emby server side, who in turns (should) updates all its clients.

Edited by jlr19
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...