Addictive Drums Full Version DLL Not Recognized

clkonkol · 04-02-2011, 10:03 AM

I was using the demo for quite a while and decided to get the full version of AD a couple days ago. I deleted (uninstalled) the demo and installed the full version, restarting before that. I was careful to put the DLL under my specific plug-ins folder, etc. Now Reaper will not see it, no matter rescan, etc. Anybody have any clues to why? I'm pretty frustrated and have an e-mail in to XLN about it also. Thanks for anyone's help.

icemac · 04-03-2011, 04:40 PM

I have the same problem.
Strangely, the dll is recognised with;

www.hermannseib.com/english/vsthost.htm

but is not 'seen' by my 2 hosts.
reaper is rescanning correctly.

we'll see what support say

Solar · 04-03-2011, 04:57 PM

Can you guys try to look for it under another name by typing once inside reaper like:

XLN or addictive . For me it shows up with both name typed.

Also, try to direct inside Preferences under VST, add the link where XLN is installed as well.

Just trying to help

Ollie · 04-03-2011, 04:58 PM

Does this thread

http://forum.cockos.com/showthread.php?t=29026

help (the regedit bit in the middle of the thread)? This probably refers to a problem when the full version goes to a different place than the demo or something.

G-Sun · 04-04-2011, 12:24 AM

I had no problem, but I didn't uninstall the demo either.

clkonkol · 04-04-2011, 08:01 AM

Hey guys - thanks for the suggestions. I tried reinstalling the demo and Reaper would not recognize that either. I have done the registry edit, actually found those instruction at XLN's forum. I'm pretty stumped at this point and haven't heard anything from XLN all weekend. Guess I'll wait and see if they answer today or tomorrow.

karbomusic · 04-04-2011, 08:06 AM

Quote:

I was careful to put the DLL under my specific plug-ins folder, etc.

Have you confirmed where the DLL is actually at? I assume it is in that folder?

Karbo

junioreq · 04-04-2011, 08:15 AM

Should be in program files/vstplugins/addictive drums.dll Make sure its there and clear cache/rescan... never had a problem...Make sure your plugin folders in reaper are separated by a semi-colon..

clkonkol · 04-04-2011, 09:10 AM

I've got my VSTi's on a different HD, all in the same folder - it's where the demo was when it worked correctly. I've posted on the XLN forum just now - maybe that will generate a response. The frustrating thing is I have to get it recognized to use it and then get the computer authorization number generated. I'll let you know if (or when) I get it figured out. Thanks again.

hopi · 04-04-2011, 10:25 AM

here is how I have it:

D:\@VST Plugins\Addictive Drums

the Addictive Drums.dll is in there and actually I install all the other sets in there as well.

If you have it installed correctly, then in reaper do the clear cache - rescan thing.

clkonkol · 04-04-2011, 10:58 AM

I just did that (I've done that a few times) - my path is actually G:\VSTi Plugins and then each is under its own folder. It sees all the other ones in there, but not AD. Color me baffled.

icemac · 04-04-2011, 01:46 PM

the official response;

"... there's nothing wrong with the Addictive Drums installation (including the DLL file). I'm afraid that neither of the hosts you're using are officially supported by us. I suggest that you try the support forums for Reaper and Mixtreme instead"

karbomusic · 04-04-2011, 02:12 PM

Any chance one of the reaper ini files still has a reference to the old one causing a conflict? Is it in the main folder you mentioned or is also in an AD subfolder? I have to think it would be a good idea to make it the exact same path as the demo or a different path as the demo depending on what you have now, then rescan/clear cache.

Karbo

icemac · 04-04-2011, 03:02 PM

for me it was a clean install on a new system.
was certainly not a path / rescan issue.

the solution;

rename the 'Addictive Drums.dll', to; 'XLN.dll'

now in reaper in shows up, as 'Addictive Drums'

karbomusic · 04-04-2011, 03:59 PM

Quote:

Originally Posted by icemac

rename the 'Addictive Drums.dll', to; 'XLN.dll'

now in reaper in shows up, as 'Addictive Drums'

Thats basically the same thing to an extent... causing the host to assume it is something different based on name. So path change is/can be equivalent to a name change. Worth a try since a clean install should never be needed for something like this. I started to suggest renaming the dll anyway but that might confuse some.

Karbo

DarkStar · 04-05-2011, 12:25 AM

Have a look in your reaper-vstplugins.ini file and let us know what it says for Addictive Drums or anything from XLN Audio.

You should be able to get to the folder containing the file(s) from [Options] > select "Show Reaper resource path in Explorer/ Finder"

You will also find it helpful, in "Folder Options" (on a Windows PC):
-- to Show Hidden Folders and Files
-- to Show File extensions (or you are vulnerable even to the most simple double-extension trick to disguise malicious files)

clkonkol · 04-05-2011, 08:15 AM

DarkStar:
In the INI file named 'reaper-vstplugins.ini' there is one line refering to Addictive Drums:
Addictive_Drums.dll=009B5AC83E4ACB01

I'm assuming that's a reference to its memory location or something, being in Hex. There are no other references to AD or XLN.

Icemac, Karbo:
I could rename the DLL, but I have installed AD's DLL in the same place where the AD demo DLL was (after uninstalling it) - that's what is odd to me - I'll experiment with the renaming (I can always change it back)

DarkStar · 04-05-2011, 08:21 AM

That means that Reaper ran into a problem when scanning that plugin. That number is some sort of identifier.

You'll see that the other lines are longer, with more details. That's how they should be..

Try this:
-- make a back-up copy of the .ini file
-- delete that one line
-- start Reaper and it should scan your folders and find AD again.

Then check that the line has more details on it. If so, you should be good to go.

hopi · 04-05-2011, 08:23 AM

Quote:

Originally Posted by icemac

the official response;

"... there's nothing wrong with the Addictive Drums installation (including the DLL file). I'm afraid that neither of the hosts you're using are officially supported by us. I suggest that you try the support forums for Reaper and Mixtreme instead"

It may not be 'officially' supported but it works for me and many others...

clkonkol · 04-05-2011, 08:43 AM

DarkStar:
I did what you suggested and it still comes up simply:
Addictive_Drums.dll=009B5AC83E4ACB01
Only now it's at the top of the list and you're right, all the other VSTi's have a bit more information after the Hex number. I don't understand, but may try a complete uninstall again or is there anywhere else where there might be conflicting entries?

Hopi:
It used to work perfectly for me too (the demo) and I thought this would be a piece of cake - but really annoying instead.

DarkStar · 04-05-2011, 08:53 AM

Many people here have AD working fine in Reaper, so any problem should be solvable.

Is there a standalone version? If so, does that run OK?

Did the AD demo put anything in the Registry that is interfering with the full plugin? See tedwood's RwgEdit in the thread referenced previously.

Or do you have any other host that you can try, even a demo?

hopi · 04-05-2011, 09:17 AM

Quote:

Originally Posted by clkonkol

Hopi:
It used to work perfectly for me too (the demo) and I thought this would be a piece of cake - but really annoying instead.

I can only suggest that you uninstall using the free version of REVO uninstaller... you will have to send them an email and ask for their free portable version... they will happily provide it...

then use it to uninstall and let it run the 'moderate' clean up and follow along to remove all the parts it finds...

Are good with doing registry edits? IF so and ONLY if so, go do a search in the reg. for XLN and for Addictive and delete anything you find...

Then reboot and do a fresh install...

I have on a few occassions had to just kill the reaper vst ini file and start fresh with a clear cache and rescan.. PITA as it takes a long time for me...

I don't know why that ini file gets confused but I have seen this happen now about 3 times...

soulranger · 04-05-2011, 09:38 AM

It's been a while since I used AD but I remember it being a nightmare to get going. Not sure if this helps but I remember my problem had to do with some of the installed folders being read only. Open property boxes on all XLN or Addictive Drums folders and make sure the read only button is unchecked.

clkonkol · 04-05-2011, 10:20 AM

DarkStar and Hopi:
I've now done all that - uninstalled again, cleaned out the registry entries and restarted, ran the installer again started Reaper, cleared cache and rescanned and it's still not picking it up. The entry for it in the VSTi INI file again is the simple Hex number, not the more descriptive string. I wonder if my downloaded ZIP file from XLN is corrupted somehow, or if the extraction of it corrupted some part of the file. I think the next thing is to download it again from XLN and redo everything.

One thing about the install I don't know is - where do all the preset files and other things that are in the extracted ZIP file installed?

I don't recall being this stumped over what should be so simple. Thanks so much for your help.

clkonkol · 04-05-2011, 10:37 AM

Quote:

Originally Posted by hopi

It may not be 'officially' supported but it works for me and many others...

During my install, I let it install the program in the C:\Program Files folder (the default location). The next window suggests the place for the DLL to be under the Steinberg folder and I browse to the location I want it, on my G: drive.

After the install, all that's in the XLN\Addictive Drums folder on the C: drive are the ICO, DAT and EXE files shown in your picture. I know why my DLL file isn't there, but why aren't any of the other folders as shown in your picture. This is making me further feel the install is not working correctly. Any thoughts on that?

KevinW · 04-05-2011, 11:28 AM

What happens when you let it install with all default paths? I remember having a similar problem when I tried to specify a different path for the dll. When I just let it install in the /steinberg/ folder, all was fine.

Gloops · 04-05-2011, 03:53 PM

Salut!
J'ai eu le même problème avec la version 1.5.2
La v1.5.1 fonctionne correctement

Hello!
I had the same problem with version 1.5.2
The v1.5.1 is working properly

clkonkol · 04-06-2011, 09:13 AM

Well - I got it working and I'll tell you how. Tore over at XLN suggested uninstalling everything, deleting the DLL and not to worry about the registry. Then download the ZIP file again, extract and install. This time when I extracted from the ZIP, I checked the box in WinZip that says 'Use Folder Names'. The extracted result was completely different from the previous times when I had not checked that box. There were two folders with all the data, two install files (for Windows and Mac) and the TXT file warning to extract before installing (which I had). When I ran the Windows Installer, it took way longer than previously and like magic, everything was in the right place. I then opened Reaper, deleted the VSTi cache and rescanned, restarted Reaper, and there was AD! And yes the resource file in VSTi cache now says:

Addictive_Drums.dll=009B5AC83E4ACB01,2019639620,Ad dictive Drums (XLN Audio) (16 out)!!!VSTi

I know it may sound like a dumb little mistake, and yes I feel that way, but I hope this helps anyone who may have a similar problem.

Happy days are here again!

DarkStar · 04-06-2011, 09:33 AM

Phew, glad you're up and running.

But why use WinZip? I normally use right-click >> Extract All for a .zip file.

clkonkol · 04-06-2011, 10:51 AM

Good point - I'm still using the trial from forever ago! The system associates ZIP files with WinZip. Back inthe 'old' days (Win 98 probably) you had to have an application to unzip ZIP files and I just do the same now. Probably ought to get in the present, huh?

Thanks for your help and comments.

hopi · 04-06-2011, 11:18 AM

big suggestion WinRaR... buy it.

get rid of winzip ...uninstall it completely

when you install WinRaR be sure to have it include all it's rt clk context menu's...

live happily ever after

karbomusic · 04-06-2011, 11:58 AM

Quote:

Originally Posted by clkonkol

Good point - I'm still using the trial from forever ago! The system associates ZIP files with WinZip. Back inthe 'old' days (Win 98 probably) you had to have an application to unzip ZIP files and I just do the same now. Probably ought to get in the present, huh?

Thanks for your help and comments.

I think you should remind the XLN tech who told you it was because the HOST was not supported.

He bailed on you IMHO.

Karbo

hopi · 04-06-2011, 02:48 PM

listen in my experience with XLN, they are really nice people... they have been very kind and generous with me, that's for sure...

you can't expect them to solve every problem long distance, eh? Especially one like this where it's 90% user error for not having a decent un packing app and\or not knowing how to use it.

karbomusic · 04-06-2011, 05:44 PM

Quote:

Originally Posted by hopi

listen in my experience with XLN, they are really nice people... they have been very kind and generous with me, that's for sure...

you can't expect them to solve every problem long distance, eh? Especially one like this where it's 90% user error for not having a decent un packing app and\or not knowing how to use it.

I agree and I have had good experiences with them too. However, this particular rep did not invest much effort into the customer and should be reminded so that next time, they will have better information for the customer than "sorry your host isn't on the list". They shouldn't be punished at all but knowing what it actually was will allow them to provide better suggestions in the future. I think they would probably like to know. Additionally, with Reaper having such a generous demo it couldn't take more than a few hours to download it and confirm it works and add it to the supported list.

Karbo