GNOME Bugzilla – Bug 626923
Compilation support broken since upgrading to libgpod-sharp.
Last modified: 2010-08-26 20:46:32 UTC
With the new libgpod-sharp implementation albums marked as compilation no longer show as compilation albums on my iPod. The albums have the Various Artists flag set in Banshee and compilation support is enabled on my iPod. Things worked before I updated master to use the libgpod-sharp implementation. Preliminary tests show that the compilation flag seems to be set correctly while creating IpodTrack objects though.
Hrm, I'm not sure what's wrong. I just pushed a change that sets the IsCompilation flag before setting the AlbumArtist -- might help. Can you retest with git master?
Still doesn't work. I'm not sure how to make Rhythmbox coop with compilation albums as I did not find a field or check-box to mark an album. Hence when I copied filed to my iPod they also ended up with the regular albums and artists. I did succeed in adding a compilation album using the gtkpod iPod Manager. It correctly identified and album as a compilation album without me doing anything. I pulled in the master branch from libgpod this morning, used ./autogen.sh --prefix=/usr && make && sudo make install to make sure I got everything and in this process it might be possible it overwrote some installed Ubuntu packaged libgpod files. I don't know whether that could have an impact.
Created attachment 168130 [details] [review] error log file I don't know whether it's related, but I tried the rm -fr trick to reset my iPod and now everything seems broken.
Comment on attachment 168130 [details] [review] error log file mark as test.
Given what I observed when looking at a wrong iTunesDB written by banshee, this is a duplicate of bug #628038. In the resulting database, the compilation field wasn't set, but some other unrelated field that had no reason to be set was set to 1 (I think it was Itdb_Track::type1 or Itdb_Track::type2). Jensen, I'm marking it as a duplicate, just reopen it if it's not fixed with a newer libgpod (patch is not committed yet) *** This bug has been marked as a duplicate of bug 628038 ***