sinbaddylad wrote: ↑Thu Jun 14, 2018 7:02 pmI've tried v5, same Bad Request. "HTTP/1.1 400 Bad Request"

If you are searching for TV Series then Video Files needs to be set to Type TV in order to do specific search for the type. But that is in MM5 as it have more sophisticated search

If you read the whole thread, it's because of changes Amazon made. MediaMonkey is working right.
Amazon.co.jp is the only one which has retained the API.

will only search in amazon japan and not search any of the other amazons.

I've tried v5, same Bad Request. "HTTP/1.1 400 Bad Request"

MediaMonkey 5 (available as Alpha) can do Movie (and TV and Music) tagging natively.

Hey guys, how are you all tagging your movie files? Discogs only works for music files. Since the Amazon issue kicked in, MM is useless for tagging my movies. Any help?

I use the discogs addon and it works ok. Finds 9.5/10 i want to tag.

1) There are no plans to "fix" Amazon tagging, it has been disabled by Amazon.

2) It's far more complex to parse data from a webpage then using an API.

3) You can't just get data from a website without permission to do so.

4) So for now, the Japan variant still works, and there alternative options like the Discogs Tagger: http://www.mediamonkey.com/addons/brows ... ta-lookup/

5) MediaMonkey 5 (in testing) will has other sources build in.

I'm curious...
The resultant pages for the searches for Amazon based on (for example) album or artist are the same. Why can't those be parsed for the information for autotag?

I don't have details on the backend results that the APIs were returning before - was there a specific format that they were being returned in that could be "built", perhaps, from the item page(s) instead of relying on the API?

This could then be called through the OS browser, and be just another web page being pulled up rather than a call to the API.

...Or am I missing something because I lack the information about the API calls or resultant data?

Just a thought ...

same problem here..I guess we wait until MM fix it. I just upgraded to latest version and then error... not sure how long this has been a problem as Ive not used mm in a while until today.
HTTP/1.1 400 Bad Request

I have the same problem!!

Same problem; Went to download folder, reinstalled 4.1.18.1853 Problem fixed.
Wait for update, or search for beta release.

Amazon Japan is still working for me too

Amazon Japan is still working for unknown reason

PROBLEM:
Unable to auto-tag
Get error "Couldn't show results - HTTP/1.1.400 Bad Request

VERSION:
MM v4.1.19.1859
OS Windows 10 (fully patched)

WHATS BEEN DONE:
Uninstalled all scripts
Turn off FW
Placed PC outside of FW
AV disabled

Still unable to auto-tag
Only thing I haven't done is uninstall and reinstall

Anyone have any other ideas?
Do I need to change freedb settings? Is Amazon changing things again?