What JHymn is meant to do

Let me start with what JHymn is not meant to do. JHymn is not meant to aid music piracy. I personally love shopping for music at the iTunes Music Store (I have nearly 900 legally-purchased songs so far, at the time of this writing), I'm happy to pay for the music I get, and I wish Apple all the success in the world at making legal music downloads a viable, profitable business.

I don't much care, however, for Digital Rights Management (DRM). I understand why it's there, and I know Apple never would have gotten the music industry to cooperate without it, but that doesn't mean I have to like DRM or having my fair-use rights restricted.

I have a non-Apple network music player attached to my stereo. With DRM, I can't play my music on my stereo with my existing equipment. I like to play my music on my computer at work, but I don't like the idea of having to "authorize" a computer that's not completely under my control. I like to edit my music sometimes — trimming intros, adding fade-ins and fade-outs, splicing consecutive tracks together to eliminate between-track dropouts, etc. As of iTunes 4.5 and QuickTime 6.5.1, however, my favorite audio editing software would no longer open my iTunes purchases for editing. That really annoyed me. I couldn't burn iTMS purchases music using Toast anymore, either. That annoyed me even more.

Thus my interest in the Hymn project began. I was happy to find the Hymn solution when it came out — and damned impressed with the code-cracking skills that went into the solution, skills I certainly don't possess — but being a more Graphics User Interface-oriented person, I wanted something slicker looking, easier to use, and more automated. When iTunes 4.6 came out — and not only refused to play my previously "hymnified" songs, but started deleting them from my iPod, as well — I also gained an interest in better understanding the process of removing DRM, and in understanding what made a file identifiable as having once been protected by DRM, even after the DRM had been removed.

Here's the ideal experience that I'd like JHymn to provide: You buy some new music through iTunes, you run JHymn — hopefully do no more than click one or two buttons — and when you quit JHymn and go back to iTunes, all of your DRM-protected music has been seamlessly replaced by unlocked, DRM-free music with the same sound quality as your original purchases, music which is virtually indistinguishable from music that you rip from your own CDs. If you had set up playlists which had included protected songs, the unprotected versions of those songs would now be in those same playlists, in the same play order.

JHymn can get pretty close to that ideal experience now, even for Windows users as of JHymn version 0.5. (Some issues were much easier to solve on Mac OS X, for technical reasons.) Hopefully time, contributions from other users, and even unintended help from Apple (like some much-needed improvements in the iTunes COM SDK) will lead to even better JHymn functionality and performance.

Downloads

JHymn 0.9.2, Mac OS X version	Click here to download the 656K .zip file
JHymn 0.9.2, Windows version	Click here to download the 628K .zip file
Source code, with Mac OS X Xcode project,    Mac and Windows build scripts	Click here to download the 1064K .zip file
Java downloads*	Click here to go to Sun's web site.
*Windows users especially might need to download Java to run JHymn.

The "Big Secret" you need to know

For various philosophical and quasi-legal reasons, JHymn, right "out of the box" so to speak, does not strip your Apple ID or the copyright information contained within the files from which DRM is removed. Leaving this information in your files, however, is a dead giveaway that those files once lived a life as DRM-protected files. We know after what happened when iTunes 4.6 came out that such vulnerabilities can, and probably will, be exploited.

You have to make the decision yourself, as the user of JHymn, to remove either or both of these items by going into JHymn's Preference settings (In the JHymn menu on OS X, in the Edit menu on Windows) and telling JHymn to delete the Unwanted atoms associated with these items. Doing so looks something like this:

Basic instructions

Note: For convenience, I'm using the terms locked and unlocked to mean protected by DRM and free from DRM, respectively. This usage should not be confused with your computer's file system concept of locked (read-only) and unlocked (read/write) files.

1. These are the files and folders containing files that you want JHymn to unlock and/or scrub. You can use the Add files/folders button, or simply drag-and-drop files and folders.

2. "Recursively" is a word that's probably more technical than should be used casually with a non-technical user, but it takes up a whole lot less room on the display than saying "If there are folders inside of another folder, look inside those folders for files too. And if there are folders inside those folders, look there too, etc. etc." If you turn this check box off, only files immediately inside the folders listed will be examined by JHymn. Folders within folders will be ignored.

3. These are the file types that JHymn will examine — .m4p (AAC files with DRM), .m4b (audiobooks, with or without DRM), and .m4a (standard AAC files).

Normally you only need to examine protected files — .m4p and .m4b. The only reason to have JHymn look at .m4a files is for what I like to call "scrubbing", by which I mean cleaning up any residual traces that a file was once a DRM-protected file (see The "Big Secret" for more).

JHymn will run faster with .m4a unchecked, since it won't have to spend time looking at files you've already unlocked, but it might be a good idea to check the .m4a option on the first time you run JHymn, and also when new versions of JHymn come out since scrubbing techniques may need to be improved over time.

4. Purchases from the iTunes Music Store come as .m4p files (aside from audiobooks — we'll get to that subject later). Typically you'll want to remove the DRM and turn these files into unlocked .m4a files.

5. When Save to a different folder is unchecked, new unlocked files are saved right where the original locked files were found. Already-unlocked files that need to be scrubbed are simply modified in place.

When Save to a different folder is checked, new unlocked files and freshly-scrubbed files are saved to whichever drive or folder you specify in section 11.

If you uncheck Replace old files, JHymn will preserve any already-existing files in the target folder by changing the names of new files as needed. For example, if Song.m4a already exists in your target folder, and song Song.m4a is about the be rewritten, a new file named Song_copy_01.m4a will be created.

6. Audiobooks, with their .m4b file extension, need to be handled as a special case. If you unlock an .m4b file and change the extension to .m4a, it will be quite playable as an unprotected audio file, but special features like bookmarks and variable-speed playback won't work. If you leave the extension as .m4b, you get full audiobook features, but iTunes still describes each such file as a "Protected AAC audio file", and JHymn has to do a little more work when it looks at .m4b files — slowing things down a little for you bit, the patiently waiting user — because it needs to read a bit of the beginning of each file before it can tell if it's unlocked yet or not.

I personally recommend leaving .m4b files with their .m4b extension, but the choice to change the extension is there if you want it.

7. The purpose of the Skip already-unlocked and scrubbed files is to make JHymn run faster by not re-converting and re-scrubbing files that have already been processed once before. Probably the only good reason to ever switch this option off is if you're running a newer version of JHymn and there's a good reason to force JHymn to re-do what an earlier version of JHymn had done.

If you've got this option turned on you might, however, find yourself asking one day, "Hey? Why is JHymn redoing all of those file that have already been unlocked and scrubbed? I thought it was supposed to skip them!" Well, this can happen for a couple of reasons:

One is that what's considered "scrubbed" can change. Both your own Preference settings and new versions of JHymn can re-define what is considered scrubbed and what isn't. Something that had been scrubbed once before might need to be scrubbed again.

Another thing that can make the difference is the Save to a different folder option. When saving to a different folder, two things need to be true for JHymn to skip reprocessing a file: The target file must be judged as being fully scrubbed, and the original file and the target file must have the same file modification dates. When JHymn does decide to process or reprocess particular files then, starting with JHymn 0.4.x, JHymn will set the modification date of any newly-unlocked and/or newly scrubbed file to match its original. Subsequently, as long as you don't change the original file (by editing song info or updating artwork, for instance) JHymn will know to skip over reprocessing these files the next time you run JHymn.

8. Use this feature to convert AAC files, even locked .m4p and .m4b as well as unlocked .m4a files, directly into MP3 (.mp3) or WAV (.wav) files.

If you wish to adjust MP3 sound quality and bit rate settings, go into JHymn's Preferences settings. There are separate settings for .m4b audiobooks and all other AAC files. While the range of sound quality settings available from the Preferences pop-up menus should serve most users needs, you can also enter your own custom settings, using LAME's command line switches. Use custom settings with caution: JHymn does no validity checking for these settings, and bad settings could cause LAME to fail in unpredictable ways.

Note on MP3 encoding speed: JHymn defaults to using the LAME "standard" preset. The alternative preset "fast standard" runs nearly twice as fast as "standard", at the expense of possibly generating slightly larger files and/or providing slightly diminished sound quality. You'll have to let your own ears and your own patience battle it out over which of these two settings — or which among the many other possible LAME settings — best suits your needs.

JHymn extracts song information such as song title, album name, artist, etc., from AAC files, and creates MP3 files with appropriate ID3 tags to convey this information. ID3v1.1 tags are created with their limited information in plain text (unaccented Roman letters, digits, and simple English punctuation — basic ASCII), as well as much more complete ID3v2.2 tags, providing the following information, using full Unicode character encoding as needed: title, artist, composer, album title, release year, comment, track number, track count, disc number, disc count, group, full arbitrary genre, compilation flag (whether the song belongs to a compilation or not), unsynchronized lyrics, tempo (BPM), and artwork (as JPG or PNG).

When converting to WAV format, it is important to note that WAV files carry no tag information. If you have Save to a different folder unchecked, and Update iTunes Music Library checked, your WAV files will have most tag information (artwork and lyrics being the main exceptions) created via iTunes' own tagging facilities, but this information then lives within iTunes database only and does not automatically travel with your WAV files if you move them elsewhere or use software other than iTunes to convert your WAV files to different formats.

9. This option gives you the ability to shorten file names (as well as the names of artist and album folders that may be created to store your files) and to simplify the character set used for folder and file names so that the resulting files will have the greatest cross-platform compatibility. Simplify file names is only applicable when the Save to a different folder option is checked on.

10. It's always a good idea to make sure you have back-up copies of the original files you purchase from the iTunes Music Store. The goal of JHymn is to create unlocked files which are indistinguishable from files that you might rip from your own CDs, but this goal cannot be guaranteed. Apple may have ways of marking files as store purchases that no one contributing to hymn-project.org has yet discovered, and any such undiscovered markers could mean, although I hope it is unlikely, that files which you once thought were completely freed from DRM suddenly become unplayable. Such problems have already occurred once, when iTunes 4.6 was released.

The first back-up option, Original locked & .xml, backs up any locked .m4p and .m4b files that get unlocked, plus a pre-update copy of the XML-formatted version of your iTunes Music Library in the event that an update is needed.

The second back-up option, All modified files, adds to the first option any unlocked but scrubbed files, backing up pre-scrubbed copies. This option might be especially useful if you're using JHymn to strip away cover art (something I'll get around to documenting later) yet want to make sure that you can recover the artwork later.

As long as you've chosen to make back-ups, the Delete original locked files option is useful not only to save disk space, but to avoid problems where iTunes ignores your newly-unlocked files in favor of your old DRM-protected files. Delete original locked files must be checked on in order to use the Update iTunes Music Library option.

11. This field changes depending on whether Save to a different folder is checked or unchecked. When unchecked, this field is where you set up a back-up folder. When checked, this is the "different folder" you'll be saving to. You can type in a folder path, drag-and-drop a folder into this field, or use the Choose button to select a folder.

12. Selecting this option lets iTunes know that locked files have been replaced by unlocked files with changed file extensions. This way, your iTunes Library and your playlists will be the same as they were before running JHymn, except that unlocked files will have replaced DRM-protected files. Without using this option (especially on Windows), iTunes will often not know where the newly-created unlocked files are, or where your old locked files are either, but will instead present you with broken tracks that can't be played.

You can only use the Update iTunes Music Library option if Save to a different folder is unchecked, and Delete original locked files is checked on. You may also need to check your Preferences in case JHymn needs help locating your iTunes Music Library files.

The following limitations to the Library update process should be noted:

• iTunes will list all .m4b files as "Protected AAC audio file", whether they are truly protected or not. JHymn's Library update procedure will not change this. (See item 6.)
• Mac OS version: Unlocked files may be briefly listed as "Protected AAC audio file" until you've played them, done a "Get Info" on them, or otherwise nudged iTunes into refreshing a little bit of outdated display information.
• Windows version: User-configured start and finish times for individual tracks will not be copied from old locked files to their corresponding new unlocked files.
• Windows version: Some unusual playlists (probably not very useable or practical ones) will not be updated, such as playlists combining both URL streams and song files.

13. Files you rip from your own CDs include information about the encoder used to create the files. Files from the iTunes Music Store lack this information. In order to make de-DRMed and scrubbed files look more like home-ripped files, the If encoder isn't specified option allows you to add an extra touch of fake authenticity.

14. The Add custom signature atom option gives you a way to mark your files as your own, both to discourage piracy and to give you a way, should the need arise, to figure out which of your files in your music collection had once been DRM-protected.

To create a custom signature atom, you need to set up your signature in JHymn's Preferences. While the signature text can be pretty much anything you want it to be, care must be taken in choosing your signature atom or you could corrupt your files and render them unplayable.

If that last bit scares you, then you probably shouldn't try to use a custom signature. If, however, you feel like boldly pressing onward, here are some things to keep in mind:

Atoms are four character codes. You can use any four characters, but it's best to stick with unaccented Roman letters, digits, and simple English punctuation (basic ASCII characters). For your own atom, remember that the goal is to come up with a four-character code that's very unlikely to be something Apple would want to use for its own purposes. Apple, for instance, reserves all all-lowercase atoms, so don't use all lowercase yourself. I'd recommend a mix of upper- and lowercase characters, and a bit of odd random punctuation is also a good idea. If I weren't using up these atom names by using them as examples here, things like 'BoB#' and 'wHy?' and 'bL1p' would probably be very good ideas.

If you're a technically-minded user using a Mac, or on Windows and have something like Cygwin installed, you could locate your custom-signed files from a command prompt with something like this:

grep -r "MyID.\{4\}data.\{8\}My signature" .

15. For brevity, this button simply says Convert, but if having a button the width of the entire JHymn main window weren't a problem, it might very well say "Convert, Scrub, and Update the iTunes Library as Needed". Click here when you're ready to have JHymn get to work converting, unlocking and scrubbing your files. If you're going to be updating your iTunes Library, you'll need to quit iTunes before you can get started.

16. Click Stop to interrupt the conversion and scrubbing process. You may be asked to allow a Library Update to proceed for files that had already been converted before you interrupted the process.

17. Progress information and status messages are displayed here, including the countdown to any pending automatic FairKeys deauthorizations.

What's new in JHymn 0.9.2

• Fixed a compatiblity problem in the FairKeys feature caused by a recent Music Store change. (JHymn is still not compatible with Music Store accounts with which purchases have been made using iTunes 6, however.)
• Improved compatibility with non-English versions of Windows and with file paths on Windows which include non-English characters.

What's new in JHymn 0.9.1

• Fixed a Windows-only bug which could cause problems dealing with files on networked drives.

What's new in JHymn 0.9

• Improved MP3 ID3 tagging, including transfer of cover art and lyrics from AAC files to MP3 files.
• New option to convert songs to WAV format.
• Fixed a problem with limited Windows user accounts (non-admin accounts) which sometimes caused automatic iTunes Library updating to fail.
• Made sure JHymn on Windows didn't get lost behind an iTunes window while waiting unseen for users to click "Continue".
• Reduced the start-up memory demands made by JHymn.

What's new in JHymn 0.8.5

• Improved scrubbing. (Please see the JHymn FAQ for more information about what "scrubbing" is, why you might want to re-scrub old files you've already unlocked with JHymn, and how.)
• Added Japan to built-in store front list.

What's new in JHymn 0.8.4

• Added support for HTTP proxies.
• Added a safety feature that lets you make sure iTunes has started up and settled down before JHymn's update of the iTunes Library begins. You can clear away any dialogs iTunes might display, let it finish any automated updates, and then click the JHymn "Continue" button to proceed with a Library update.
• JHymn now will recognize and use by default the new file name, as of iTunes 4.9, for the iTunes binary database.
• Users are now warned that a forced Library update will cause podcast subscriptions to be lost. (Already-downloaded podcast files remain, found in a ordinary playlist called "Podcasts", but no new podcasts will be automatically download without first re-subscribing.)

What's new in JHymn 0.8.3

• Added new country choices for FairKeys Music Store log-in.
• Added an option for updating available country choices without having to update your version of JHymn itself. (Updates are provided via the hymn-project web site, and may lag a few days behind Apple's introduction of support for new countries.)
• Fixed a bug reading certain AAC files which could result in an "oversized atom" error, preventing JHymn from unlocking such files.

What's new in JHymn 0.8.2

• Fixed a bug which could prevent JHymn from exiting properly when trying to quit the application.
• Fixed a bug which could corrupt audiobooks, and a related bug which prevented reporting of the error of trying to convert such a corrupted file to MP3.
• Keys are now converted and saved in the same format which had been used prior to JHymn 0.8, compatible with earlier versions of JHymn and other related tools.
• Updated the build scripts to ensure Java 1.4.x compatibility.

What's new in JHymn 0.8.1

• Fixed a couple of bugs related to the Preferences dialog, which might make it badly formatted, or might cause it not to open at all.
• Rebuilt the Windows version to be compatible with Java 1.4.x.

What's new in JHymn 0.8

• Now compatible with iTunes 4.7 protocols for downloading keys.
• Optional automatic notification of new JHymn versions, as well as for other announcements which might affect JHymn use.
• Improved iPod-based key retrieval. (Requires iPod software 2004-07-15 or earlier, and a not-too-recent model iPod which will accept that software.)
• Password info hidden when password-bearing URLs are shown in error dialogs and the log window.
• Command-line build scripts for both Mac and Windows.
• JHymn can now be built completely using only OS-provided tools and freeware.
• GPL/LGPL license info available through Help menu.
• A fix for a (fortunately rare) bug in automatic library updating which affected a couple of Windows users creating MP3 files in a bad way.

What's new in JHymn 0.7.5

• Fixed a bug which caused JHymn to fail to start converting files after trying to read files from an inaccessible folder.
• FairKeys functions now display HTTP response codes when failures happen, which I'm hoping will relieve at least some of the anxiety users often express when their attempts to access the iTunes Music Store fail, typically — as the new display of response codes should help illustrate — from simple matters such as Apple's servers being too busy to respond.

What's new in JHymn 0.7.4

• JHymn can now read AAC files with bad date tags without throwing an exception.
• JHymn will now keep going, after throwing an exception on an individual difficult file, with the rest of a multi-file conversion task.
• Open as text... will now display any exception thrown while attempting to read and display a file.

What's new in JHymn 0.7.3

• Fixed a bug which I thought had been fixed in version 0.7.1, dealing with an undefined "played date" causing Library updates to fail in the Mac version of JHymn.
• Added back-up of the binary iTunes database to back-up of the XML version.

What's new in JHymn 0.7.2

• Fixed a bug which prevented the Windows version from converting some files to MP3 when double-quote characters appeared within ID3 tag data.
• Can now read and process files with excess trailing data, files which used to be skipped over by JHymn for being badly formatted.
• Improved scrubbing — removal of an identifying mark found within JPEG cover art.
• Fixed a bug that could cause unnecessary Library updates after scrubbing .m4a files, and even possibly doubled-up entries in the Library for the same files.
• Open as text... will now display atoms with odd names as eight-digit hexadecimal numbers rather than four-character codes.
• 8-digit hexadecimal atom names can now be used when specifying unwanted atoms.
• AOL IDs, as were Apple IDs before, are now preserved from scrubbing unless user preferences indicate that (apID) should be scrubbed. (Previously, AOL IDs still survived initial DRM-removal, but they would most likely have been deleted by any subsequent scrubbing.)
• Eliminated the need for JHymn to start iTunes, and then quickly quit iTunes, at the start of the conversion process when Library updating has been selected.

What's new in JHymn 0.7.1

• Fixed a bug caused by a strange situation one user had where a file had a play count greater than zero, yet no "played date" (the time the last play occurred) was defined. This inconsistent state caused JHymn's Library update to fail.
• Fixed a bug in the Windows version that might cause playlists to be updated without preserving playlist order, even for playlists with 100 or fewer tracks.
• Added a warning to eject your iPod before performing an automatic iTunes Library update — doing so will help you avoid the annoyance of iTunes starting an iPod update while JHymn is trying to start and quit iTunes for its own reasons.

What's new in JHymn 0.7

• More robust AAC parsing to help with recent (Jan-Feb 2005) iTMS downloads which have previously been unreadable by either JHymn or Hymn, and some scrubbing improvements to tidy up the mess inside these oddly formatted files.
• Mac version of JHymn now uses scripted updating of the iTunes Library to create a more thorough break by unlocked files from their locked originals — this can solve some of the problems seen with the release of iTunes 4.7.1 and songs being unplayable and/or deleted from iPods.
• Incorporated some features from the new Mac scripted Library update into the Windows version, including, for speed, a size threshold for how playlists are rebuilt.
• New Force iTunes to rebuild its Library feature — useful, among other things, for solving some iTunes 4.7.1-related problems.
• Improved MP3 functionality — conversion to MP3 is no longer restricted to the "Save to a different folder" mode.
• XML playlists, including the XML iTunes Music Library itself, can be added to the files/folders list, causing each file in such playlists to be inspected just as the contents of a folder would be.
• The Mac version has been updated with FAAD 2.1 beta, which, among other improvements, allows .m4b audiobooks to be converted to MP3. Had used FAAD 2.0.
• The Windows version has been updated with LAME 3.96.1. Had been 3.96.
• Error handling has been improved, including fixing a bug where unreadable AAC files were skipped over without any errors being reported.
• It's no longer necessary to use the Delete original locked files option in order to have the option of updating the iTunes Library.
• Some legacy file extension choices (.mp4, .aac) have been removed.
• Interrupting a Library update by clicking Stop is no longer permitted, as this could leave the iTunes Library in a bad state.
• Fixed a bug where, in the Windows version, the conversion process would keep running in the background when it should be paused, waiting for a user response when the user has interrupted conversion and is prompted about continuing with a Library update or not.

What's new in JHymn 0.6.3:

• Fixed a bug where part of JHymn could hang after an attempt to display certain log messages.
• The Naive Trust Manager is now automatically activated for users running Java 1.4.0, rather than 1.4.1 or later. Java 1.4.0's certificate store is insufficient for validating the Music Store connection. For such users, updating to the latest Java release is recommended.

What's new in JHymn 0.6.2:

• Fixed a bug in the Mac version which caused MP3 conversion to fail unless you'd previously installed FAAD2 on your computer.
• Fixed a potential problem in Open as text... where possibly a duration value might have been formatted to say something like 0:03:60.000 instead of 0:04:00.000.

What's new in JHymn 0.6.1:

• .m4a files with low sample rates (24 kHz or less) or low bit rates (32 kbps or less) will be treated just like .m4b audiobooks as far as the quality settings used for MP3 conversion.
• Some minor GUI tweaking, including a visual cue linking the Convert all file types to .mp3 option to the Save to a different folder option.
• Elimination of a superfluous error message that could occur when a user interrupts MP3 conversion.
• Better progress feedback during the AAC→WAV phase of MP3 conversion on Windows.
• A little bit of README documentation added to the source code, including some notes on how the Windows version gets built, and the minor changes that were made to the FAAD2 source code for Windows.
• A possible fix for this obscure incompatibility problem on Windows.
• Open as text... provides more information about viewed files, such as bit rates and duration.

What's new in JHymn 0.6:

• Option for converting AAC files, including protected files, directly into MP3 files. FAAD2 2.1 and LAME 3.96 are built into JHymn and used for this purpose. ID3 tags are supported.
• Fixed some strangeness in text selection behavior.
• Small improvements to error logging and reporting.

What's new in JHymn 0.5:

• Automatic iTunes Library updating for Windows users.
• New JHymn log window — shows details of conversion, Library update, and FairKeys activities. This feature will be especially useful to me when any of you run into problems you need to report.
• Better menu support for AAC view-as-text windows (Open as text...).
• On Windows, JHymn windows now have a custom title bar icon, rather than the default Java coffee cup.
• Better interface font consistency on Windows.
• Update iTunes Music Library option now only works when Delete original locked files is checked on.
• JHymn can tell if iTunes is running and when necessary warn users to quit iTunes before JHymn proceeds.
• New warning messages to caution users against FairKeys overuse.
• Create file to import for updating your Library option has been removed — this only existed to make up for a lack of automatic Library updating for Windows, which is now no longer a problem.
• The file count beneath the progress bar now only counts audio files. Including the iTunes Library file in the count as I did before seemed to have caused a lot of confusion.
• Other small enhancements and bug fixes.

What's new in JHymn 0.4.4:

• Fixed a bug related to correctly reading audiobooks.

What's new in JHymn 0.4.3:

• Fixed a bug introduced in 0.4.2 which caused problems when re-writing AAC files which contained unknown data when first read in.

What's new in JHymn 0.4.2:

• Added the "Naive Trust Manager" feature to help overcome log-in problems caused by having an old Java installation.
• Open as text windows no longer misleadingly editable.
• Color coding and error text added to Open as text windows.
• Made a step towards improving the robustness of reading AAC files (but accidentally introduced a potential problem at the same time).
• When determining if a file can be skipped over as already processed in Save to a different folder mode, the "cleanliness" of any pre-existing target will be considered.
• Changed the AES decryption used by FairKeys so that it would work for users with Java 1.4.1 or 1.4.0.

What's new in JHymn 0.4.1:

• Replaced the "Immediately deauthorize" option with an option for delayed automatic deauthorization.

What's new in JHymn 0.4:

• FairKeys key retrieval: No iPod needed, just log into the music store and get the keys you need to free your music.
• Assistance for Windows users in restoring their iTunes Library and playlists with newly-unlocked .m4a files replacing old protected .m4p files. Mac users don't need this assistance. By sheer luck (and not just because I'm a Mac fan!) there's a simple trick, already implemented, that helps Mac users sync their libraries and playlists.
• The built-in link to this help page.
• A new option to replace old files, and to ignore already-converted files, when using the Save to a different folder option.
• Enhanced "scrubbing" to improve how well unlocked files look like home-ripped files.
• The Cancel button now works properly in the Preferences dialog.

JHymn 0.3-0.3.1:

• First versions that run on Windows.
• First distributions of ready-to-run application binaries.

JHymn 0.1-0.2:

• Early source-code-only, Mac only versions.