After successfully installing Izotope IDrum 1.7, I got the following error dialog box after attempting to select Drum Kits - IDrum Default from the Track Info panel in GarageBand.

"This Apple Loops File was created using an effect or instrument which is not available. The plugin Idrum is not available"

I did open a ticket with Izotope support, and they told me to delete a file 'com.apple.audiounits.cache' which didn't exist on my machine. Now they want me to upgrade the OS along with GB and ILife, uninstall Idrum, manually uninstall the files their uninstall program didn't take care of, and then reinstall IDrum.

I was wondering if anyone here had experienced a similar problem, and found a simpler solution! I'd appreciate any help anyone has to offer.

I installed IDrum from the CD - I didn't download it. There was one choice that pertained to Logic which I have heard of, so I thought that generally the rest of the choices pertained to sequencer brands as well (VST = Verygood Sequencer Technology? ). Since GarageBand was not one of the choices, I picked standalone, the only other choice which wasn't some kind of buzzword acronym.

I've since googled VST, and audiounits and understand that they are competing technologies that enable integration of software packages such as IDrum with sequencers. However, I don't think that a software company such as Izotope should assume this knowledge on the part of their customer especially since IDrum can be integrated with an entry level product such as GarageBand. If Izotope had made some more thoughtful choices on how they presented the installation options, like mapping the choices to sequencer brands, or including a short description of each option on the install screen, pain could have been obviated. Hopefully Izotope monitors forums like this one and uses the feedback to improve their products.

I completely agree with your assertion that I need to be schooled. However, this doesn't preclude a software company sucb as Izotope having clear documentation on installation choices.

Picture installing a word processor which asks you if you want the installation to support Ole32 automation. WTF right? How about if it asked you whether or not you wanted to insert images or spreadsheets in your documents? A lot clearer right?

As a developer myself for the past 18 years who has had the dubious pleasure of writing end user docs on a number of occasions I've had my feet held to the fire for the same kind of buzzword laden choices that I'm objecting to here - and I did get better at it, and the users were happier.

Until companies are taken to task for poor docs, the same problems will occur in the future.