QUOTE(alphaex32 @ Dec 14 2006, 00:14)

I think basing these options on metadata would be a good way to do it though, because otherwise you would need to reset them anytime you take songs off the ipod and put them back on. For example, Im always swtiching around my ipod nano library, and it would be nice if I didnt have to set these options more than once. Doing it through tags would also allow us to set these options easily with scripts or with trackinfo buttons.
I see what you are saying. I would prefer the fields to be stored in an external database rather than the tags itself - but realistically that's not going to happen. Ideally I guess I'll add both tag-based and non tagged based methods.
QUOTE(mdhare007 @ Dec 15 2006, 04:47)

There are no dumb questions, right? Ok, here is a possible dumb one. With recent developments I'm anxious to try foo_dop out, but I have some possible concerns with the playlist feature.
I have a live version and a non live version of a track that share the common following tags
Artist: Foo
Title: Bar
However, the live version also has
Comment: Live
It sounds like if I upload two playlists, one with the live version and another with the non live version, I may not get the desired results based on the following text.
"Files are matched to those on your iPod using metadata (ARTIST, TITLE and ALBUM fields). Therefore any track without metadata may be matched to the wrong track."
Is there a way around this with the currently existing features? Is this what 'Metadata 'mapping' fields do' in tools->ipod manager? Is the solution to put something like '%title%[ {%comment%}]' into Title mapping?
If the ARTIST, ALBUM and TITLE fields match exactly for those files, then yes they will get mixed up. This does not depend on field re-mappings. It also only affects the "Send playlists to iPod" and not the syncronise feature.
The reason behind this is to avoid duplicates if the file has been modified locally since this is not a sync operation (where the old version would get deleted from the iPod). I'm not sure changing the fields it uses is going to help so much - definitely I am not going to add COMMENT to the list. Does neither the TITLE nor ALBUM vary for your files?
Next version will store the source path on the iPod for files sent using foo_dop. This info could be used in future versions to seperate two matching files (if you don't move your files around).
QUOTE(splint3r @ Dec 16 2006, 08:39)

Hi musicmusic,
I have been watching this thread for a while now and regularly checking the changelog with my fingers crossed, hoping to see a line go through the first item on the request list, 'Add dynamic transcoding to support other formats like FLAC'.
I see this list is not in order of priority so i guess i have to ask again, how important is this feature to you? And my second question is what would it take to make it more important?
All of my tunes are either in Flac or some obscure codec (mpc) and i would dearly love to simplify sending files to my girlfriends Ipod using Foobar2000 V9.x.
It is somewhat important to me (I have tracks in MPC, OGG Vorbis, WavPack, WMA, ... too) but there are lots of issues surrounding it:
-tracking the files properly for sync. This can be solved my storing necessary data in foo_dop's db it will store in iPod from next version
-the actual conversion. There is no convertor API or source - so I would have to rewrite large chunks of it for a decent level of functionality.
I will most likely work on it at some point. But its quite complicated.