"The album covers do not upload, and most of the times the songs are
duplicated. I do not use
clementine to upload things to the ipod, at least until the
development
fixes those issues. It's great to listen to music on the pc, but not
to
manage the ipod so far."
Just a few notes on the above quote/post:
Clementine, by default, uses a secondary native database for a number
of things. Album art is one of those things. If you use the built-in
Clementine album art fetching through Last.fm and the album art
manager, it saves that retrieved artwork to the secondary Clementine
database and creates a virtual symbolic link between the database
entry and the music file. Clementine does NOT save the artwork to the
actual music file. This works great if you don't load your music onto
a portable player or share between computers across a network and are
just using your music within Clementine. If you use those files
anywhere else, the album art will NOT be included with the file. The
solution to this is to embed the album art in the music tracks in the
extended track tag metadata. Clementine does not currently offer the
option and capability to do this as Clementine only allows for non-
extended track tag editing. You'll need a separate program to do that
such as Puddletag (for Linux) or MP3Tag (for Windows) or another media
player with extended track tag editing to do that. (This is one of my
*very* few personal complaints with Clementine, for the record.)
And to play devil's advocate as far as support for the iPod
specifically. It's not like Apple is being super friendly with their
(IMHO) paranoid-level guarding of proprietary interface for the iPod
with any player that isn't iTunes. I won't bash them (publicly, at
least) and state personal opinion on the matter because, hey, it's
their business model and they are certainly free to do what they want
with it, but suffice it to say that kudos goes to any media project
that isn't iTunes that can work in any capacity with an iPod. Apple
hasn't made it easy. The fact that iPod and Clementine don't play
perfectly together is to be somewhat expected.
Apple has invented their own proprietary interface and system for
pretty much every aspect of the portable music player interface.
Everything from the code base that iPod uses to connect and transfer
files to/from a computer to having their own dedicated track tag
fields for music files for iTunes specifically. This creates a LOT of
confusion if you use your music files both on and off Apple products.
A prime example is the track tag flag that denotes if a track is part
of a compilation album or not. Itunes looks for a field called
"itunescompilationflag" within the metadata for that, and just about
every other media player out there uses the standard field
"compilation" track tag. Another example is the metadata tag for
defining the artist for a track. Some apps use the standard "artist"
field for that, while iTunes uses an (again) made-up-for-iTunes
proprietary field of "AlbumArtist" along with the standard "artist"
field so that the display text and the way the track sorts in Itunes
are separate. These fields are interpreted in different ways (if
present) by different media players and devices. Some media programs
will use one or the other, and some will use both. Same for portable
media players. This can create a rather interesting (read: confusing)
effect if you have conflicting tags or missing fields, depending on
what app or device you currently have your music tracks on. It's
entirely possible for the same single track to be listed as "Artist X"
on one player, "Artist Y" on another, and be sorted under "Artist Z"
on Itunes while displaying "Artist F" in the text, all based on what
the track metadata for that track is. And it is entirely possible to
have a track show up multiple times in a music library based on
multiple metadata track data denoting that it should be in different
places. In short, this is all a lengthy and complicated explanation
to say, "Personally, I have found that issues regarding music tracks
and Apple products being wonky is, overwhelmingly, usually resolved by
cleaning up the embedded track tag metadata." Which is why it's so
baffling to me that Clementine does not currently possess the option
to edit extended track metadata through a native Clementine option
rather than a 3rd party app.
I'm not knocking Apple or Clementine. Just saying that, for the time
being, that's the way it is, and we'll have to work around it.
Hope that helps.