Metadata transfer for existing songs generates error
I copied most of my music library from my iPod's library to a new computer, but I already had a few songs in my library via iTunes' built-in "Transfer Purchases" functionality for songs that were purchased from the iTunes Store.
In PodWorks 2.9.3's preferences, I've selected "Always" for the "Actively Prevent Duplicates" pop-up menu, and I've checked the "Transfer metadata only for songs already in iTunes". However, when I attempt to transfer the metadata for these files by selecting the appropriate songs on my iPod and clicking the "Selected to iTunes" toolbar button, I get an error message for each song.
Usually the error message says "-30720: Invalid date and time 2008-04-03 00:59." or something like that. I'm not sure what date and time it's referring to, though -- maybe the last played or last skipped time, because it's not the current date, and it's too recent to have been the date added. One song has the error "-10006: iTunes got an error: Can't set library playlist id 5260 of source id 39 to «class" and the rest of the message gets truncated by the Transfer Errors window.
Other relevant info: I run my system under the Italian localization (although PodWorks does not have one so it defaults to English, my next setting). I also have a non-standard medium-length time format set up in the International preference pane -- my time format includes the date via a trick (see http://www.macosxhints.com/article.ph... ), so maybe this is causing problems.
Any ideas on how to fix this problem? I want to transfer my metadata to my library before I set my iPod to sync with this new library.
In PodWorks 2.9.3's preferences, I've selected "Always" for the "Actively Prevent Duplicates" pop-up menu, and I've checked the "Transfer metadata only for songs already in iTunes". However, when I attempt to transfer the metadata for these files by selecting the appropriate songs on my iPod and clicking the "Selected to iTunes" toolbar button, I get an error message for each song.
Usually the error message says "-30720: Invalid date and time 2008-04-03 00:59." or something like that. I'm not sure what date and time it's referring to, though -- maybe the last played or last skipped time, because it's not the current date, and it's too recent to have been the date added. One song has the error "-10006: iTunes got an error: Can't set library playlist id 5260 of source id 39 to «class" and the rest of the message gets truncated by the Transfer Errors window.
Other relevant info: I run my system under the Italian localization (although PodWorks does not have one so it defaults to English, my next setting). I also have a non-standard medium-length time format set up in the International preference pane -- my time format includes the date via a trick (see http://www.macosxhints.com/article.ph... ), so maybe this is causing problems.
Any ideas on how to fix this problem? I want to transfer my metadata to my library before I set my iPod to sync with this new library.
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Interesting--that's definitely a new one to me. Yeah, I suspect this has something to do with the fact that I'm using the date format as specified in the International Preferences and AppleScript doesn't like the way you have it set up. I guess I'll have to look into not using the format from the preferences, but rather always coercing the date into a form that AppleScript doesn't choke on.
-
Inappropriate?Yep, it was the formats in the International pane. I changed it from "Custom" to the standard "United States" set of formats, and PodWorks didn't complain after that. Perhaps PodWorks should first try to get the date into a standard format, and once it does that, *then* convert it to the localized format as per the International preferences?
I’m happy to find a workaround.
-
Inappropriate?Yeah, the next version will definitely address this. Thanks for bringing it to my attention...
Loading Profile...



EMPLOYEE