Wow--you know things are bad when even the Moonie Times is turning up government corruption.

DOES NOT COMPUTE!
DOES NOT COMPUTE!

Neat in theory and looks really cool, but I'm thinking about the amount of dust, fuzz, and other random grime that collects in the corners of the steps in my house...

Susan Oliver,

The files were "-rwx------", so only my user account had read permissions on them. Mpd and mt-daapd run under different accounts, so couldn't read the files.

A simple "chmod o+r" on all the files added the necessary permissions, at which point the mpd and mt-daapd scans picked them up.

Would you believe it was file permissions?

I hang my head in shame.

@AMAZONMP3:

Agreed. Thanks for going the extra mile. I'll continue investigating my setup.

As the OP, let me add my thanks to Amazon as well, and repeat that, aside from this admittedly minor issue, I'm glad to see their extensive support for non-DRM music. My apologies if the initial "It's proprietary" response sent me barking up the wrong tree.

Here, roughly, is what I've seen thus far:

1. Purchase/download mp3's.
2. See that they show up fine in Amarok, Rhythmbox, etc.
3. Move files to mp3 directory on my media server.
4. Run mpd and mt-daapd scans, which have worked w/out fail (and with exactly the same config) for hundreds of non-Amazon mp3's.
5. Both scans fail to recognize Amazon mp3's.
6. Check Amazon mp3's with EasyTag ID3 editor, see that tags look normal.
7. Check Amazon mp3's with hex editor, confirm that tags are ID3v2.3.0.
8. Move files to a different machine, install current versions of both mpd and mt-daapd. Scans still fails to pick up Amazon mp3's.
9. Manually retag all files, confirming ID3 version and charset settings in ID3 tag editor, which, again, have worked fine for hundreds of other mp3's.
10. Rescan files, still nothing.
11. Try various combinations of ID3 version, charsets, etc., same thing.

I'm baffled.

@dculberson:

So far, I've tried ID3v1 only, ID3v2 only, both v1 and v2, v2.3, v2.4, etc.

Frankly, I'm *sure* this is some issue with the ID3 versioning or perhaps the character set being used, given that the files play fine, and that every local player reads them fine (and yes, the music Intelligence's Deuteronomy is quite good).

My larger point was the default "We can't tell you, it's proprietary" answer from Amazon.

I definitely give Amazon credit for coming as far as they have, and I fully realize this is *not* an issue most users will run into.

Still fiddling with tag versioning...

Pete