@Terra1226 said:

@Scooby1965 said:

@Terra1226 said:

@Scooby1965 said:

@Terra1226 said:

@Scooby1965 said:

@DiGiTALY-LiVE said:

@ercolepatata said:

I contacted wd and the question is on the table of wd senior team.

73 days or 2 and a half months later is what only happened - it moved directly from the table of the WD senior team in San Jose to their Waste container where they burried the device.

Keep the pressure on WD. I'm trying to. If we can get the copy of the xml file currently installed on the devices, it is easy to modify it with an active API key to fix the problem. I'm also trying to figure out how to access the files in the WD too as then we don't even need WD for anything. If anyone can help get that file it can fix it for everyone.

Someone must have that file because it used to be on the WD website for download for people who wanted to add a new meta-source. It was under "meta-source sample". I found the article explaining how to add a new meta-source, but the link and the WDTV website is dead.

If you have the link, the internet archive may still have a copy. If you can post the link I will have a look for it and let you know.

I will look for it. Meanwhile, I have the link for what is supposed to be this sample file http://www.mediafire.com/?5d9d74hqs6z85sa 280. Found it on a forum, I downloaded the xml file and changed the API Key to a developer key that I got from TMDB, but it doesn't work. Either the format is incorrect, or a developer key doesn't work for streaming devices? Maybe a developer key only works with apps?

I checked the link and it was using the old version that used the API 2.1 framework which is the file that I was able to access from the last firmware update. I can't figure out why the last firmware update includes the 2.1 framework instead of the 3 framework which is what appears to be used now. From what I can find in the forums, TMDB upgraded their structure back in September 2013. Someone in this thread posted their log from their router which included a query from the file showing that it was using API 3 so I'm pretty sure that is what the problem is. Here's the copy of the code which works if you manually enter it into your browser and insert your API key where the * is:

http://api.themoviedb.org/3/search/movie?api_key=*&query=xwv&language=it&year=

This is the WD support website: https://support-eu.wd.com/app/products/product-detailweb/p/186. It has a bunch of firmware upgrades available for download. Maybe one of these files has the API 3?

And this is the TMDB API 3 sample files, but I don't know which language the WD player uses: https://developer.themoviedb.org/reference/intro/getting-started

@Terra1226 said:

@Scooby1965 said:

@Terra1226 said:

@Scooby1965 said:

@Terra1226 said:

@Scooby1965 said:

@DiGiTALY-LiVE said:

@ercolepatata said:

I contacted wd and the question is on the table of wd senior team.

73 days or 2 and a half months later is what only happened - it moved directly from the table of the WD senior team in San Jose to their Waste container where they burried the device.

Keep the pressure on WD. I'm trying to. If we can get the copy of the xml file currently installed on the devices, it is easy to modify it with an active API key to fix the problem. I'm also trying to figure out how to access the files in the WD too as then we don't even need WD for anything. If anyone can help get that file it can fix it for everyone.

Someone must have that file because it used to be on the WD website for download for people who wanted to add a new meta-source. It was under "meta-source sample". I found the article explaining how to add a new meta-source, but the link and the WDTV website is dead.

If you have the link, the internet archive may still have a copy. If you can post the link I will have a look for it and let you know.

I will look for it. Meanwhile, I have the link for what is supposed to be this sample file http://www.mediafire.com/?5d9d74hqs6z85sa 280. Found it on a forum, I downloaded the xml file and changed the API Key to a developer key that I got from TMDB, but it doesn't work. Either the format is incorrect, or a developer key doesn't work for streaming devices? Maybe a developer key only works with apps?

I checked the link and it was using the old version that used the API 2.1 framework which is the file that I was able to access from the last firmware update. I can't figure out why the last firmware update includes the 2.1 framework instead of the 3 framework which is what appears to be used now. From what I can find in the forums, TMDB upgraded their structure back in September 2013. Someone in this thread posted their log from their router which included a query from the file showing that it was using API 3 so I'm pretty sure that is what the problem is. Here's the copy of the code which works if you manually enter it into your browser and insert your API key where the * is:

http://api.themoviedb.org/3/search/movie?api_key=*&query=xwv&language=it&year=

This is the WD support website: https://support-eu.wd.com/app/products/product-detailweb/p/186. It has a bunch of firmware upgrades available for download. Maybe one of these files has the API 3?

Unfortunately, I've checked all the firmware files and they all reference the old API 2.1 syntax. I'm not sure where the new file came from.

@Terra1226 said:

@Scooby1965 said:

@Terra1226 said:

@Scooby1965 said:

@Terra1226 said:

@Scooby1965 said:

@DiGiTALY-LiVE said:

@ercolepatata said:

I contacted wd and the question is on the table of wd senior team.

73 days or 2 and a half months later is what only happened - it moved directly from the table of the WD senior team in San Jose to their Waste container where they burried the device.

Keep the pressure on WD. I'm trying to. If we can get the copy of the xml file currently installed on the devices, it is easy to modify it with an active API key to fix the problem. I'm also trying to figure out how to access the files in the WD too as then we don't even need WD for anything. If anyone can help get that file it can fix it for everyone.

Someone must have that file because it used to be on the WD website for download for people who wanted to add a new meta-source. It was under "meta-source sample". I found the article explaining how to add a new meta-source, but the link and the WDTV website is dead.

If you have the link, the internet archive may still have a copy. If you can post the link I will have a look for it and let you know.

I will look for it. Meanwhile, I have the link for what is supposed to be this sample file http://www.mediafire.com/?5d9d74hqs6z85sa 280. Found it on a forum, I downloaded the xml file and changed the API Key to a developer key that I got from TMDB, but it doesn't work. Either the format is incorrect, or a developer key doesn't work for streaming devices? Maybe a developer key only works with apps?

I checked the link and it was using the old version that used the API 2.1 framework which is the file that I was able to access from the last firmware update. I can't figure out why the last firmware update includes the 2.1 framework instead of the 3 framework which is what appears to be used now. From what I can find in the forums, TMDB upgraded their structure back in September 2013. Someone in this thread posted their log from their router which included a query from the file showing that it was using API 3 so I'm pretty sure that is what the problem is. Here's the copy of the code which works if you manually enter it into your browser and insert your API key where the * is:

http://api.themoviedb.org/3/search/movie?api_key=*&query=xwv&language=it&year=

This is the WD support website: https://support-eu.wd.com/app/products/product-detailweb/p/186. It has a bunch of firmware upgrades available for download. Maybe one of these files has the API 3?

Unfortunately, I've checked all the firmware files and they all reference the old API 2.1 syntax. I'm not sure where the new file came from.

@Scooby1965 said:

@ercolepatata said:

Hello.

using a managed switch, with port mirroring function, and wireshark as sniffer, i found the request and response

this is the request:

http://api.themoviedb.org/3/search/movie?api_key=*&query=xwv&language=it&year=

the key "api_key" contains a value that is the same for every film i searched, it is not like a kind of url's sign, so i don't know if i can publish the value of api_key.

In this case, i tried a film called "xwv".

the response is long, the most important parts are this ones:

[Path with value: /status_message:Invalid API key: You must be granted a valid key.]
[Member with value: status_message:Invalid API key: You must be granted a valid key

    Source Address: 99.86.159.68
Hypertext Transfer Protocol
    HTTP/1.1 401 Unauthorized\r\n
        [Expert Info (Chat/Sequence): HTTP/1.1 401 Unauthorized\r\n]
            [HTTP/1.1 401 Unauthorized\r\n]
            [Severity level: Chat]
            [Group: Sequence]
        Response Version: HTTP/1.1
        Status Code: 401
        [Status Code Description: Unauthorized]
        Response Phrase: Unauthorized

putting the request in a browser, i had the same response in json

{"status_code":7,"status_message":"Invalid API key: You must be granted a valid key.","success":false}

Thank you for support.

Can you tell me what firmware version you are on as I can see in the code above that it is referencing the API 3 coding but when I pull up the xml file from the firmware updates it is still using the API 2.1 coding so I'm not sure how to update the old coding. If I can figure out which firmware version your file is from I should be able to get it working again.

Good morning

i am using firmware 1.03.07

model WDBPUF0000NBK

@ercolepatata said:

@Scooby1965 said:

@ercolepatata said:

Hello.

using a managed switch, with port mirroring function, and wireshark as sniffer, i found the request and response

this is the request:

http://api.themoviedb.org/3/search/movie?api_key=*&query=xwv&language=it&year=

the key "api_key" contains a value that is the same for every film i searched, it is not like a kind of url's sign, so i don't know if i can publish the value of api_key.

In this case, i tried a film called "xwv".

the response is long, the most important parts are this ones:

[Path with value: /status_message:Invalid API key: You must be granted a valid key.]
[Member with value: status_message:Invalid API key: You must be granted a valid key

    Source Address: 99.86.159.68
Hypertext Transfer Protocol
    HTTP/1.1 401 Unauthorized\r\n
        [Expert Info (Chat/Sequence): HTTP/1.1 401 Unauthorized\r\n]
            [HTTP/1.1 401 Unauthorized\r\n]
            [Severity level: Chat]
            [Group: Sequence]
        Response Version: HTTP/1.1
        Status Code: 401
        [Status Code Description: Unauthorized]
        Response Phrase: Unauthorized

putting the request in a browser, i had the same response in json

{"status_code":7,"status_message":"Invalid API key: You must be granted a valid key.","success":false}

Thank you for support.

Can you tell me what firmware version you are on as I can see in the code above that it is referencing the API 3 coding but when I pull up the xml file from the firmware updates it is still using the API 2.1 coding so I'm not sure how to update the old coding. If I can figure out which firmware version your file is from I should be able to get it working again.

Good morning

i am using firmware 1.03.07

model WDBPUF0000NBK

by any chance do you have access to a copy of the tmdb.xml file? On the alternative, I will try and find your firmware file unless you have a copy of it.

@Scooby1965 said:

@ercolepatata said:

@Scooby1965 said:

@ercolepatata said:

Hello.

using a managed switch, with port mirroring function, and wireshark as sniffer, i found the request and response

this is the request:

http://api.themoviedb.org/3/search/movie?api_key=*&query=xwv&language=it&year=

the key "api_key" contains a value that is the same for every film i searched, it is not like a kind of url's sign, so i don't know if i can publish the value of api_key.

In this case, i tried a film called "xwv".

the response is long, the most important parts are this ones:

[Path with value: /status_message:Invalid API key: You must be granted a valid key.]
[Member with value: status_message:Invalid API key: You must be granted a valid key

    Source Address: 99.86.159.68
Hypertext Transfer Protocol
    HTTP/1.1 401 Unauthorized\r\n
        [Expert Info (Chat/Sequence): HTTP/1.1 401 Unauthorized\r\n]
            [HTTP/1.1 401 Unauthorized\r\n]
            [Severity level: Chat]
            [Group: Sequence]
        Response Version: HTTP/1.1
        Status Code: 401
        [Status Code Description: Unauthorized]
        Response Phrase: Unauthorized

putting the request in a browser, i had the same response in json

{"status_code":7,"status_message":"Invalid API key: You must be granted a valid key.","success":false}

Thank you for support.

Can you tell me what firmware version you are on as I can see in the code above that it is referencing the API 3 coding but when I pull up the xml file from the firmware updates it is still using the API 2.1 coding so I'm not sure how to update the old coding. If I can figure out which firmware version your file is from I should be able to get it working again.

Good morning

i am using firmware 1.03.07

model WDBPUF0000NBK

by any chance do you have access to a copy of the tmdb.xml file? On the alternative, I will try and find your firmware file unless you have a copy of it.

My firmware could be downloaded here

http://download.wdc.com/wdtv/wdtvmediaplayer_1.03.07.zip

Now wdtv works, without posters and stories, but it works.

I don't want to risk burning it by loading modified firmware. I'd rather keep it that way.

If the readers of this discussion think that Western Digital should do something, let them know by opening a ticket to their support.

Sincerly.

Epatata

@ercolepatata said:

@Scooby1965 said:

@ercolepatata said:

@Scooby1965 said:

@ercolepatata said:

Hello.

using a managed switch, with port mirroring function, and wireshark as sniffer, i found the request and response

this is the request:

http://api.themoviedb.org/3/search/movie?api_key=*&query=xwv&language=it&year=

the key "api_key" contains a value that is the same for every film i searched, it is not like a kind of url's sign, so i don't know if i can publish the value of api_key.

In this case, i tried a film called "xwv".

the response is long, the most important parts are this ones:

[Path with value: /status_message:Invalid API key: You must be granted a valid key.]
[Member with value: status_message:Invalid API key: You must be granted a valid key

    Source Address: 99.86.159.68
Hypertext Transfer Protocol
    HTTP/1.1 401 Unauthorized\r\n
        [Expert Info (Chat/Sequence): HTTP/1.1 401 Unauthorized\r\n]
            [HTTP/1.1 401 Unauthorized\r\n]
            [Severity level: Chat]
            [Group: Sequence]
        Response Version: HTTP/1.1
        Status Code: 401
        [Status Code Description: Unauthorized]
        Response Phrase: Unauthorized

putting the request in a browser, i had the same response in json

{"status_code":7,"status_message":"Invalid API key: You must be granted a valid key.","success":false}

Thank you for support.

Can you tell me what firmware version you are on as I can see in the code above that it is referencing the API 3 coding but when I pull up the xml file from the firmware updates it is still using the API 2.1 coding so I'm not sure how to update the old coding. If I can figure out which firmware version your file is from I should be able to get it working again.

Good morning

i am using firmware 1.03.07

model WDBPUF0000NBK

by any chance do you have access to a copy of the tmdb.xml file? On the alternative, I will try and find your firmware file unless you have a copy of it.

My firmware could be downloaded here

http://download.wdc.com/wdtv/wdtvmediaplayer_1.03.07.zip

Now wdtv works, without posters and stories, but it works.

I don't want to risk burning it by loading modified firmware. I'd rather keep it that way.

If the readers of this discussion think that Western Digital should do something, let them know by opening a ticket to their support.

Sincerly.

Epatata

Hi, I managed to find the firmware but I keep finding copies that reference API 2.1 and not 3.

What I'm trying to do is find the xml file that you could modify and then load from the metasource manager on the machine. Its not modifying the firmware so there is no risk to doing anything to the unit.

I've spoken and written to WD multiple times and continue to do so. I believe it is from the tmdb.xml file that should have sent the query that you posted earlier:

http://api.themoviedb.org/3/search/movie?api_key=*&query=xwv&language=it&year=

but as you can see it is referencing api.themoviedb.org/3/ whereas the tmdb.xml file I am finding is posting queries such as the following which references api.themoviedb.org/2.1/ so I'm lost.

http://api.themoviedb.org/2.1/Movie.search/$INFO[language]/xml/c014e6cf75cea3567bc035b5c9d2c5c6/\1" dest="3"

If we can get a copy of the xml code presently residing on the WD then its easy to change WD's API key for a new one you can get from TMDB (I already have one) and then upload that file using the metasource manager page in the menu. If it's easier to communicate, you can email me at 4921horstman at gmail dot com

Nothing new on the change metadata source front?

Does anyone know of any way to make the WD use locally stored backdrop images? If I have understood this correctly the WD uses the urls in the xml file to download the images if they don't exist in the backdrop folder. Then it stores the images in the backdrop folder and from then on it uses the locally stored images and don't need to download them everytime. But where is the connection between an url in the xml and the corresponding image file? How does the WD know which of the urls have been downloaded? Can this info be found somewhere in the wdtv.cas2 file that seems to be some kind of sql db. Is it maybe possible to trick the WD into thinking an url has had it's image downloaded without it having to try and connect to tmdb and get all messed up by the missing api key? I'm already generating the xml files and getting the metathumb files with a python script, and is at a standstill when it comes to the pesky backdrops...

You can download the backdrops from TMDB and save them as jpg, then drop them in the .background folder.

Any news guys? Anyone figured out how to change the API key?

I have thought about this, would replacing the URL in the xml file with a network file path work? Just like what computers use to access files on a local area network, then add a file path where the backdrops are stored? (I'm no IT expert)

I have been manually creating XMLs for new movies and the URLs still work so backdrop images are displayed, if you find an older XML that was created from the API key you just have to copy the format of the URL as it seems to define image sizes.

To be honest, I don't think I am bothering with backdrops going forward but I am doing it manually so if you find a way to automate the process that would be a lot more appealing!

If you look at the .backdrop folder, the images are saved in that folder, the player doesn't actually retrieve them from the URL.

Interesting, where is the .backdrop folder?

Each movie has a .xml, .thumbnail and .backdrop folder that the player creates when downloading Metadata. You can create that folder manually also.

@Terra1226 said:

You can download the backdrops from TMDB and save them as jpg, then drop them in the .background folder.

Any news guys? Anyone figured out how to change the API key?

That's what I've been trying to achive, and I have tried many different ways without success. If I download an image from somewhere on the internet and put it in the folder The file structure looks like this on my system:

...\pathtomovie\moviename.mkv
...\pathtomovie\moviename.xml
...\pathtomovie\moviename.metathumb
...\pathtomovie\.moviename.backdrop\backdrop1.jpg
...\pathtomovie\.moviename.backdrop\backdrop2.jpg

This is the xml file Last.Night.in.Soho.2021.1080p.BluRay.H264.AAC-RARBG.xml that was generated by my WDTV a few years ago (I edited out a few of the urls just for brevity):

<?xml version="1.0" encoding="UTF-8"?><details>
<genre>Thriller</genre>
<id>576845</id>
<imdb_id>tt9639470</imdb_id>
<overview>A young girl, passionate about fashion design, is mysteriously able to enter the 1960s where she encounters her idol, a dazzling wannabe singer. But 1960s London is not what it seems, and time seems to be falling apart with shady consequences.</overview>
<year>2021-10-21</year>
<runtime>117</runtime>
<title>Last Night in Soho</title>
<cast>Thomasin McKenzie / Anya Taylor-Joy / Matt Smith / Rita Tushingham / Michael Ajao</cast>
<director>Olivia Fitzroy</director>
<trailer>http://www.youtube.com/watch?v=tB9WUIv9KH8</trailer>
<backdrop>http://image.tmdb.org/t/p//w1280/7OcRErUXXdAVAHg6y5cjn56ivtu.jpg</backdrop>
<backdrop>http://image.tmdb.org/t/p//w1280/nZP1rGsOh3G2HbYfRqO58zg0V4Y.jpg</backdrop>
<backdrop>http://image.tmdb.org/t/p//w1280/wgwJj8PMhfZpnx8iYC8WMJYDD2G.jpg</backdrop>
</details>

This is what's in the corresponding folder .Last.Night.in.Soho.2021.1080p.BluRay.H264.AAC-RARBG.backdrop\

fanart_original00.jpg
fanart_original01.jpg
fanart_original02.jpg

But my WDTV doesn't seem to find these images anymore for whatever reason. Removing all the tags from the xml doesn't seem to help. Replacing them with .Last.Night.in.Soho.2021.1080p.BluRay.H264.AAC-RARBG.backdrop\fanart_original00.jpg for a relative filepath also doesn't seem to achieve anything.

I have a python script that scrapes imdb for metadata and also uses the tmdb (with an api key) to get images. I can get it to generate working xml files and metathumb files for my movies, but I have no clue how to make the WDTV find the backdrop images and show them to me. Whenever I put a tag in the xml file the WDTV will notice that and add the menu entry "view backrop images" for that movie. It will however not display the images. This menu entry isn't there if there are no tags in the xml, so I know it reads the new xml file...

If you have actually done this and got it to work, please show my what your xml files look like and what I might do to make it work.

@fezza123 said:

I have thought about this, would replacing the URL in the xml file with a network file path work? Just like what computers use to access files on a local area network, then add a file path where the backdrops are stored? (I'm no IT expert)

I have been manually creating XMLs for new movies and the URLs still work so backdrop images are displayed, if you find an older XML that was created from the API key you just have to copy the format of the URL as it seems to define image sizes.

To be honest, I don't think I am bothering with backdrops going forward but I am doing it manually so if you find a way to automate the process that would be a lot more appealing!

Wait. Are you able to create xml-files with backdrop urls (to tmdb) in them that actually work? The WDTV is able to download and display the images? Could you please share what those xml files look like? My WDTV doesn't show any backdrop images anymore, no matter what I do. The backdrops for tv series seems to work though, since it's another online metadata db.

Regarding file paths to the backdrops. I think the WDTV is supposed to be able to handle a path relative to where the xml is located in the backdrop tags. I haven't had any success though. The whole thing seem cursed.