Windows installer: updated AtomicParsley build

[dinkypumpkin]

I have posted an update to the AtomicParsley build used by the 
get_iplayer 4.4 for Windows installer.  This update will hopefully fix a 
problem that causes AtomicParsley to sporadically crash when tagging 
downloaded programmes.

I would recommend this update for all 4.4 users, but it is not essential 
unless you have experienced AtomicParsley crashes.  How can you tell if 
that happens?  The console output from get_iplayer will contain lines 
like this:

INFO: Command exit code 5 (raw code = 1280) [raw code may = 65280]
WARNING: Failed to tag M4A file

How to update:

1. You *must* have previously upgraded to get_iplayer 4.4 for Windows. 
The automatic update does not work with earlier versions.  If you 
upgrade to 4.4 after reading this, you will already have the latest 
AtomicParsley.

2. To update an existing installation, just run the get_iplayer 4.4 
installer.  If you don't have the copy you originally used to upgrade 
get_iplayer for Windows, you can download a fresh copy here:

http://www.infradead.org/get_iplayer_win/get_iplayer_setup_latest.exe

3. After you click through the first installer page, you should see a 
notice that an update for AtomicParsley is available to upgrade from 
0.9.4 -> 0.9.4-hg-472d5fe6fb04.  Click through to the component 
selection page and you should see AtomicParsley automatically selected 
for installation.  You may still deselect it at this point, or exit the 
installer altogether.  If you elect to proceed, the installer will 
overwrite the current version of AtomicParsley with the new version.

Note: If you elected not to install some components when you upgraded to 
4.4, you will also see update notices for those components.  You can 
deselect them in the component selection page.

DIY Windows users can find the updated AtomicParsley here:

http://bitbucket.org/jonhedgerows/atomicparsley/downloads/AtomicParsley-0.9.4-hg-472d5fe6fb04.zip

Thanks to Jon Davies for hosting the downloads.

If you have any problems with the update, please reply to this mailing 
list thread.