Open GoogleCodeExporter opened 9 years ago
This isn't a problem with the clamz, it's an issue with Amazon, because they
stopped supporting their own Linux downloader altogether. I've tried changing
the Useragent, but it hasn't helped - they seem to be using Javascript or some
other means to profile the system as a Linux host.
Original comment by rollstwe...@gmail.com
on 13 Aug 2012 at 1:18
So now we're screwed? Downloading songs one at a time from their cloud service
isn't ideal, especially once that fills up.
Original comment by garputhe...@gmail.com
on 10 Sep 2012 at 3:43
Darn, so can you download the amz file from windows? Maybe it's time to set-up
a virtual machine if so (and can watch Netflix too then).
Original comment by guikubivan
on 13 Sep 2012 at 6:34
Sadly, I dumped my windows partition awhile ago. Guess this makes me
investigate other sources for mp3s...lot of bands have stuff up on
bandcamp, which means they get more of the cut. But, damn, clamz was
awesome. :(
I bitched to Amazon. They gave me some BS about how they're protecting me
from my computer and crashes.
Jen
Original comment by garputhe...@gmail.com
on 13 Sep 2012 at 6:37
The Cloud Player still works if you do the following.
1. Set your User-Agent to something that Amazon thinks is Windows (I tried
"Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1)")
2. Ensure that your 'dmusic_download_manager_enabled' cookie is set correctly
(click the appropriate link on the clamz homepage)
3. *Log out of the Cloud Player and back in*
4. Select a list of files to download
5. You might still at this point be prompted to install the Amazon MP3
Downloader; if so, download the installer, and then click the link that says
"click here to try again after installing the MP3 downloader" or something like
that.
6. It will prompt you to "authorize your device" (!!) before letting you
download your files - apparently you can only do this for 10 "devices" at a
time? Actually, looking at my account it appears I did this once before,
though I don't remember doing so.
7. Finally it will give you an amz file that you can download as always.
Note also that the old non-Cloud-Player system is still working, although they
are making it harder to find: after purchasing a song/album, below the big
yellow "Play your music in Cloud Player" button, it will say "If you have the
Amazon MP3 Downloader, you can download your music now." (Again, this requires
your cookie be set correctly beforehand - click the link on the clamz homepage
- and Javascript must be enabled.)
But the moral of the story, of course, is that you should never trust Amazon
(or any other "cloud" service) to be your only backup.
Original comment by Benjamin...@gmail.com
on 14 Sep 2012 at 2:23
I just bought http://www.amazon.de/gp/product/B006C1OJLW/ref=dm_ty_trk and I
could play it in the cloud player or download it, I clicked on download and got
directly the amz file.
Maybe this is only an issue with the us-store?
My useragent string is "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.1
(KHTML, like Gecko) Chrome/21.0.1180.89 Safari/537.1" (it is google chrome)
Original comment by tim.daniel.schumacher@gmail.com
on 18 Sep 2012 at 9:38
Confirming that it still works on amazon.de — I just downloaded an album
without any issue.
Original comment by devuran...@gmx.net
on 24 Sep 2012 at 10:38
Benjamin, thanks for the walk-through, but I can't get past their Linux OS
detection. Looks like they've torpedoed me as a user. Must be nice to have so
many customers you can afford to drive them away.
Original comment by DaGood...@gmail.com
on 28 Sep 2012 at 3:14
The cookie setting link didn't work for me, but the " Comment by
kael.shi...@gmail.com, Aug 9, 2012" at
http://code.google.com/p/pymazon/wiki/HowToAmzDownload did work:
"
1. When I make One-Click purchases, I get the option at that point to download
the .amz file, which I can do and open in Pymazon or Clamz and all is well.
2. If I DON'T download at that point, my only option is the Cloud Player. 3. To
download in the Cloud Player, I changed my user-agent via User Agent Switcher
(FF extension) to IE8 and tried a bulk (.amz) download. It still told me I had
to download the Amazon MP3 Downloader, so I clicked on the download button,
then simply cancelled the download. After that, I saw a screen that said, "when
you've installed the MP3 Downloader, click on the 'Download Your Music'
button", but the button was grayed out. BELOW THE BUTTON, there was a link that
said, "'Download Your Music' button not working? click here." I clicked and it
apparently filled in the right cookies for the download to go through and I did
a full download!
"
Original comment by cdamian
on 11 Oct 2012 at 10:46
I just bought an album on amazon.de (a One-Click purchase as well) and I was
given the option to download the songs which promptly started the download of
the .amz file.
It seems to be kind of hit-and-miss but for me it worked hassle-free. Maybe
there are regional differences?
Original comment by s.je...@gmail.com
on 10 Nov 2012 at 3:06
I just tried downloading an album from Cloud Player that I had purchased a
couple days earlier. After following the user agent tricks, I managed to
download the .amz file. However, clamz then fails to download the mp3 files
with an error of "ERROR: Error downloading file: The requested URL returned
error: 500".
It seems that Amazon is now enforcing an "Amazon MP3 Downloader" user agent for
downloads to work. This pymazon bug has more details:
http://code.google.com/p/pymazon/issues/detail?id=59. The issue only seems to
affect amz files from Cloud Player. Changing pymazon to set a User-Agent header
of "Amazon MP3 Downloader (Pymazon 1.0.17 en_US)" (as in
http://code.google.com/r/jsphslgr-pymazon/source/detail?r=818aa6ca8405a92379122e
67c5b38d23375e1ea1) fixed the issue for me. clamz should probably do something
similar.
Original comment by happily....@gmail.com
on 26 Nov 2012 at 10:34
[deleted comment]
I could confirm what happily....@gmail.com describe is correct.
I have an amz with 5 different mp3
clamz could only download 3 of the 5.
With the other 2 giving me this error
"ERROR: Error downloading file: The requested URL returned error: 500"
Similar error is returned if using wget to download
wget {url copy from amz file} -O {mp3 file name}
However, I can download the file successfully if using this user agent 'Amazon
MP3 Downloader (Pymazon 1.0.17 en_US)'.
wget --user-agent='Amazon MP3 Downloader (Pymazon 1.0.17 en_US)' {url copy from amz file} -O {mp3 file name}
Original comment by sun...@gmail.com
on 11 Dec 2012 at 8:51
I get error 500 if I try resuming downloads (with clamz's -r option), but clamz
would download files from scratch just fine, which is really odd.
Sadly Google Play Music is not exactly much better when it comes to
downloading. I use it as a write-only cloud storage for my music, but last I
checked they only let you download songs twice -- even songs you upload
yourself!
Original comment by Michael....@gmail.com
on 13 Dec 2012 at 5:02
It didn't work for me with the UA changed to IE8, so I changed it to IE6 and
got a message stating that my browser istn't fully supported. But the Cloud
Player loaded and gave me an amz that worked for a bulk download.
Original comment by steffenb...@gmail.com
on 30 Jan 2013 at 7:42
I wrote a Greasmonkey Script which will work around Amazons Cloud Player
restrictions:
http://userscripts.org/scripts/show/426973
Original comment by sebastia...@gmail.com
on 30 Mar 2014 at 11:37
userscripts.org appears to be down. Perhaps you can put it up at github or
bitbucket or similar?
Original comment by pbren...@gmail.com
on 26 May 2014 at 11:48
Mirror available here:
http://floe.butterbrot.org/external/unfuck_amazon_cloud_player.js
Original comment by florian....@gmail.com
on 7 Jun 2014 at 12:42
My userscirpt is now available here:
http://sebastian.gellweiler.net/amz_unchain/.
I need to find the time to set up updating since userscripts.org seems to be
down forever. The version Florian posted is not working anymore because amazon
changed the design of the cloud player. For now you can get a working version
at the link above.
Original comment by sebastia...@gmail.com
on 19 Jun 2014 at 4:55
Original issue reported on code.google.com by
possu...@gmail.com
on 9 Aug 2012 at 5:50