Auto-tag from web...: HTTP/1.1 400 Bad Request [BUG# 5605]

Get answers about using MediaMonkey 4 for Windows.

Moderator: Gurus

Jeff The Riffer

Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request

Post by Jeff The Riffer »

This isn't MediaMonkey's fault, not really. Amazon's requirement for digitally signing all search requests is the problem. OTOH, Amazon did send out notices over 60 days ago:

"We wanted to remind you that all Product Advertising API developers will be required to authenticate all calls to the Product Advertising API by August 15, 2009. We noticed that requests with your AWS Access Key ID are not being signed and, while you have more than 60 days until the date on which authentication is required, we are, as a courtesy, sending you this email to remind you of the new authentication requirement. Please remember that calls to the Product Advertising API that are not signed will not be processed after August 15, 2009. "

I'm guessing someone wasn't checking the e-mail account their AWS key is signed-up under, :)

So because Amazon didn't decide to require digitally signing advertising requests to start with, like they do for all the REST of their AWS customers, people have to be inconvenienced. Oh well...
Cosmos

Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request

Post by Cosmos »

I'm having the same issue...operating Windows Visa Home Premium 64bit version...just loaded the new Media Monkey Gold and getting same error as you guys...tried turning off my firewall but still comes up with the same erro "Couldn't show results: HTTP/1.1 400 Bad Request"!??? Can Anyone HELP!? I'd like to tage my albums sometime soon here.... :roll:
Kutusov
Posts: 80
Joined: Thu Apr 09, 2009 7:31 pm

Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request

Post by Kutusov »

(... coming back much later after a lot of beers...)

:lol: :o There isn't going to be a patch for this?? We'll have to wait for the next MM build?? Whaaaatttttt??? Now seriously... that can't be right... auto-tag is a crucial aspect of this kind of managers! You know how long it takes to tag an album by hand...

If MM takes too long to release the new build I'll be having so many untagged tracks that I won't know what is what. Isn't there some sort of plug-in for this?
Cosmos

Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request

Post by Cosmos »

MM Needs to release this "On The Fly" as in, RIGHT NOW, if this is the case! I myself hope this is released in AT LEAST a day or two, correct? Is this asking for too much!!?? Come On Media Moneky!? You have a GREAT PRODUCT, so don't start screwing it up now!!!!! If you FIXED IT already...please releast it!!!! WHAT ARE YOU WAITING FOR!!?? A bunch of Mad Monkeys!!!!?
Lowlander
Posts: 58960
Joined: Sat Sep 06, 2003 5:53 pm

Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request

Post by Lowlander »

The problem with a new release is that all other feature changes need to be tested. So although this issue has been addressed in a new build other changes need to be tested before a new release can be made. We wouldn't want a fix to this issue result in other bugs.
Kutusov
Posts: 80
Joined: Thu Apr 09, 2009 7:31 pm

Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request

Post by Kutusov »

OOOCH OOOOOCH OOOOCH!!!!!! :evil: :evil: :evil: :evil:

(That was me trying to sound like a mad monkey... :oops: )
thecongressman
Posts: 28
Joined: Sun Mar 30, 2008 3:38 pm

Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request

Post by thecongressman »

Lowlander wrote:The problem with a new release is that all other feature changes need to be tested. So although this issue has been addressed in a new build other changes need to be tested before a new release can be made. We wouldn't want a fix to this issue result in other bugs.
So, easy fix. Release the next build with just this fix--and after the testing is done with the other changes release another build. This is obviously something that many, many people would have liked fixed two days ago. Especially if the patch has already been taken care of. :evil:
Over 280,000 songs and Mediamonkey is still going strong...
Kutusov
Posts: 80
Joined: Thu Apr 09, 2009 7:31 pm

Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request

Post by Kutusov »

Hear hear!
BluBear

Re: Auto-tag

Post by BluBear »

An interim release of code addressing ONLY the auto tag feature is the only sensible course of action IMHO. I would venture to guess that many users could care less about some arcane new feature that has been added to the last release. The auto tag feature is what made me use (and purchase) MM in the first place, and is at the heart of MM's library management functionality. I have lost the ability to rip CD's with MM already (issue raised in another thread), so losing auto tag for an extended period leaves me with an overblown MP3 player. For heavens's sake, don't make me switch to WMP11!
Kutusov
Posts: 80
Joined: Thu Apr 09, 2009 7:31 pm

Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request

Post by Kutusov »

... or ITunes! I would be pretty screwed if I had to migrate to ITunes and correct my libabry all over again. I've also bought MM (lifetime license) so if anybody from MM reads this posts I am another person who finds auto-tag to be crucial to this manager. I don't think it's great, just having Amazon doesn't cut it, but not having anything is enough for me to stop using MM.

I guess a lot of people feels this way, including developers. That's why I honestly believe this issue is going to be addressed pretty soon.
chrisss

Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request

Post by chrisss »

new google search.. what would a good google search be? how about "mediamonkey alternative"?
Kutusov
Posts: 80
Joined: Thu Apr 09, 2009 7:31 pm

Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request

Post by Kutusov »

lol, yhea!... But MM is a great software, I can't believe that they will just let this be until a new build 6 months or so from now...

And as far as I understand, everything on this thread are just rumours and guesses, right?... Personally I'll wait a week or two. Then will see...
Gabe

Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request

Post by Gabe »

The problem is clear and solutions are given, just for courtesy reasons a post from one of the MM crew here would be nice :P
Anon

Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request

Post by Anon »

I'm surprised no MM rep has given us the ETA on a new release. MM is useless software without the auto-tag feature.
MonkeyMagic
Posts: 3
Joined: Tue Aug 18, 2009 12:49 pm

Re: Auto-tag - Couldn't show results: HTTP/1.1 400 Bad Request

Post by MonkeyMagic »

And i'd like a nice blonde to walk through my front door right now, but it aint going to happen. Will you all just chill out!!!
Locked