#Has Prime Video Streaming Name Changed?
1 messages · Page 1 of 1 (latest)
Welcome @primal gorge!
It looks like you have not yet completed the id:customize section of our Discord server, this will allow us to help you quicker.
Someone from <@&938443185347244033> will assist when they're available.
Including meta.log from the beginning is a huge help. Type !logs for more information.
After attaching your log, do not forget to hit the green check boxes when prompted by our bot.
You can press the "Close Post" button above or type /close at any time to close this post.
Can you provide an example and we will check it out?
Yes, of course.
I have a series that can be seen on Prime Video in my country.
https://www.justwatch.com/es/serie/perverso
https://www.themoviedb.org/tv/239663-perverso/watch
In the TMDB API response json, it responds like this:
"ES": {
"link": "https://www.themoviedb.org/tv/239663-perverso/watch?locale=ES",
"flatrate": [
{
"logo_path": "/pvske1MyAoymrs5bguRfVqYiM9a.jpg",
"provider_id": 119,
"provider_name": "Amazon Prime Video",
"display_priority": 3
},
{
"logo_path": "/8aBqoNeGGr0oSA85iopgNZUOTOc.jpg",
"provider_id": 2100,
"provider_name": "Amazon Prime Video with Ads",
"display_priority": 82
}
]
},
As you can see, the provider name is Amazon Prime Video instead of Prime Video. Could this be the reason why none of my series are being localized for Spanish?
Sorry, I think I know what's going on.
Amazon is set to tmdb_key: 9
and there are now a lot of "Amazon Prime Video" ids in tmdb.
These ids:
9|119|613|2100
I'm doing local testing with this setup.
It seems that works
Ok, I understand the "Watch Providers" output.
For ES, I should use Amazon ID 119. Just like in CA, AU, and NL, as shown in the image.
I'll add "ES" there and run new tests, leaving the original Amazon ID at "9" (not adding the pipe and the previous IDs).
Let me know if that works as you expect
We can update the file or you can submit a PR
@primal gorge didn't realise you were the same person as the movistar stuff, can you test nightly for the movistar change? I've merged it
Haha, yes, that's me.
I'll update my Docker version with nightly, although I already tested my changes by manually updating the files inside the container.
It works perfectly.
I did this because I broke my leg two months ago and now I have time to study this project and get it working in my library. I realized the streaming services for my country were missing, so I submitted "Movistar Plus+."
Today, at my location, I added and/or fixed at least 3-4 streaming services for Spain. If you think this might make sense for the project, I'd be happy to run a PR for each of them. What I would need is to know the requirements for the logos. I don't know if they have to be a specific size or if you can tell me a library from which to get the official logos.
This is the final result.
In green, the new features I've fixed or added to my version.
- There are networks with incorrect names (Atresplayer => Atres Player)
- Prime Video in ES region is 119
- I've added AMC+ because it's missing (528|1854)
- I've added Filmin because it's missing
- Netflix can also be "1796", in addition to tmdb_id = 8
Feel free to submit your PR(s)
Okay. Thanks.
To do this as best as possible... can you tell me if there are any guidelines for the logos?
I saw that the PR I posted with the new HBO Max logos was considered, but it was done with other logos. If you tell me where to look for them, their size, or their characteristics, I'll do the same.
Is this an issue?
I understand that "both" is for collections and "overlays" is for overlays. But I'm not sure they have to have different settings for these types of things. I'm not in the "CA" region, so I don't know if this is a bug.
I will review later today for you
@sturdy oriole may know the guidelines about sizes for overlay images etc
Thanks @onyx island
In the meantime, I'm creating some PRs with some minor fixes.
I'm waiting for @sturdy oriole instructions for the images.
Hahaha, I think I'm going to cause some conflicts with the PR 😅😅😅
Hey there
So for the images, the default images repo is the source and there is automation to create those files. For overlays, the source is within the defaults/overlays/images of the kometa repo.
So there are several things to be aware of...
Bigger, standard
Color, white
These are variations so what we do is find the right size in the default images repo, and then manually copy them in to replace or add the missing logo within the kometa overlays.
So it's hard for me to tell you the exact sizes because we respect certain limits and auto size to fit within those limits
Some logos are really wide and square, some really tall and narrow... and some are perfectly square.
The best ones for overlays are typically short and wide so they can take up the most room in the lozenge.
If a logo is nowhere to be found, then we need to get the right logo, reprocess it with our automation(white, color, bigger, standard, logos, collections, etc) and then push it back to the repo.

Heading out to golf now so if I don't reply it's because I can't. 😉
I'm not entirely sure what automation you're referring to.
I wanted to integrate this logo: https://es.wikipedia.org/wiki/Archivo:Logotipo_Filmin_2023.png
I don't want to do it wrong.
If the tool is internal, I ask you to do it. If it isn't, I ask you to tell me where it is so I can generate those images.
This logo isn't in the defaults.
If you are going to add a logo for a network, you would PR it into this repo:
https://github.com/Kometa-Team/Default-Images
Into this folder:
https://github.com/Kometa-Team/Default-Images/tree/master/network/logos
There is then automation that you don't need to worry about that generates the variations.
Due to the wide variety of logo shapes, there is no single "it should be this size". You can look at the logos that are already there to get an idea.
Sorry I should have been a little clearer... on my GitHub, I have something called create_default_posters.ps1.
We add the new logo to the right section, run the automation, it produces all the outputs. I do a folder diff across all folders and push the difference to the default-images repo...
So adding something to the default-images repo directly means that it won't run through with the create_default_posters.ps1 automation
So honestly... the easiest is to ask and I can produce them pretty easily...
I have been in this ps1 file for 3 years now so it's super easy..
So just let us know what the logo is and the correct name for the file... the rest we can handle.
I stand corrected.
I apologize because I didn't understand anything when I read @kind kraken's message, haha.
I'll give you the information so you can generate the image with your tool for the new streaming provider:
Image: https://es.wikipedia.org/wiki/Archivo:Logotipo_Filmin_2023.png
Thanks, @sturdy oriole
I have the code ready to send the PR when this logo is available. I don't want to do it before then to avoid errors.
What type of image is this? Network, Streaming, Studio?
Based on the above PR, it's streaming.
Additionally, your "code" would be some yml updates, right?
https://kometa.wiki/en/nightly/defaults/both/streaming/
and
https://kometa.wiki/en/nightly/defaults/overlays/streaming/
for the collection and the overlays...
Yml changes would be needed for both and the wiki page updates as well.
create_default_posters.ps1 is running and will create the appropriate overlays, and collections for streaming.
Likely, you will need to go and grab the correct overlay from the repo once it's pushed to add to your PR since overlays are not pulled from the repo, but from the kometa directory itself.
Correct, it's a streaming service (https://www.filmin.es/).
And yes, I have the code ready with all the yml and documentation modifications. This is the fourth streaming service I've created in the last few days, but it's the first one without an original image. For the other 3, I've been able to reuse the "networks" logo since those "networks" are also streaming services in my country.
When the image (Filmin) is in the repository, I'll download it and include it in the Kometa PR to add the new streaming service.
Thanks a lot, @sturdy oriole
To give you an idea...
Pushed. Note that 1 streaming addition of Filmin, produced 14 files
Network and studio would be similar...
Can you share the other 3 please so we can verify that the ps1 script?
So for Movistar +, there is a color logo, however, both white logos were placed in the color and the white overlays folder. Additionally, I don't think the corresponding collection posters were created and those should have been added as options in the streaming collections potentially? Or maybe there isn't a color logo...
Movistar + does not have a color logo in 2025. That is why it was reused for color and white.
Movistar +
Atres Player --> Same as AtresPlayer Premium, but changed name
AMC+ ---> New Streaming, but logos exists on "Network", so I reused.
I saw in the PR for new images that I had to create the corresponding covers for "Originals," "Movies," and "Shows."
I didn't know I had to create them, and I never did it with Movistar 😅
FYI, I produced a bunch of those logos for use in your PRs. AMC+, Atres Player, Movistar Plus+, Filmin.
They are all in the default images repo now.
Each of the overlays will typically have a set of collections as well. So the idea is that if you add an overlay, make sure to adjust the yml for the collections in that family...
And vice versa, if you add an overlay collection, add the corresponding overlay.
Family being things like, network, studio, streaming, franchise, audio_codec, video_format, etc.
Overlay images need to be PR'd into the kometa repo.
Collection images need to be pushed into the Default-Images repo for kometa to pull from.
And finally, wiki needs adjustment based on family as well... so both network overlays and network collections would need an adjustment if you altered the yml for them.
Thank you. I will do my best to meet these requirements. I will review the PR in case there are things missing.
I'll wait for some to merge to avoid local conflicts since all PRs come out of Nightly and edit the same files.
I don't know which ones are good to merge?
Theoretically these:
https://github.com/Kometa-Team/Kometa/pull/2756/
https://github.com/Kometa-Team/Kometa/pull/2757/
https://github.com/Kometa-Team/Kometa/pull/2758/ --> Because @sturdy oriole has already created the images of the collections in the official image repository and I have transferred the logo to have an overlay to the PR
I left a comment on the first PR: 2756
bull can you leave a comment on the GH PRs when they are good to merge please, I'll follow your lead
Sure... I'll do my best
3 reviews completed, 1 approved
Thanks, boys
Pretty sure I approved the last two today
I promise not to bother you anymore for now.
This is the last one 😊
Add Filmin: https://github.com/Kometa-Team/Kometa/pull/2767/
Do the collection images exist for that?
Yup
Merged
antwanchild used !aenh
@primal gorge, anything else needed here? If not, please type /close and hit enter. Please respond within 24 hours of this message or it will be archived.
/close