antp.be forum

IMDB 5.4 beta 1

CHANGELOG:
* improved localization
* BatchMode: added mode 3 to import from IMDB custom field
* DescriptionSelection: new default value is 0 (short plot description works better with localization)
* PopularSearches: new default value is 1 (0 is too strict on search results)

2 words on improved localization. The new version changes how iMDB works. In previous versions the UserCountry parameter value was used ONLY for translated title. In this new version the UserCountry parameter value is used ALSO for country, categories and description. Description could still be shown in english language if there isn't a translated plot (and remember to set DescriptionSelection to 0 to have a chance to get translated plot). This is how UserCountry parameter affect languages (tell me if you see errors):

argentina, bolivia (plurinational state of), chile, colombia, costa rica, cuba, dominican republic, ecuador, el salvador, equatorial guinea, guatemala, honduras, mexico, nicaragua, panama, paraguay, peru, spain, uruguay, venezuela (bolivarian republic of), puerto rico: Spanish

benin, burkina faso, burundi, central african republic, chad, congo, côte divoire, gabon, guadeloupe, guinea, madagascar, mali, martinique, mayotte, monaco, niger, new caledonia, réunion, rwanda, saint barthélemy, saint martin (french part), saint pierre and miquelon, senegal, switzerland, togo, france, french guiana, french polynesia, french southern territories, luxembourg, wallis and futuna: French

angola, brazil, cabo verde, guinea-bissau, mozambique, portugal, sao tome and principe, timor-leste: Portoguese

austria, germany, liechtenstein: German

italy, san marino, holy see: Italian

If you live in a multi-language country, you can force language changing the country, so if you are from Switzerland and you speak/prefer italian or german you can set Italy or Germany

This is a beta so please test and report here.

MrObama2022, I try with few movies and series.

DescriptionSelection: 0
PopularSearches: 1
UserCountry: Spain

Works OK

Thanks

Thank you so much

Thanks, I'll update it on my server tomorrow (can't do it right now).

Each time I run the script it pops up the following message part way through.



If I manually change the > Script Parameters > UserCountry it makes no difference, and it also keeps defaulting back to, United States of America.

My local country is the, United Kingdom, when I changed it to, Australia it worked without error, maybe an issue parsing the "space" character?

Cheers.

S.

I've tried it and it works very well. It translates the synopsis, category, and country into Spanish. Before, I had to modify the country and category for each movie, but now I don't have to. Thanks.

I don't know if it is also possible to translate the Comments into Spanish?

MrObama2022, there appear to be some issues with the script (5.4 beta 1).

movie: https://www.imdb.com/title/tt31193180/reference/

result 1: only "Tina Anderson" is returned as "Producer".
expected result 1: "Tina Anderson, Pete Chiappetta, Rebecca Cho, Ryan Coogler, Zinzi Coogler, Will Greenfield, Ludwig Göransson, Andrew Lary, Ammar Mohamed, Sev Ohanian, Anthony Tittanegro, Kenneth Yu"

result 2: no "Trivia" is returned for Comments field.

My RapidApiKey is apparently in working order because Trivia is returned for other movies, ie. https://www.imdb.com/title/tt0043417/reference/ and https://www.imdb.com/title/tt0021435/reference/

Additional issues:
https://www.imdb.com/title/tt0044136/reference/ returns one writer (Art Cohn) instead of three (Art Cohn, Guy Endore, Guy Endore; yes, Guy Endore is listed twice on the page)

https://www.imdb.com/title/tt34463310/reference/ returns one composer (Xiao'ou Hu) instead of two (Xiao'ou Hu, Nathan Wang).

Any chance you can have a look? Many thanks.

IMDB is on the move again....

I'm getting this error:



And this is the result, no image and the movie is given the number 0



Thanks!

IMDB 5.5 beta 1

CHANGELOG
* fixed imdbapi url and syntax

imdbapi removed rest.imdbapi.dev domain and now use a different domain with a different syntax. Because these changes, you get an error for AKAS (alternative title) and picture (when ImageKind = 5). This is a quick first change to the code and should fix this.

For number field error (script put it to 0) please uncheck "Number" in modifiable fields script setup. I'll fix this error asap

MrObama2022 wrote: 2025-08-06 15:21:30 IMDB 5.5 beta 1

CHANGELOG
* fixed imdbapi url and syntax

imdbapi removed rest.imdbapi.dev domain and now use a different domain with a different syntax. Because these changes, you get an error for AKAS (alternative title) and picture (when ImageKind = 5). This is a quick first change to the code and should fix this.

For number field error (script put it to 0) please uncheck "Number" in modifiable fields script setup. I'll fix this error asap

You are amazing, you know that, right?

EDIT: TESTED: the error is gone, but the problem with imagekind=5 and imagekind=4 is still there, not image shown.

Thank you so much!!

IMDB 5.5 beta 2

CHANGELOG
* fix images retrieve (imagekind = 4 or 5)
* fix movie number forced to 0

Tested, it's working perfectly again, thank you so much!

Thanks, updated on the server

The new version fails to retrieve the poster of this movie with imagekind=5 and retrieve the wrong image with imagekind=4:

https://www.imdb.com/title/tt0103239

"HTTP/1.1 404 not found"


Thanks!!

IMDB 5.5 beta 3

CHANGELOG
* fix picture when LargePictureHeight is set and image cannot be resized

I have bad news. Resize does not work with that poster and I don't know why. How resize is made: changing this url https://m.media-amazon.com/images/M/MV5BYzAzMTFiNjMtNTA3OS00ZTZhLWJjYzUtNjc3YzVhMDYzNjE3XkEyXkFqcGc@._V1_.jpg in this https://m.media-amazon.com/images/M/MV5BYzAzMTFiNjMtNTA3OS00ZTZhLWJjYzUtNjc3YzVhMDYzNjE3XkEyXkFqcGc@._V1_SY720_AL_.jpg (where 720 is your wanted final height as in LargePictureHeight parameter). With this image this trick does not work and you get a not found response. This is the first time this trick does not work: if you look at this poster https://m.media-amazon.com/images/M/MV5BNjA2OTFlMTUtY2E5Ni00NGMwLWI2OGMtMWIzYzQwYWY2MGVjXkEyXkFqcGc@._V1_.jpg and you modify it https://m.media-amazon.com/images/M/MV5BNjA2OTFlMTUtY2E5Ni00NGMwLWI2OGMtMWIzYzQwYWY2MGVjXkEyXkFqcGc@._V1_SY720_AL_.jpg this old trick works

How I changed the script: now the script try to get the image in the resized format (using _SYXXX_AL_ as usual): if this fails, it uses the original picture url without resizing. This method is used now for every ImageKing option values. So now you could get sometimes images with a different size and LargePictureHeight could be ignored

MrObama2022 wrote: 2025-08-07 11:46:26 IMDB 5.5 beta 3

CHANGELOG
* fix picture when LargePictureHeight is set and image cannot be resized

I have bad news. Resize does not work with that poster and I don't know why. How resize is made: changing this url https://m.media-amazon.com/images/M/MV5BYzAzMTFiNjMtNTA3OS00ZTZhLWJjYzUtNjc3YzVhMDYzNjE3XkEyXkFqcGc@._V1_.jpg in this https://m.media-amazon.com/images/M/MV5BYzAzMTFiNjMtNTA3OS00ZTZhLWJjYzUtNjc3YzVhMDYzNjE3XkEyXkFqcGc@._V1_SY720_AL_.jpg (where 720 is your wanted final height as in LargePictureHeight parameter). With this image this trick does not work and you get a not found response. This is the first time this trick does not work: if you look at this poster https://m.media-amazon.com/images/M/MV5BNjA2OTFlMTUtY2E5Ni00NGMwLWI2OGMtMWIzYzQwYWY2MGVjXkEyXkFqcGc@._V1_.jpg and you modify it https://m.media-amazon.com/images/M/MV5BNjA2OTFlMTUtY2E5Ni00NGMwLWI2OGMtMWIzYzQwYWY2MGVjXkEyXkFqcGc@._V1_SY720_AL_.jpg this old trick works

How I changed the script: now the script try to get the image in the resized format (using _SYXXX_AL_ as usual): if this fails, it uses the original picture url without resizing. This method is used now for every ImageKing option values. So now you could get sometimes images with a different size and LargePictureHeight could be ignored

First of all, thank you so much for you hard work.

With this new version the problem is still there in both imagekind=4 (no error with this option, but it retrieves the wrong poster) and imagekind=5, look:



The poster size is huge, no matter the option selected:



And it retrieves a weird poster I'm unable to find in the original imdb page:



But if you select imagekind=3 the correct original poster is selected along with the right size (the problem with imagekind=3 is, if the movie has a foreign translated poster it will take that based on the user location)

The problem is this. Each of the values set in ImageKind works differently: values 1, 2, and 3 access the IMDB URL, while values 4 and 5 access imdbapi, a site that offers free APIs for IMDB. In the code you can see it here: option 3 accesses PageText, meaning the content of the IMDB page:

jsonMultipleValuesToList(PageText, '"aboveTheFoldData":{', '"mainColumnData":{', '{"url":"', '"', 0, 1);

and as you can see, it takes whatever the page provides. Instead, options 4 and 5 access imdbapi:

jsonMultipleValuesToList(GetPage5(('https://api.imdbapi.dev/titles/tt' + MovieNumber), '', '', '', 'accept=application/json'), '"primaryImage":', '}', '"url":"', '",', 0, 1);

imdbapi is not an official IMDB site, so it may not be perfectly synchronized. With option 3, the page content is tied to your own IP. With options 4 and 5, the poster from the country of origin is always taken, because imdbapi doesn’t distinguish by country: it has all posters but doesn’t specify which country they belong to, so by default it uses the “main” one (which corresponds to the USA). Option 5, compared to 4, tries to resize, but the resize doesn’t work and therefore it returns the original image.

Now, look here:

curl -X "GET" "https://api.imdbapi.dev/titles/tt0103239" -H "accept: application/json"
{"id":"tt0103239", ... "primaryImage":{"url":"https://m.media-amazon.com/images/M/MV5 ... @._V1_.jpg","width":2000,"height":3000}, ...}

As you can see, the image returned by imdbapi for this movie is that “strange” and giant one ( https://m.media-amazon.com/images/M/MV5BYzAzMTFiNjMtNTA3OS00ZTZhLWJjYzUtNjc3YzVhMDYzNjE3XkEyXkFqcGc@._V1_.jpg ), different from the one currently returned by the IMDB site (which was likely changed in recent months). Moreover, for this particular image the resize, as I mentioned before, doesn’t work, so the script leaves the huge image.

There’s nothing you can do about it. What I hope is that this case is an exception and not the rule, and that you don’t find other critical cases like this. If you do, let me know, but honestly I wouldn’t know how to solve them.

---------------------------------------------------------------------------------------------------------

El problema es el siguiente. Cada uno de los valores establecidos en ImageKind funciona de manera diferente: los valores 1, 2 y 3 acceden a la URL de IMDB, mientras que los valores 4 y 5 acceden a imdbapi, un sitio que ofrece API gratuitas para IMDB. En el código lo puedes ver aquí: la opción 3 accede a PageText, es decir, al contenido de la página de IMDB:

jsonMultipleValuesToList(PageText, '"aboveTheFoldData":{', '"mainColumnData":{', '{"url":"', '"', 0, 1);

y como ves toma el contenido que ofrece la página. En cambio, las opciones 4 y 5 acceden a imdbapi:

jsonMultipleValuesToList(GetPage5(('https://api.imdbapi.dev/titles/tt' + MovieNumber), '', '', '', 'accept=application/json'), '"primaryImage":', '}', '"url":"', '",', 0, 1);

imdbapi no es un sitio oficial de IMDB, así que podría no estar perfectamente sincronizado. Con la opción 3 el contenido de la página está asociado a la propia IP. Con las opciones 4 y 5 se toma siempre el póster del país de origen, porque imdbapi no distingue por país: tiene todos los pósters pero no indica a qué país pertenecen, así que por defecto se toma el "principal" (que corresponde al de EE.UU.). La opción 5, respecto a la 4, intenta hacer un resize pero el resize no funciona y por tanto devuelve la imagen original.

Ahora mira aquí:

curl -X "GET" "https://api.imdbapi.dev/titles/tt0103239" -H "accept: application/json"
{"id":"tt0103239" ... "primaryImage":{"url":"https://m.media-amazon.com/images/M/MV5 ... @._V1_.jpg","width":2000,"height":3000}, ...}

Como puedes notar, la imagen que me devuelve imdbapi para esta película es esa "extraña" y gigante ( https://m.media-amazon.com/images/M/MV5BYzAzMTFiNjMtNTA3OS00ZTZhLWJjYzUtNjc3YzVhMDYzNjE3XkEyXkFqcGc@._V1_.jpg ), diferente de la que actualmente devuelve el sitio de IMDB (probablemente la han cambiado en los últimos meses). Además, para esa imagen en particular el resize, como dije antes, no funciona y entonces el script deja la imagen enorme.

No hay forma de intervenir. Lo que espero es que este caso sea una excepción y no la regla, y que no encuentres más casos críticos como este. Si los encuentras, avísame, pero sinceramente no sabría cómo resolverlos.

MrObama2022 wrote: 2025-08-07 23:50:23 The problem is this. Each of the values set in ImageKind works differently: values 1, 2, and 3 access the IMDB URL, while values 4 and 5 access imdbapi, a site that offers free APIs for IMDB. In the code you can see it here: option 3 accesses PageText, meaning the content of the IMDB page:

jsonMultipleValuesToList(PageText, '"aboveTheFoldData":{', '"mainColumnData":{', '{"url":"', '"', 0, 1);

and as you can see, it takes whatever the page provides. Instead, options 4 and 5 access imdbapi:

jsonMultipleValuesToList(GetPage5(('https://api.imdbapi.dev/titles/tt' + MovieNumber), '', '', '', 'accept=application/json'), '"primaryImage":', '}', '"url":"', '",', 0, 1);

imdbapi is not an official IMDB site, so it may not be perfectly synchronized. With option 3, the page content is tied to your own IP. With options 4 and 5, the poster from the country of origin is always taken, because imdbapi doesn’t distinguish by country: it has all posters but doesn’t specify which country they belong to, so by default it uses the “main” one (which corresponds to the USA). Option 5, compared to 4, tries to resize, but the resize doesn’t work and therefore it returns the original image.

Now, look here:

curl -X "GET" "https://api.imdbapi.dev/titles/tt0103239" -H "accept: application/json"
{"id":"tt0103239", ... "primaryImage":{"url":"https://m.media-amazon.com/images/M/MV5 ... @._V1_.jpg","width":2000,"height":3000}, ...}

As you can see, the image returned by imdbapi for this movie is that “strange” and giant one ( https://m.media-amazon.com/images/M/MV5 ... @._V1_.jpg ), different from the one currently returned by the IMDB site (which was likely changed in recent months). Moreover, for this particular image the resize, as I mentioned before, doesn’t work, so the script leaves the huge image.

There’s nothing you can do about it. What I hope is that this case is an exception and not the rule, and that you don’t find other critical cases like this. If you do, let me know, but honestly I wouldn’t know how to solve them.

---------------------------------------------------------------------------------------------------------

El problema es el siguiente. Cada uno de los valores establecidos en ImageKind funciona de manera diferente: los valores 1, 2 y 3 acceden a la URL de IMDB, mientras que los valores 4 y 5 acceden a imdbapi, un sitio que ofrece API gratuitas para IMDB. En el código lo puedes ver aquí: la opción 3 accede a PageText, es decir, al contenido de la página de IMDB:

jsonMultipleValuesToList(PageText, '"aboveTheFoldData":{', '"mainColumnData":{', '{"url":"', '"', 0, 1);

y como ves toma el contenido que ofrece la página. En cambio, las opciones 4 y 5 acceden a imdbapi:

jsonMultipleValuesToList(GetPage5(('https://api.imdbapi.dev/titles/tt' + MovieNumber), '', '', '', 'accept=application/json'), '"primaryImage":', '}', '"url":"', '",', 0, 1);

imdbapi no es un sitio oficial de IMDB, así que podría no estar perfectamente sincronizado. Con la opción 3 el contenido de la página está asociado a la propia IP. Con las opciones 4 y 5 se toma siempre el póster del país de origen, porque imdbapi no distingue por país: tiene todos los pósters pero no indica a qué país pertenecen, así que por defecto se toma el "principal" (que corresponde al de EE.UU.). La opción 5, respecto a la 4, intenta hacer un resize pero el resize no funciona y por tanto devuelve la imagen original.

Ahora mira aquí:

curl -X "GET" "https://api.imdbapi.dev/titles/tt0103239" -H "accept: application/json"
{"id":"tt0103239" ... "primaryImage":{"url":"https://m.media-amazon.com/images/M/MV5 ... @._V1_.jpg","width":2000,"height":3000}, ...}

Como puedes notar, la imagen que me devuelve imdbapi para esta película es esa "extraña" y gigante ( https://m.media-amazon.com/images/M/MV5 ... @._V1_.jpg ), diferente de la que actualmente devuelve el sitio de IMDB (probablemente la han cambiado en los últimos meses). Además, para esa imagen en particular el resize, como dije antes, no funciona y entonces el script deja la imagen enorme.

No hay forma de intervenir. Lo que espero es que este caso sea una excepción y no la regla, y que no encuentres más casos críticos como este. Si los encuentras, avísame, pero sinceramente no sabría cómo resolverlos.

Again thank you so much!

I know it's a different script but the Munkey API version of the script takes the right poster (the default original one), even for the "Wedlock" movie. What is that script doing that: 1- ignores the user ip and gets the default poster 2- is able to get the Wedlock poster without any issue, even with the resize option turned on.

Dorohedoro wrote: 2025-08-08 08:54:27 I know it's a different script but the Munkey API version of the script takes the right poster (the default original one), even for the "Wedlock" movie. What is that script doing that: 1- ignores the user ip and gets the default poster 2- is able to get the Wedlock poster without any issue, even with the resize option turned on.

This is because Munkey API version access to official imdb API so:
- it retrieve a 100% updated movie info (and posters)
- that poster is still official in IMDB so you can also resize it (it fails in my script because that poster is no more official)
- both imdbapi and official imdb api does ignore ip