[seemingly abandonware] iPod manager, also known as foo_dop Options

[musicmusic]

iPod management component for foobar2000 0.9.5+.

Home page with details and download

Notes/FAQs/changelog available here. If you read the notes and FAQs before asking any questions, it will keep me happy

When posting problem reports, include:
-Operating system
-iPod/iPhone model and firmware version

This post has been edited by musicmusic: Feb 22 2010, 18:41

[musicmusic]

I'm pretty sure my 4G supports non-ascii characters, at least the europeanish ones. It correctly displays all the weird characters in Sigur Rós track names.

But that's not the filename, is it? The metadata is usually fine. (In fact, stored in Unicode).

However, one character that my iPod refuses to display in the ARTIST list is ý. I wonder if they fixed that in later models.

Edit: the Mount and Unmount commands used to work fine (I have iPodService installed, and am using firewire,) but now i get:

IDispatch error #56938 Code: -7FFB1F96

I have seen it do that once too, it seems to be slightly temperamental (I didn't change anything from the previous versions). My guess is it has something to do with whether iTunes is running. I have no idea what the error code means right know, because the iPodService uses its own error codes. I'll see if I can work it all out..

Edit: Just tested 0.2.4 on my 4G, seems to work fine, however it messes up the sort order (it's now purely alphabetical, it used to ignore 'The'. Perhaps once this component matures we could configure a custom formatting string for use in sorting the Artist/Albums/Tracks?

Known, mentioned someplace on wiki.

The sort strings I am using are:

CODE

            t_index_pattern library_indices[] =
            {
                {library_index_types::title, "%title%"},
                {library_index_types::album_disc_tracknumber_title, "%album%|%discnumber%|$num(%tracknumber%,2)|%title%"},
                {library_index_types::artist_album_disc_tracknumber_title, "%artist%|%album%|%discnumber%|$num(%tracknumber%,2)|%title%"},
                {library_index_types::genre_artist_album_disc_tracknumber_title, "%genre%|%artist%|%album%|%discnumber%|$num(%tracknumber%,2)|%title%"},
                {library_index_types::composer_title, "%composer%|%title%"}
            };

If I make those strings user-configurable, there's some room for user error, since they have to follow a specific pattern. I guess putting it on the advanced prefs page would counter-act that Alternatively I could make each of those fields configurable (TITLE, ALBUM, ..) which would also eliminate that.

The other alternative is not writing the 'sort tables' at all, which seems to give back the normal ordering, but that make browsing the library super-slow (on my 3G at least).

This post has been edited by musicmusic: Jun 14 2006, 09:27

[david_dl]

I'm pretty sure my 4G supports non-ascii characters, at least the europeanish ones. It correctly displays all the weird characters in Sigur Rós track names.

But that's not the filename, is it? The metadata is usually fine. (In fact, stored in Unicode).

Sorry, mustn't have read the previous post properly

If I make those strings user-configurable, there's some room for user error, since they have to follow a specific pattern. I guess putting it on the advanced prefs page would counter-act that Alternatively I could make each of those fields configurable (TITLE, ALBUM, ..) which would also eliminate that.

The other alternative is not writing the 'sort tables' at all, which seems to give back the normal ordering, but that make browsing the library super-slow (on my 3G at least).

Advanced prefs page sounds like a good idea; at least then users can have a fiddle and restore the defaults if they break something.

Also, for the soundcheck values, is album or track gain used? Perhaps this could be user configurable, as well as a replaygain 'preamp' value for those with volume limited (european) iPods.