Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: iPod manager (Read 2254871 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

[seemingly abandonware] iPod manager

Reply #775
I do have a further suggestion regarding my gapless problem... I am currently going through the painful process of fixing all my mp3s (roughly half of my 76Gb of MP3s are affected and foobar is little help in identifying them!).

It occured to me, why are you parsing the "accurate stream data" from the file yourself? Surely it would be much faster to use the cached data that foobar can provide. In order to add files to the iPod, they must be in a playlist which means foobar has already parsed them. That data is available via the TAGZ engine and presumably there are internal hooks in the API as well. Not only would it circumvent problems like mine, but it should also be much faster...?
It does use that data. However, the iPod also requires the audio stream byte offset of the 8th from last frame in the stream. I have to parse the audio data for that.

Also, according to this multiple id3 tags are to be expected.
Well, that is kind of more applicable to radio (or other) streams I guess. I could fix this on my side, but I think you would be hard pressed to argue you intended your files to be like this, or that there is a legitimate reason to have two id3v2 tags separated by null padding only. The iPod itself apparently doesn't always play files with double id3v2 tags if you look over the thread history a bit. I think you should complain to the EAC author instead for the brain dead tagging.
.

[seemingly abandonware] iPod manager

Reply #776
Quote
Well, that is kind of more applicable to radio (or other) streams I guess. I could fix this on my side, but I think you would be hard pressed to argue you intended your files to be like this, or that there is a legitimate reason to have two id3v2 tags separated by null padding only. The iPod itself apparently doesn't always play files with double id3v2 tags if you look over the thread history a bit. I think you should complain to the EAC author instead for the brain dead tagging.


I don't want to be a dick about this as I do appreciate your efforts... but I disagree. This *is* a bug in your plugin, whether or not you want to fix it.

I opened the file I sent you in a hex editor myself. What I found was that there are two ID3v2 tags as you say... one ID3 v2.3 and one v2.4. This is entirely reasonable. ID3v2.4 is apparently only supported by a few software players, if you want id3v2.4 then it makes some sense to include ID3v2.3 as well for backwards compatibility (instead of ID3v1 for example). Having both tags is no more or less non-standard than having id3v1 and id3v2.3, for example. Not to mention that the spec says it is allowed. Do you still think it is worth me complaining to EAC about "brain dead tagging". There is "a legitimate reason to have two id3v2 tags separated by null padding only". (The null padding is for the ID3 tag itself, so that new entries can be added to the tag without a complete file rewrite)

Anyway, I know how configure EAC for new rips... that is not the issue. The issue is that "fixing" my existing tracks is nightmarishly difficult. Foobar will not tell you which variants of id3v2 exist in a given file (nor, more importantly let you create a playlist with just those files), only that one or more of them exists. So I have no trivial way to make a playlist with just those files in, such that your suggested workaround can be applied. If any one of the files in the playlist has only one ID3v2vX tag, then it will be thrown away. The only alternatives are all extremely laborious manual processes which would take far longer than it would to fix what I can only assume is a fairly trivial piece of code (not wishing to reignite this argument, but I would happily fix it myself if the source were open).

Even if I manage to "fix" all my files... the next sync will take forever as your plugin needlessly deletes compliant files and copies them back again, stressing the HDD and probably fragmenting the files. The alternative would be to flush the whole thing and start from scratch.

As you say, we already know that I'm not the only person that is susceptible to this problem. If the iPod has ever had troubles playing these files, it certainly doesn't for me on the current firmware. There is no trivial workaround to this and you are likely to be asked about it again.

[EDIT] I've found another reason why your workaround is poor. Foobar removes the first ID3v2 tag it finds, which is the one it updates. This means that any changes you've made to id3 tags in foobar since you originally ripped the track are lost, it returns to the original ripped state. This is especially poor as EAC/LAME don't support the %album artist% tag so these have to be applied manually. Now I have to go and fix a bunch of my mix CDs which I just broke

[seemingly abandonware] iPod manager

Reply #777
[quote name='Dunc-uk' post='539145' date='Jan 4 2008, 15:39']I opened the file I sent you in a hex editor myself. What I found was that there are two ID3v2 tags as you say... one ID3 v2.3 and one v2.4. This is entirely reasonable. ID3v2.4 is apparently only supported by a few software players, if you want id3v2.4 then it makes some sense to include ID3v2.3 as well for backwards compatibility (instead of ID3v1 for example).[/quote]Well, this is clearly not what you were trying to do. Did you try and load that file in some app that only supports id3v2.3 anyway?

[quote name='Dunc-uk' post='539145' date='Jan 4 2008, 15:39']Having both tags is no more or less non-standard than having id3v1 and id3v2.3, for example.[/quote]I think it is pretty different.

[quote name='Dunc-uk' post='539145' date='Jan 4 2008, 15:39']Not to mention that the spec says it is allowed.[/quote]This is what the id3v2.3 spec says:
Quote
The ID3v2 tag header, which should be the first information in the file, is 10 bytes as follows:
It was the second tag in your file of course, so not the first information in the file.

This is what the 2.4 spec says:
Quote
  The default location of an ID3v2 tag is prepended to the audio so
  that players can benefit from the information when the data is
  streamed. It is however possible to append the tag, or make a
  prepend/append combination. When deciding upon where an unembedded
  tag should be located, the following order of preference SHOULD be
  considered.
 
    1. Prepend the tag.

    2. Prepend a tag with all vital information and add a second tag at
        the end of the file, before tags from other tagging systems. The
        first tag is required to have a SEEK frame.
     
    3. Add a tag at the end of the file, before tags from other tagging
        systems.


I didn't see any explicit reference in the actual specs to multiple tags at the beginning of the file (maybe you could point me to those), and mixing v2.3 tags and v2.4 tags. What you linked was some developer guidelines, again not about mixing v2.3 tags and v2.4 tags but metadata changes in internet streams (and it also mentions a lack of distinct files which we have here).

[quote name='Dunc-uk' post='539145' date='Jan 4 2008, 15:39']Do you still think it is worth me complaining to EAC about "brain dead tagging".[/quote]Yes. You can set it to write v2.3 tags right? If you do that, does it still add a whole new tag?

[quote name='Dunc-uk' post='539145' date='Jan 4 2008, 15:39'](The null padding is for the ID3 tag itself, so that new entries can be added to the tag without a complete file rewrite)[/quote]Right. I didn't say otherwise.

[quote name='Dunc-uk' post='539145' date='Jan 4 2008, 15:39']The issue is that "fixing" my existing tracks is nightmarishly difficult. Foobar will not tell you which variants of id3v2 exist in a given file (nor, more importantly let you create a playlist with just those files), only that one or more of them exists. So I have no trivial way to make a playlist with just those files in, such that your suggested workaround can be applied. If any one of the files in the playlist has only one ID3v2vX tag, then it will be thrown away. The only alternatives are all extremely laborious manual processes which would take far longer than it would to fix what I can only assume is a fairly trivial piece of code [/quote]All you are proving is that it is entirely impractical (for you/a user) to work with files with multiple id3v2 tags at the beginning. I am pretty sure that method I mentioned to remove the first tag using foobar2000 isn't by design, just a result of it not expecting multiple id3v2 tags in this manner. Unticking ID3v2 and then opening the dialog again to see it ticked again should be a good indicator of that.

[quote name='Dunc-uk' post='539145' date='Jan 4 2008, 15:39'](not wishing to reignite this argument, but I would happily fix it myself if the source were open).[/quote]Try a hex editor and disassembler instead then? What did you really expect me to say to that?

[quote name='Dunc-uk' post='539145' date='Jan 4 2008, 15:39']Even if I manage to "fix" all my files... the next sync will take forever as your plugin needlessly deletes compliant files and copies them back again, stressing the HDD and probably fragmenting the files. [/quote]No it is not needless. You modify the file, it gets updated on the iPod. Metadata etc. *is* important information. One example of the iPod using it is that it reads lyrics directly from the id3v2 tag.

[quote name='Dunc-uk' post='539145' date='Jan 4 2008, 15:39']If the iPod has ever had troubles playing these files, it certainly doesn't for me on the current firmware.[/quote]As far as I am aware it was just an issue on the iPod Classic/Nano 3G. It didn't sound like you had one of those.

[quote name='Dunc-uk' post='539145' date='Jan 4 2008, 15:39'][EDIT] I've found another reason why your workaround is poor. Foobar removes the first ID3v2 tag it finds, which is the one it updates. This means that any changes you've made to id3 tags in foobar since you originally ripped the track are lost, it returns to the original ripped state.[/quote]Well, I knew that. I don't know why you blame my workaround though when you are just showing you don't have a practical way to manipulate that second tag.
.

[seemingly abandonware] iPod manager

Reply #778
Quote
Yes. You can set it to write v2.3 tags right? If you do that, does it still add a whole new tag?


OK you got me there. If I untick the EAC box for ID3v2.4 then it still writes an extra ID3 tag. That certainly looks like an EAC bug.

However, your claim that it is non-standard and therefore not worth supporting is weak. The parts of the spec you quote don't explicitly deal with the possibility of multiple id3v2 tags, to claim that they imply this is disallowed is disingenuous, especially when the accompanying developers guide says that it should be supported.

Quote
It was the second tag in your file of course, so not the first information in the file.


Are you suggesting that reversed tags would work with your app (i.e. 2.3 before 2.4)?

iTunes copes with multiple tags perfectly well as does every mp3 player I've ever tried (including the audio player your plugin is based upon) - they are all perfectly capable of finding the beginning of the audio stream and determining gapless data. I think it would at least be worth noting in your FAQ that your plugin doesn't support files like these. I really don't understand why you are so against adding this to the list of things to do. It really can't be more than a few lines of code. I'm not demanding an instant fix / workaround, merely requesting that you add it to the TODO list.

Oh well, I guess I'll have to write an app that scans all my MP3s and spits out an m3u of tracks that suffer from this. Maybe with a view to adding a function to strip the tags too.

[seemingly abandonware] iPod manager

Reply #779
Oh well, I guess I'll have to write an app that scans all my MP3s and spits out an m3u of tracks that suffer from this. Maybe with a view to adding a function to strip the tags too.

Why not just use MP3Tag to write all tags to a text file, have it remove all ID3v2 tags then re-apply them from the text file?

No need to re-invent the wheel, and TBH it's more comfortable than Foobar2000 when it comes to editing tags.
np: 4'33"

[seemingly abandonware] iPod manager

Reply #780
OK you got me there. If I untick the EAC box for ID3v2.4 then it still writes an extra ID3 tag. That certainly looks like an EAC bug.
Next question: why doesn't it itself write both v2.4 and v2.3 tags before the audio data if you enable that option?

Quote
Are you suggesting that reversed tags would work with your app (i.e. 2.3 before 2.4)?
No. I am implying your file didn't comply with the statement in that quote. You were the one saying it is in the spec and referred to something that was not the spec and was actually out of context here anyway. Did you find me some software that itself writes both id3v2.4 and v2.3 tags at the beginning of the file? Don't you wonder why foobar2000 doesn't do that?

Quote
iTunes copes with multiple tags perfectly well as does every mp3 player I've ever tried (including the audio player your plugin is based upon) - they are all perfectly capable of finding the beginning of the audio stream and determining gapless data.
OK let me make it clear:
They don't skip the second id3v2 tag because it is an id3v2 tag. They skip it because they are written to skip junk data while seeking to the first MPEG frame. This is confirmed by the fact that iTunes *does not* play (or accept) the sample file someone else previously provided that the iPod also doesn't play. It is similar to yours except the second id3v2 tag is 23KB. Clearly iTunes/the iPod wasn't written to skip so much garbage data. I also made my own test file with similar results.

Similarly, you can replace the second id3v2 tag with some random bytes (that doesn't look like audio data) and foobar will still play the file. I just am not trying to write a complete audio player / MP3 decoder that covers every possible contingency.

I think it would at least be worth noting in your FAQ that your plugin doesn't support files like these.
I can change the error message. And I may write a FAQ entry on skipped files on the iPod.

I really don't understand why you are so against adding this to the list of things to do. It really can't be more than a few lines of code. I'm not demanding an instant fix / workaround, merely requesting that you add it to the TODO list.
Because in the time it takes to add it to the to-do list I could change my code (if I wanted to). I could have changed it several times over in the time I wrote this post as well. I just am not changing it because one person ripped all their files with screwed up settings/software/whatever. Before you refer to the other person I referred to, they were complaining about the file not playing on their iPod.
.

[seemingly abandonware] iPod manager

Reply #781
musicmusic, after thinking about this some more I see you are right... mp3s are not intended to have more than one id3v2 tag, I was wrong about that. The only way to achieve this is through an EAC bug.

As a matter of pragmatism it may prove useful to some people if you could put handling for garbage data in their mp3s rather than refuse to parse them... you could also spit out a warning so that people are aware, so they can fix them if they choose.


Oh well, I guess I'll have to write an app that scans all my MP3s and spits out an m3u of tracks that suffer from this. Maybe with a view to adding a function to strip the tags too.

Why not just use MP3Tag to write all tags to a text file, have it remove all ID3v2 tags then re-apply them from the text file?

No need to re-invent the wheel, and TBH it's more comfortable than Foobar2000 when it comes to editing tags.


I think I'd fixed most of my files anyway, but this should work to fix the rest. Thanks!

[seemingly abandonware] iPod manager

Reply #782
As a matter of pragmatism it may prove useful to some people if you could put handling for garbage data in their mp3s rather than refuse to parse them...
Yes I will try and do that

you could also spit out a warning so that people are aware, so they can fix them if they choose.
Well, I can't really see a way that wouldn't seem out of context (it probably won't impact gapless playback).
.

[seemingly abandonware] iPod manager

Reply #783
Yes I will try and do that


Thanks! I've a feature suggestion to bounce off you... not all of my tracks have gapless information included. I've no particular interest in having the majority of them play gaplessly anyway, but iTunes has an annoying habit of trying to estimate the gaps for these tracks whenever I use it to add a video or podcast, which I think screws up their album art in the process.

Would it be easy to have an option to add ineffective / null gapless data to the database for these tracks, so iTunes doesn't think it needs to do this? Alternatively, it looks like iTunes has some sort of "ignore gapless" flag it can add to the id3. I presume you have no intention of adding gapless guessing routines anyway, I certainly have little use for them.

[seemingly abandonware] iPod manager

Reply #784
Excellent plugin! I love the way it interfaces seamlessly with foobars playlists. Goodbye bloated iTunes.

I want to report some strange behavior on my 6G ipod classic which I am not certain was intended.

If for example from a blank state (no mp3's) I synchronize my media library and playlists, it will copy the songs that are in the playlists over twice into two separate files! That is, it seems to first see an mp3 in the media library and copy it over, and then when it sees it again on a playlist it will copy it over a second time.
Browsing on the ipod, it will confirm that there are in fact duplicate songs of anything that was on a playlist.
If, after this occurs, I synchronize again with the media library and same playlists selected however, it will report that it has removed some files, and indeed they are the duplicate entries.

So it's not a huge deal, I just synchronize twice whenever I want to update the ipod. This seems to me like unintended behavior, so I thought I should report it.

edit - nevermind; upgraded from foobar 0.9.4.5 to 0.9.5 and that seemed to fix it! Nice plugin!

[seemingly abandonware] iPod manager

Reply #785
Thanks! I've a feature suggestion to bounce off you... not all of my tracks have gapless information included. I've no particular interest in having the majority of them play gaplessly anyway, but iTunes has an annoying habit of trying to estimate the gaps for these tracks whenever I use it to add a video or podcast, which I think screws up their album art in the process.

Would it be easy to have an option to add ineffective / null gapless data to the database for these tracks, so iTunes doesn't think it needs to do this?
Well I would still need to seek through the file to calculate the value of the field I mentioned before. Basically, I don't think it is worth it, because I believe iTunes will still decide to 'correct' all the metadata/artwork when you try to add a file.

Excellent plugin! I love the way it interfaces seamlessly with foobars playlists. Goodbye bloated iTunes.

I want to report some strange behavior on my 6G ipod classic which I am not certain was intended.

If for example from a blank state (no mp3's) I synchronize my media library and playlists, it will copy the songs that are in the playlists over twice into two separate files! That is, it seems to first see an mp3 in the media library and copy it over, and then when it sees it again on a playlist it will copy it over a second time.
Browsing on the ipod, it will confirm that there are in fact duplicate songs of anything that was on a playlist.
If, after this occurs, I synchronize again with the media library and same playlists selected however, it will report that it has removed some files, and indeed they are the duplicate entries.

So it's not a huge deal, I just synchronize twice whenever I want to update the ipod. This seems to me like unintended behavior, so I thought I should report it.

edit - nevermind; upgraded from foobar 0.9.4.5 to 0.9.5 and that seemed to fix it! Nice plugin!
Hi,
Yes of course you are right it is not meant to behave like that. I found something that may cause that to not work correctly, I'll change that for next build so it should work reliably then.
.

[seemingly abandonware] iPod manager

Reply #786
Firstly, this works perfect with my ipod classic 160gb.

There is only one thing I would like is to be able to see the tracks being transferred instead of it saying copying files, so I can see how long its going to take to finish.

Thanks!

[seemingly abandonware] iPod manager

Reply #787
[Well I would still need to seek through the file to calculate the value of the field I mentioned before. Basically, I don't think it is worth it, because I believe iTunes will still decide to 'correct' all the metadata/artwork when you try to add a file.


Hmm, I don't think I explained very well... when your plugin decides that a track has no gapless data, it seems to leave the database in a state which makes iTunes think it still needs to scan the track itself.

For example, when I first loaded up my iPod classic, I forgot to tick the gapless tick box in foobar. When I next used iTunes, it started scanning all 11,000 tracks one by one (which I cancelled).

I later manually used the plugin "Determine gapless information" and it found gapless info for about half my tracks. However, next time I used iTunes to load a video, it started scanning again... only this time it only had about 5,000 tracks to scan, presumably because the others had already been updated by your plugin. If all my tracks had gapless info, iTunes would not have tried to do anything as your plugin would have correctly added gapless data for every track. Having now fixed all of my files with the id3 problem and resynced, iTunes now thinks I've got about 1000 tracks that need scanning.

So all I would like is an option for the plugin - having already scanned the tracks itself - to mark in the database those tracks that definitely have no gapless data, in such a way that iTunes doesn't try to re-scan them. Not being familiar with the iPod database, I don't know if this is possible.

On a loosely related note, it would seem that "SharePod" does something to the iPod database that makes your plugin think it is corrupt (I've been using this to add videos, to get around the iTunes problems). Mine is a Classic 160Gb.

Whatever it does, iTunes doesn't mind and seems to fix it so your plugin works with it again... I've no idea if this is a bug in SharePod or your plugin, but I seem to remember reading earlier in the thread someone else having this problem with another iTunes style app.

SharePod website

 

[seemingly abandonware] iPod manager

Reply #788
Some (very) late replies:
Now, a couple questions:
Currently there's no support for doing replaygain when autoconverting files.  Is this something you have planned at all?  Currently I'm converting manually and replaygain scanning before sending to iPod, but it would be great if it could be fixed to do it for me.
I also want that feature, however the problem is the lack of any proper replaygain API. I can essentially run the menu command on my side to do the scan, but that will possibly trigger popup dialogs (as well as secondary progress dialogs though there are already a few of those) and some other inefficiencies. The main issue is those user prompts that may appear though.

The good news is that if you let foo_dop convert the files itself, and manually replaygain scan the copies on your iPod those files will not be recopied on next sync (unless the local copy was modified). You can use the 'Update metadata in ipod library' command to update the soundcheck values in the database after the manual replaygain scan. (Of course if you're regularly sending files that need to be converted it's a bit tedious)

Tedious, and there's the problem of figuring out which files need to be scanned.  I can't think of any way in foobar to sort by replaygain.  In an average week I probably send a few hundred tracks to my iPod with about half being mp3 and the other half being a mix of flac, tak, and ogg.  Even more tedious than having to manually scan the files and the update metadata is having to first check every file sent to see whether it needs to be scanned.  Something as simple as an optional dialog box that would pop up after a send operation and list which files were converted would make the process easier.  Sort of the opposite of the transcode warning someone wanted earlier, I want to know what was converted once the job is done so I can do some followup, not before.  Currently I leave covnersion off so that the files will error out, then convert them to a temp dir, replaygain scan, and send in a second batch.

Second, there's an issue that's been bugging me for a while with smart playlists and the "load library and playlists" menu option.  I use a lot of smart playlists that are based off time - "50 most played songs in the last 1 month", "50 most played songs in the last 3 months", "songs played in the last 7 days", etc.  When I load the playlists in foobar they seem to be a cached version.  Judging from the contents I think it's from the last time I actually used iTunes to send something to my iPod.  When using the playlists on my iPod they all work correctly, but in foobar they just seem to be some old cached copy instead of being calculated.  Is there something I'm doing wrong, is it a bug, or is it just not supported?
It's a bit of a quirk. Basically, for 'Live-updating' smart playlist the iPod dynamically generates content for the playlist (which you only see on your iPod). The smart playlists also have associated 'static' items which I guess are only of use (on the ipod itself) with 'Live-updating' disabled. iTunes updates those static entries whenever you use it (by basically applying the smart playlist rules to the ipod library) but foo_dop does not (I think you can imagine writing handlers to apply all of those specific rules would be pretty complicated)

Ah.  Weird, but that does explain the problem.  It's mainly an issue for me because I use my ipod as a portable music hard drive 8+ hours a day at work.  None of my playlists work there.  I can see your point about applying all the rules.  It doesn't feel like much to me since all my smart playlists are based off number of plays, date added, and/or date last played, but I realize that there's a ridiculous amount of options for smart playlists.  Thanks for the reply.

1. It's currently unsorted: it is just the order they are in the iPod database. In general that is the order they were added to the iPod. I use this so I may add an option to control the sorting.

Is there any chance of getting some options for controlling the order that they're sent?  This is related to my smart playlists and to using it as a hard drive full of music while at work.  In all the smart playlists that are based solely off time and not off number of plays, the songs are displayed in the order they were added to the database.  The plugin seems to be very fickle as to what order it sends them in, depending on whether the album is VA or not and how I click on them in the playlist for sending.  Sometimes I get everything in the same order as they were in my playlist, sometimes I get completely jumbled, sometimes I get some albums completely in order with others mixed together, etc etc.  It makes browsing those playlists very interesting.  Sorting by album before sending, or simply always sending in the same order as they currently are in the playlist would make me much happier.

---

Also, for the people with the dual ID3 problems, wouldn't "select all->right click->Tagging->MP3 tag types->checking APEv2 and unchecking everything else->applying->going back in and doing it again to make sure all ID3v2 tags are gone->applying->going back in and checking Id3v2 and unchecking everything else" take care of it?

[seemingly abandonware] iPod manager

Reply #789
Hmm, I don't think I explained very well... when your plugin decides that a track has no gapless data, it seems to leave the database in a state which makes iTunes think it still needs to scan the track itself.

[...]

So all I would like is an option for the plugin - having already scanned the tracks itself - to mark in the database those tracks that definitely have no gapless data, in such a way that iTunes doesn't try to re-scan them. Not being familiar with the iPod database, I don't know if this is possible.

I don't think any such flag to indicate a file has been scanned for gapless data and it wasn't fond exists in the database (I looked and didn't find any). Bear in mind that iTunes likes to estimate the data. So I reckon it probably just tries to fill missing data.

I don't know if it helps you, but I finally managed to put all the pieces together to calculate the gapless data for Nero MP4 (AAC) files (recent Nero encoders only). So they will get gapless data from next version of foo_dop as well.

On a loosely related note, it would seem that "SharePod" does something to the iPod database that makes your plugin think it is corrupt (I've been using this to add videos, to get around the iTunes problems). Mine is a Classic 160Gb.

Whatever it does, iTunes doesn't mind and seems to fix it so your plugin works with it again... I've no idea if this is a bug in SharePod or your plugin, but I seem to remember reading earlier in the thread someone else having this problem with another iTunes style app.

SharePod website
What is the error message? If it is 'Unsupported format or corrupted file' it is probably some incorrect size field or something, foo_dop checks those very strictly whereas iTunes is probably a bit more liberal there. Is there something you dislike about using foo_dop for videos?

Tedious, and there's the problem of figuring out which files need to be scanned.  I can't think of any way in foobar to sort by replaygain.  In an average week I probably send a few hundred tracks to my iPod with about half being mp3 and the other half being a mix of flac, tak, and ogg.  Even more tedious than having to manually scan the files and the update metadata is having to first check every file sent to see whether it needs to be scanned.  Something as simple as an optional dialog box that would pop up after a send operation and list which files were converted would make the process easier.  Sort of the opposite of the transcode warning someone wanted earlier, I want to know what was converted once the job is done so I can do some followup, not before.  Currently I leave covnersion off so that the files will error out, then convert them to a temp dir, replaygain scan, and send in a second batch.
The ReplayGain Scanner skips files with existing replaygain data. Anyway, I can't automate this at all (apart from the possible user prompts during the scan I don't seems to have anyway of knowing when the scan is finished.) So yes, the best I can do is ask to send the converted files to a playlist so you can manually scan and reload info on them.

Is there any chance of getting some options for controlling the order that they're sent?  This is related to my smart playlists and to using it as a hard drive full of music while at work.  In all the smart playlists that are based solely off time and not off number of plays, the songs are displayed in the order they were added to the database.  The plugin seems to be very fickle as to what order it sends them in, depending on whether the album is VA or not and how I click on them in the playlist for sending.  Sometimes I get everything in the same order as they were in my playlist, sometimes I get completely jumbled, sometimes I get some albums completely in order with others mixed together, etc etc.  It makes browsing those playlists very interesting.  Sorting by album before sending, or simply always sending in the same order as they currently are in the playlist would make me much happier.
Do you mean you are sorting your smart playlists by date added to your iPod? I see how that may cause some issues. The order they are added was just a result of my handling for duplicate items, but it should be possible to change it back to the order the items are received (order in playlist etc.) (edit: seems a bit more complicated than I thought but I'll put it on my todo)
.

[seemingly abandonware] iPod manager

Reply #790
Sorry if this was covered before, I did do a quick search.

Is it possible to have the albums in the iPod library sorted first by date and then by name, or you don't have any control over this?

For example, Music -> Artists -> Led Zeppelin gives me:
  • Houses of the Holy
  • Led Zeppelin
  • Led Zeppelin II
  • Led Zeppelin III
  • Led Zeppelin IV
  • ...

And I would like go get:
  • Led Zeppelin
  • Led Zeppelin II
  • Led Zeppelin III
  • Led Zeppelin IV
  • Houses of the Holy
  • ...

[seemingly abandonware] iPod manager

Reply #791
I don't think any such flag to indicate a file has been scanned for gapless data and it wasn't fond exists in the database (I looked and didn't find any). Bear in mind that iTunes likes to estimate the data. So I reckon it probably just tries to fill missing data.


Yes, I expect that iTunes deduced the scanned status implicitly... if it is marked has having "accurate" or "estimated" gapless info then by definition it has been scanned. Here is where a workaround may be possible... I assume foo_dop doesn't use the "estimated" option for gapless as it has no mechanism for estimating gapless info (and I don't think anybody wants one). I presume iTunes estimates gapless info by just scanning for silence at the beginning and end of the track. Of course, some tracks may not have any silence at all (the track genuinely ends at the end of an MPEG frame) and so iTunes will add estimated gapless data to this effect.

What foo_dop could do is mark all tracks with no accurate data as having "estimated" gapless data that equates to "no lead in, no lead out". The iPod playback of the file would be completely unaffected but iTunes would think the file had been scanned already and would not try to rescan.

I don't know if it helps you, but I finally managed to put all the pieces together to calculate the gapless data for Nero MP4 (AAC) files (recent Nero encoders only). So they will get gapless data from next version of foo_dop as well.


Not me personally as I don't have any AAC files, but I'm sure other people will be. Good work!

What is the error message? If it is 'Unsupported format or corrupted file' it is probably some incorrect size field or something, foo_dop checks those very strictly whereas iTunes is probably a bit more liberal there. Is there something you dislike about using foo_dop for videos?


Yes I think it was that message... I only used this app as it offered more flexibility over how to classify videos (i.e. as Music Video, TV Show, Film etc.). Some of the other apps (and iTunes) allow you to edit video specific metadata about the show, like episode number, series etc. I've nothing against using foo_dop, but as foobar isn't much of a video handler itself I wasn't expecting much in that regard from foo_dop.

Had you considered a dedicated video handling dialogue, for adding video and editing the database metadata directly? Just a thought.

[edit] Oh wow, how did I never spot the video specific metadata fields in your FAQ? Doh!

[seemingly abandonware] iPod manager

Reply #792
OK, I have a feature request. I've fallen over a bug / feature of the new iPod classic, whereby it orders episodes in a TV series according to the "release date" and not the episode number. See:

http://discussions.apple.com/thread.jspa?messageID=6298710

Could we get a field mapping for this database field? Or is there one already?

[edit] on the other hand it is widely being reported as a bug in the latest firmware, hopefully Apple will fix it.

[seemingly abandonware] iPod manager

Reply #793

Is there any chance of getting some options for controlling the order that they're sent?  This is related to my smart playlists and to using it as a hard drive full of music while at work.  In all the smart playlists that are based solely off time and not off number of plays, the songs are displayed in the order they were added to the database.  The plugin seems to be very fickle as to what order it sends them in, depending on whether the album is VA or not and how I click on them in the playlist for sending.  Sometimes I get everything in the same order as they were in my playlist, sometimes I get completely jumbled, sometimes I get some albums completely in order with others mixed together, etc etc.  It makes browsing those playlists very interesting.  Sorting by album before sending, or simply always sending in the same order as they currently are in the playlist would make me much happier.
Do you mean you are sorting your smart playlists by date added to your iPod? I see how that may cause some issues. The order they are added was just a result of my handling for duplicate items, but it should be possible to change it back to the order the items are received (order in playlist etc.) (edit: seems a bit more complicated than I thought but I'll put it on my todo)

I'm not explicitly sorting by that, but it's the criteria for being added to most of my smart playlists.  Most of them are of the type "Date added < [1|7|30] days" or "Last played < [1|2|7] days"  Anything based off number of plays is sorted by that and is easy enough to browse that way, but all of the time based ones appear to be sorted by when they were added onto the iPod.  So when I use those playlists on my iPod, browsing gets interesting.  Also when I do a load library in foobar2000 and play songs off my ipod as an external hard drive, I generally just skip to the bottom of the list and listen to the most recently added stuff.  In foobar it's easy enough to re-sort the albums that are jumbled up, but on the iPod itself it's a pain.

[seemingly abandonware] iPod manager

Reply #794
Sorry if this was covered before, I did do a quick search.

Is it possible to have the albums in the iPod library sorted first by date and then by name, or you don't have any control over this?
I do have control over this. However, messing with the sort order can get complicated, mainly due to issues with the 5G iPod. If they added support for all of the sort fields in the last firmware update for the 5G then it would make my life easier. I am not sure if they did though. It's easy to check though if you have a 5G iPod: Hold Ctrl whilst clicking the 'View iPod device information' button in foo_dop prefs. Check if there is an entry as follows:
Code: [Select]
<key>SortFieldsSupported</key>
<true/>


Yes, I expect that iTunes deduced the scanned status implicitly... if it is marked has having "accurate" or "estimated" gapless info then by definition it has been scanned. Here is where a workaround may be possible... I assume foo_dop doesn't use the "estimated" option for gapless as it has no mechanism for estimating gapless info (and I don't think anybody wants one). I presume iTunes estimates gapless info by just scanning for silence at the beginning and end of the track. Of course, some tracks may not have any silence at all (the track genuinely ends at the end of an MPEG frame) and so iTunes will add estimated gapless data to this effect.

What foo_dop could do is mark all tracks with no accurate data as having "estimated" gapless data that equates to "no lead in, no lead out". The iPod playback of the file would be completely unaffected but iTunes would think the file had been scanned already and would not try to rescan.

Ignoring other concerns, setting the track's gapless data as 'estimated' doesn't seem to stop iTunes from rescanning it.

Yes I think it was that message... I only used this app as it offered more flexibility over how to classify videos (i.e. as Music Video, TV Show, Film etc.). Some of the other apps (and iTunes) allow you to edit video specific metadata about the show, like episode number, series etc. I've nothing against using foo_dop, but as foobar isn't much of a video handler itself I wasn't expecting much in that regard from foo_dop.

Had you considered a dedicated video handling dialogue, for adding video and editing the database metadata directly? Just a thought.

[edit] Oh wow, how did I never spot the video specific metadata fields in your FAQ? Doh!
Hmm yes as you noticed it is possible to control those through metadata  I did realise already that a specific tagging dialog for those fields is kinda needed, but I put it off as just the underlying functionality is good enough, at least for a TEST version anyway  As a compromise you could use Quick/Mass Tagger presets.

OK, I have a feature request. I've fallen over a bug / feature of the new iPod classic, whereby it orders episodes in a TV series according to the "release date" and not the episode number. See:

http://discussions.apple.com/thread.jspa?messageID=6298710

Could we get a field mapping for this database field? Or is there one already?

[edit] on the other hand it is widely being reported as a bug in the latest firmware, hopefully Apple will fix it.
Hmm no remapping but there are metadata fields for them. There are various sort tables for the TV shows so not sure if the Classic is not using them or they are the problem or what... iTunes 7.6 was released very close to the recent firmware update. I'll try and check it out anyway.

I'm not explicitly sorting by that, but it's the criteria for being added to most of my smart playlists.  Most of them are of the type "Date added < [1|7|30] days" or "Last played < [1|2|7] days"  Anything based off number of plays is sorted by that and is easy enough to browse that way, but all of the time based ones appear to be sorted by when they were added onto the iPod.  So when I use those playlists on my iPod, browsing gets interesting.  Also when I do a load library in foobar2000 and play songs off my ipod as an external hard drive, I generally just skip to the bottom of the list and listen to the most recently added stuff.  In foobar it's easy enough to re-sort the albums that are jumbled up, but on the iPod itself it's a pain.
OK. I'm looking into changing it.
.

[seemingly abandonware] iPod manager

Reply #795
Ignoring other concerns, setting the track's gapless data as 'estimated' doesn't seem to stop iTunes from rescanning it.


Hmm, that is odd... somehow iTunes does know whether it has personally scanned a track. It also does avoid rescanning tracks that foo_dop has marked as having accurate data. It is a mystery. 

As a compromise you could use Quick/Mass Tagger presets.


Actually, I've now set up several presets and the masstagger working fairly well for me... a dialogue would be nice, but I do appreciate this is still in beta phase.

Hmm no remapping but there are metadata fields for them. There are various sort tables for the TV shows so not sure if the Classic is not using them or they are the problem or what... iTunes 7.6 was released very close to the recent firmware update. I'll try and check it out anyway.


Down the bottom of that thread I linked, it is mentioned that the Classic sorts by release date. I managed to get episodes sorted properly using a combination of foo_dop/Foobar and iTunes. I used the masstagger to format the Date field in the form YYYY-MM-%tracknumber% with an arbitrary year and month. Upon updating the metadata in the database, the files were still arranged weirdly.

I then clicked "Get Info" on the first 3 (of 13) files in iTunes. The next time I checked the episode sorting on the iPod, those three files had release dates and were listed in order (last as it happens). So I went back to iTunes and clicked "Get Info" on each file in turn (doing them all at once doesn't work). Now they're all in the correct order, listed and sorted by my faked release date. Looks like iTunes is using some mystery field.

[UPDATE] Never mind, the Classic 1.1 firmware fixes the episode sorting problem.

[seemingly abandonware] iPod manager

Reply #796
Quote
I do have control over this. However, messing with the sort order can get complicated, mainly due to issues with the 5G iPod. If they added support for all of the sort fields in the last firmware update for the 5G then it would make my life easier. I am not sure if they did though. It's easy to check though if you have a 5G iPod: Hold Ctrl whilst clicking the 'View iPod device information' button in foo_dop prefs. Check if there is an entry as follows:
iPod Classic here, maybe someone else can help.

[seemingly abandonware] iPod manager

Reply #797
Hmm, that is odd... somehow iTunes does know whether it has personally scanned a track. It also does avoid rescanning tracks that foo_dop has marked as having accurate data. It is a mystery.
Well, it is probably just looking at the actual data (checking if the encoder delay/padding is set to null/zero). The 'estimated'/'accurate' thing is just observed values of some field - what that field is actually for who knows.
.

[seemingly abandonware] iPod manager

Reply #798
Well, it is probably just looking at the actual data (checking if the encoder delay/padding is set to null/zero).


But what if iTunes scans a file to estimate gapless which genuinely has no lead-in or lead-out? Does it perpetually rescan it every time you fire it up?

[seemingly abandonware] iPod manager

Reply #799
Awesome plugin man!!!

I read through quite a bit of the topic, but I could not find what I was looking for, so please don't flame me for it.

Is there any way to change the way the iPod sorts?
For instance: A-Z now comes before 0-9. Is there any way of reversing this with your plugin?
Last time I heard, iTunes is what sorts the music in this manner, not the firmware of the iPod, so could your program help change this?

Cheers.

EDIT: Found it on the FAQ page that sorting is on the to-do-list. Cool.