Comments on: Having trouble with Lostify’s iTunes integration?

By: Josh

Josh — Thu, 06 Mar 2008 23:36:35 +0000

Metafreshen is a great little script. I spent a ton of time using Lostify to add my tags and long descriptions how ever due to running out of drive space I migrated a bunch of files to a larger drive and I was dismayed when my long descriptions were missing. Metafreshen saved me a ton of time by not having to rerun Lostify to fix something that was already there.

By: Mark

Mark — Thu, 14 Feb 2008 20:03:24 +0000

It’d like to request a feature which trashes the created file after it is added to iTunes. I have set iTunes so that it automatically manages my library, i.e. it copies all files which are added to the iTunes Music folder. This means that the files Lostify just created can be trashed after being added to iTunes.

By: NONfinis

NONfinis — Thu, 14 Feb 2008 14:41:03 +0000

Roughly speaking, I have about 6200 items in my library (music+tv shows+movies).

One thing I noticed, which may or may not be of any use: the problem with lostify not working in iTunes (ie having that error pop up) seems to always happen with newly added items to the library. Occasionally it seems to work with items that I have added but haven’t gotten around to tagging until I’ve added more things into the library (making those first added things no longer the most recently added item).

I hope that garbled mess of words made sense.

- Jeff/NONfinis

By: lowell

lowell — Tue, 12 Feb 2008 06:50:48 +0000

NONfinis… if you don’t mind my asking, approximately how many items do you have in your iTunes library?

By: lowell

lowell — Tue, 12 Feb 2008 06:48:24 +0000

has… thanks for the great information! It hadn’t occurred to me that the database IDs might be overrunning a 30-bit integer. Can that really be true? Of course I have no idea how iTunes assigns these IDs internally, but perhaps some user actions (consolidating or moving your library, etc.) could conceivably cause iTunes to reassign database IDs in such a way that the numbers could climb a lot bigger than the number of items in your library. Me personally, I don’t think I’ve seen any database IDs in my library over 6 digits (which would fit in 20 bits). Do database IDs for some users really exceed 1,073,741,842?

Another reason this never occurred to me was that the database IDs typically reported in the error messages (can’t get track 1 of library playlist 1 whose database ID = xxxxx) were usually just 4- or 5-digit numbers, nothing even close to any limits. Maybe these numbers were actually incorrect, the result of some truncation that happened internally when I coerced a really large value into an AppleScript integer? Never thought of that.

At any rate, I’ve been doing some performance testing on the idea of using the newer “Persistent ID” instead of the “Database ID” for these lookups. On my machine (2.4 GHz Core 2 Duo w/2GB RAM) and with my iTunes database (7000+ items), lookups by Database ID via AppleScript take about 0.11 seconds average. Lookups by Persistent ID appear to take about 60% longer — on average about 0.18 seconds. So not quite as quick, but still better than most other ways of looking up tracks via AppleScript. I guess I’ll try using the Persistent ID in the next release. Thanks again, has.

By: NONfinis

NONfinis — Tue, 12 Feb 2008 05:17:08 +0000

Hi! Thanks again for looking into this! I was one of the ones that mentioned this problem awhile back (I’ve been busy and unable to respond or post more about it - sorry!)

I thought the problem was solved when I installed Leopard, but sadly it came back. Sometimes it comes and goes, and seems to be whenever I want to Lostify something newly added to iTunes.

If there’s any info I can add that would help, please let me know (though I’m a total newb at much of this.)

And again, thanks for a truly wonderful app!

By: has

has — Mon, 11 Feb 2008 23:15:53 +0000

“these users begin getting errors like “Can’t get track 1 of library playlist 1 whose database ID of it = xxxxx”.”

Older versions of iTunes used a 64-bit integer for database IDs. This isn’t a problem for languages such as Python and Ruby that can represent integers of any size. AppleScript integers are limited to 30-bit, however, and anything larger gets coerced to an AppleScript real, which only has 50-bit precision so there’s often some loss of accuracy that renders numerical database IDs completely useless.

Solutions:

1. Make sure you’re using iTunes 7.5 or later. iTunes 7.5+ represents database IDs as hex strings which AppleScript can’t screw up.

2. Switch to Python/Ruby/ObjC and appscript (see my sig), which provides non-lossy mappings between native and Apple event integer types.

3. Rewrite your AppleScript so that it doesn’t use the ‘database ID’ property.

HTH

has
–
http://appscript.sourceforge.net
http://rb-appscript.rubyforge.org