Skip to main content
Topic: iPod manager (Read 1717128 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: iPod manager

Reply #4150
It does include comments (though on older iPod models it will only be the first ~500 characters). One reason is that you should be able to create smart playlists based on values of that field. Another possible reason is that iTunesDB is used by iTunes when viewing the iPod's content.

However, you can define a remapping for the field in iPod manager preferences, so you shouldn't need to retag your files to stop it being written to the iPod's database.
Thanks!
The thing I wondered specifically about the iPod's firmware caring for the Comment field (should have remembered to mention this first time around...) is if it's used while the iPod itself is in use, and not just when connected to a computer and managed? That is, if t counts in the data limitations that make up the stock firmwares' + hardware's maximum supported track amounts? I mean that one for instance how a 5.5 gen (64MB logic board version) has a track count limit of approximately 50k tracks, which, if I'm not mistaken, is how many tracks the stock firmware can handle at once, and is directly tied to the amount of RAM present on the device and the size of the library database.

Btw, there seems to be conflicting information floating around regarding this. As you must be quite an expert on their workings, can you confirm whether this limit is on how many tracks a given iPod can (reliably) hold in general, or just on how many tracks it can queue up when shuffling?

Field remapping uses Foobar's title formatting code, I'd presume?

Re: iPod manager

Reply #4151
The thing I wondered specifically about the iPod's firmware caring for the Comment field (should have remembered to mention this first time around...) is if it's used while the iPod itself is in use, and not just when connected to a computer and managed?
If a smart playlist uses the comment field, and it has live updating turned on, and the iPod model supports live updating (for rules based on things like last played), then I assume the iPod itself would be looking at the field. That should be relatively easy to test.

That is, if t counts in the data limitations that make up the stock firmwares' + hardware's maximum supported track amounts? I mean that one for instance how a 5.5 gen (64MB logic board version) has a track count limit of approximately 50k tracks, which, if I'm not mistaken, is how many tracks the stock firmware can handle at once, and is directly tied to the amount of RAM present on the device and the size of the library database.
I don't think it's an unlikely scenario that the field is being held in memory on a 5.5G and similar models, especially if the field works with live updating. But you'd need to e.g. decompile the firmware, dump the iPod's memory or do some other manual testing to be sure.

Btw, there seems to be conflicting information floating around regarding this. As you must be quite an expert on their workings, can you confirm whether this limit is on how many tracks a given iPod can (reliably) hold in general, or just on how many tracks it can queue up when shuffling?
I don't have any specific knowledge on such a limit, unfortunately. But if RAM is the limiting factor, then I'd expect the limit to be a function of both the number of songs and the total size of the variable-length metadata fields. So the limit may well be directly proportional to the file size of iTunesDB.

Field remapping uses Foobar's title formatting code, I'd presume?
Yes, it does. You might be able to put something like $null() in it to stop it being populated at all.
.

Re: iPod manager

Reply #4152
Thanks! And sorry for the late reply, I sort of kinda almost forgot I had a question posted in the thread.  :P

Hope you don't mind being bothered with a couple of more things.
Since last time posting here, I've come across a couple of odd occurrances with foo_dop.


First off, when managing by iPod(s) I by chance happened to notice some tracks were missing. And not just not being in the expected sort order position after an action modifying the iPod database (I've noticed that can sometimes happen, as mentioned in the FAQ), but not being there at all, confirmed by looking at the "Manage contents" listing. When transfering the music, I had done that in many smaller chunks of around 2K tracks at a time (these were the initial big transferings following a factory reset done in iTunes), reasoning any potential errors or other issues would be less of a hassle to locate and fix as opposed to if I had dropped everything in one go. But there had been no error messages at any point, so expected each transfer had gone fine and didn't check after each chunk of files transfered. Should there have been messages when those 'skipped' files happened?
 
I know foo_dop at least shows a message when duplicate files already found on the iPod have not been transfered. To my knowledge, it shouldn't have been issues with the files themselves, as adding them after noticing their absence worked perfectly fine. Also, when doing these transfers of rather large bunches of files, I let my PC do that undisturbed, not doing other stuff at the same time.
Oh well, now I know to always check and confirm that all the transfered files have made it onto the iPod. Checking through the contents of two iPods for missing tracks, totaling around 52K tracks combines, took a little while...  :P :D Thank goodness for the "by artist" grouping option! That made checking the iPods' contents a lot smoother and faster. 


Now the the second thing oddity was perhaps even weirder. Earlier this week I noticed the odd iPod track here and there showing up in Foobar at the wrong positions in the 'iPod view' listing, with wrong track information to boot, that switched to showing the correct data when playing said track. Re-toggling the sorting made the affected track then show up in the expected correct spot, until you loaded the iPod library again.
Example: one time loading the iPod library, I had Satyricon's album Now Diabolical show two track #8s, "To The Mountains", the other being the real thing and the other turning out to be Primordial's "To The Edge Of The Earth" when playing them.
This phenomenon seemed to be happening purely on the Foobar/foo_dop side of things - the "Manage contents" listing showed these tracks shown in wrong position with initially incorrect information to be there on the iPod, with correct information, and they also appeared correctly on the iPod itself. It would seem that the "Rewrite database" command fixed the issue, however.

Any idea what could have caused this kind of behavior? I had never had this kind of thing happen before, the only difference I can think of is that I currently have two iPods that I've managed, as opposed to just one. Could that have had something to do with it?

I'm currently running v1.3.9 of Foobar2000 and 0.6.9.6 of foo_dop. Both somewhat outdated, admittedly. These issues might be something already fixed in newer version(s)?


Thanks again!  8)

Re: iPod manager

Reply #4153
Yes, if an error was encountered, or the file type isn't supported by the iPod etc., it will normally be reported at the end of the process.

One thing to be aware of is that if iTunes is running at the same time as foobar2000, iTunes can (later) overwrite the iTunesDB file on the iPod with what it had in memory which would cause whatever changes iPod manager made to the iPod to be lost.

You could try the 'Recover orphaned tracks' command; it looks for songs stored on the iPod but not in its database (and re-adds any it finds to the database).

On the confused tracks problem, that does sound odd but could happen if the file located at a particular file path has changed. Essentially, initially you're seeing the metadata of the file that was previously stored there, and playing the track causes the metadata to be re-read.

If it's getting confused between the two iPods, it would suggest that they're both being mounted at the same drive letter (not at the same time, of course), and those songs have the same path on both devices. Are either of those true?
.

Re: iPod manager

Reply #4154
I'm getting a security warning (Trojan) from Malwarebytes when I try to visit yuo.be/ipod_manager
Quis custodiet ipsos custodes?  ;~)

Re: iPod manager

Reply #4155
Thanks, false positive again.



Re: iPod manager

Reply #4158
Hi there!
Sorry if this is a dumb question (I think  it was answered somewhere but I can't find the solution anymore), but what do I need to do if the iPod manager can't find any metadata for some tracks? The tracks just appear with their filename, four letters in caps, and nothing else. Makes it really hard to find the song I want!

I have an iPod Nano 7th gen, using v0.7.2 of the manager and v1.6 of foobar. I should also note, I'm not using the manager to sync the iPod, only to view and play tracks from the iPod.

Thanks in advance, and thanks for this great plugin!

Re: iPod manager

Reply #4159
That sounds like those files don't contain any embedded metadata (or foobar2000 doesn't understand the metadata).

How did you tag those files initially?
.

Re: iPod manager

Reply #4160
I didn't tag them, iTunes did (I still use iTunes to sync and manage my iPod on my desktop. I use foobar and iPod manager to access and listen to music from my iPod on my laptop). So I'm pretty sure they have metadata.

There is no obvious pattern to which songs are affected by this, though all songs in an album are affected, and it's always the same albums.

Even stranger, I just realized that the Quicksearch foobar plugin is able to find and read the metadata from the songs - but when you try to play them you get errors:

these first two are successful, and found through the playlist generated by iPod manager
Opening track for playback: "D:\iPod_Control\Music\F08\YBVP.m4a"
Opening track for playback: "D:\iPod_Control\Music\F40\MFDW.m4a"
these next two are unsuccessful, and found through the playlist generated by Quick search
Opening track for playback: "http://192.xxx.xxx/content/d6c958a439a21a634ff4f10ccdd1f249.wav?profile_id=1&convert=wav"
Unable to open item for playback (Network error):
"http://192.xxx.xxx/content/d6c958a439a21a634ff4f10ccdd1f249.wav?profile_id=1&convert=wav"
Opening track for playback: "http://192.168.1.74:56923/content/ec7569930a2c18dbef9e605f0a9a7510.wav?profile_id=1&convert=wav"
Unable to open item for playback (Network error):
"http://192.xxx.xxx/content/ec7569930a2c18dbef9e605f0a9a7510.wav?profile_id=1&convert=wav"

Re: iPod manager

Reply #4161
I'm not sure what those URLs are (a search suggests foo_upnp) but they're not directly related to the iPod or the component.

The same basic conclusion holds, if you can play the songs but foobar2000 isn't showing any metadata for them (other than the file name) then it's not finding any metadata in the files.

You could try opening Properties for one of the files (in foobar2000), and then clicking on Tools and Reload info. If it succeeds and there's still no metadata displayed, it would confirm the above.

You could also check if the same holds true for the original files on your computer. If those files are OK, it would suggest they are somehow different from the ones on your iPod.

If foobar2000 isn't showing any metadata for the original files, you could check in another program such as Mp3tag to see if it can read any metadata from them.
.

Re: iPod manager

Reply #4162
Yup, yup, you're completely right, I was being dumb!
Checked in foobar and windows explorer, those files are simply missing metadata. I'll just have to go update the metadata on my desktop later. (And you guessed right: the Quick Search was finding songs in an old UPnP Search playlist that I hadn't flushed!)
Thanks so much, and sorry for the bother!

 
SimplePortal 1.0.0 RC1 © 2008-2020