New Apple Lust Objects

:(

for burning to cd, i think you have to look elsewhere, but this works for playing "live"

But when you're using it on its native machine, it's a whole different deal. On Windows, its only advantages are the way it organizes the music and edits ID3 tags. Other than that, it eats memory and processor by using QuickTime (yuck!) and works spottily with some PC hardware configurations (in my experience). But on a Mac, it's so seamless. You can't imagine using anything else.

xxpost:
I remember using macamp, which had a similarly small footprint.

Or were you asking a different question?

As for winamp 5, the way I use winamp it was very slightly slower. Maybe I'll try it again and try to get my head around the expanded features.

fwiw i found it slow at first too, i fixed that by changing back to the original skin.

xxxpost:
excellent, I'll try it with the old skin!

Or better yet, snag a copy of ssX. I was using nicotine for awhile and made the switch to ssX and haven't looked back. It's significantly stabler than nicotine and doesn't need X11.

Spencer, I can't for the life of me remember what the name of the program was, but Jen was recently messing with the trial version of a "media library" database/front end that was able to hit an online database similar to the CDDB to grab all data on a CD or DVD based on the barcode. It was compatible with barcode readers as well as codes manually entered via the keyboard.

For some reason she decided against paying for and using the program (I think it didn't have enough configurable fields to store her library with all the data she wanted to store), but we agreed that feature was pretty slick. She's on vacation at the moment, but if I catch her online or remember next time I talk to her on the phone I'll see if I can get the product name for you.

Oh, it was a Mac-only app...

Preference---->Burning----->Gap between songs: none doesn't seem to do the trick, still a little blip there...

Interesting little fact, When Apple first ported quicktime to windows, rather than port quicktime they ported a whole Application environment over to windows and Ran quicktime on top of it, kind of like the Mac OS equivalent of cygwin. When OS X came about they ported vast chunks of the Carbon Application environment over and later bits of cocoa (or rather reused bit os x86 openstep and bits from an x86 version of OS Xthey developed when Motorola was giving them processor trouble.

ITunes uses this environment as well and it means that apple if it so desired could port any other OS X app relatively easily if it chose to. It also makes quicktime stuff more compatible cross platform and easier to port quicktime based apps across.

Doesn't, of course, help iTunes/quicktime being rather larger than it need be.

It's not the burner, and technically it's not even iTunes. It's a side effect of the mp3 encoding/decoding process.

Best explanation I found online to save myself a bunch of typing and save ilxors who don't care a bunch of scrolling:

http://www.geocities.com/altbinariessoundsmusicclassical/mp3gaps.html

Developer is called Delicious Monster, and the app is Delicious Library.

Sadly I did remember correctly that it is Mac only.