• SONAR
  • Addictive Drums Sample Content Directory? (p.2)
2013/10/11 09:36:18
dubdisciple
swamptooth. makes sense. 
2013/11/24 21:07:47
losguy
sharke
However there does not appear to be a way of separating the samples from the application installation, so EVERYTHING is going to get moved to the new location, including the application itself. This is pretty lame IMO - pretty much every other sample based instrument I've ever installed has included the option to place the samples in a separate location from the program data. 


Agreed - very lame.
 
swamptooth
navigate in windows explorer to C:\Program Files (x86)\XLN Audio\Addictive Drums
cut the folder "Sound Data"
make a folder in my sample location called "Addictive Drums"
open that folder and paste the Sound Data folder into it
open a command prompt in administrator mode
go to the "C:\Program Files (x86)\XLN Audio\Addictive Drums" folder
type mklink /d "Sound Data" "<mysamplepath>/Addictive Drums/Sound Data"
 
this creates a symbolic link to the moved sound data folder so windows "thinks" it's still in the same place
this is by far the easiest way to move directories and requires no registry edits.

 
Very helpful indeed - so much so that I marked it as such.  I've been looking for this capability for other apps too.  According to this article, MS snuck this capability in with Vista (who knew?), and from what I can tell, it is only available through the command-line window.
2013/11/24 21:29:21
Sixfinger
Would the mklink also work for the midi files which seem to be locked here
 
C:\Documents and Settings\Owner\Documents\Addictive Drums\User Midi Files
 
?
2013/11/24 21:32:28
scook
It should. Everything I have relocated with mklink works fine. Should you find a situation where it does not work, it is a simple matter to return the files to their original location.
2013/11/24 21:51:32
Splat
On the subject of the Addictive packages, I don't like it when they don't allow me access to the full installation files. Their XLN app copies the install files to a temp folder, installs the app (i.e. addictive drums) and then wipes the install package.
 
This means (heaven forbid) that if the company went tits up, it might end up being extremely difficult to install the package again if not impossible as you will be reliant on their server being up.
2013/11/24 22:35:14
losguy
Wow- good point.  That is VERY heavy-handed of them - way beyond necessary IMO.  Unless their license agreement says otherwise, someone ought to figure out a way to capture their installers, for sake of future archival in case of a vanishing XLN. 
 
A quick search shows that technology for this sort of thing exists - at least in virtualized setups - for tracing installation sequences. (See here)  It seems to me that a utility based on this could be extremely handy, like in situations where you'd like to back out of an installation gone awry without having to do a complete image-restore of your hard drive.  Oh - and for situations like this.
2013/11/25 09:11:56
Sixfinger
Ok I'm not sure how to open a command prompt, can you spell it out a bit more for the uninitiated?
2013/11/25 09:29:23
scook
type cmd in the start menu search box
2013/11/25 13:43:52
Atsuko
You have to log in your XLN account, the offline files is here: http://www.xlnaudio.com/myaccount-myproducts/offline 
If it doesn't work, search the site for: Offline Installation of Addictive Drums and add-ons
2014/12/18 15:50:22
dede
Hey Arvid and everybody, I'm resurrecting this thread cause I created a link to my sample folder
F:\DD Presets\Addictive Drums\Sound Data
from the original
C:\Program Files (x86)\XLN Audio\Addictive Drums\Sound Data
the cmd syntax seems to be ok but still Addictive Drums fails to launch, I get an error
 
Exception: Cannot find file or directory: C:\Program Files (x86)\XLN Audio\Addictive Drums\XDStacks


What am I missing?
 
Thanks
dd
 
 
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account