Known Issues

Issues

Corrupted zip files: this is common among songs that were compressed using winzip that you may find on the internet. they aren't technically all corrupt, tho some may actually be. most are compressed using a method that is NOT "deflate" (a typical codec that the ZIP format employs), and there is no software on the mac (stuffit, zlib, BOMArchiveHelper) that can decompress these non-deflate zip files. but move it on over to windows and it'll unzip fine, then re-zip it using zlib, you should be good to go. that's what that "make playlist of all bad zips" is eventually gonna be, you'll be able to gather them all in one place, move to windoze, re-compress them, move them back. that feature is not complete, the smart playlist doesn't really work yet. but it will!

Glitchy Graphics: When you rip, some graphics come out glitchy. I'm sure you've seen what it looks like, when all the words don't erase and they pile up into muck you can't read? This is due to the error correction codec not being invoked when reading. Funny thing is, the (reed - solomon) codec is BUILT INTO THE HARDWARE OF THE DRIVE. Potential culprits: 1) Apple, for not providing the a driver that utilizes the hardware's potential, or 2) due to kJams not having a debugged and working "reed - solomon codec" in software, 3) other programs doing poor encoding (see "Burning"), or due to excessive dust and scratches.

Burning: well, bad news from apple is that CDG rip/burning is not *entirely* built into Tiger. They did "allow burning", as they promissed, (using the new "bin/cue" API), but they STILL don't invoke error correction when writing. This to me is absolutely not a solution and I expect any customer of mine would feel the same. They now allow burning in Tiger, (of CDG's) but without error correction, the results can be quite poor (see Glitchy Graphics).

Name Parsing: Read this so you know what I'm talking about. There are still bugs with that, especially around numbers. You may run into this when importing zip files, or when rebuilding your (previously working) library.

Reward

$1,000 Bounty! If you know anybody that knows galois field math or reed-solomon error correction, (or can write a "kext" for me and hand me a home rolled API for rip/burn (specifically I need a C API i can call from user space, written in objective C, that uses the IOKit API from kernal space, I can even help fill in the burning code)), I'll offer a $1000 bounty! Either help me debug my software RS codec, or help me write a kext to invoke the one built into the hardware.

Details

These are just details I want to just keep track of. Pretty much the same thing as the "Future" page, but much more finely grained, programmer oriented stuff.

• option to pre-cue the next song (so the audio starts instantly, skipping silence)
• volume normalize
• when deleting a file from the library, recursively go up folders, deleting them if they're empty
• enable import of playlists (so you can wipe your library.xml file, start over, and reimport all your songs in one click)
• drag and drop CDs to add them to your library.
• context menu
• bug: If I am in a program or window on top of kJams, but kJams is visible, I can click on songs in the window to highlight them, but it does not bring kJams forward, which would be the expected action.
• Use AUGraph for audio piping, stop trying to wire AU's together manually
• input from QuickTime video (to get pix of users from webcam)
• plugin audio units