Support
Support
All your questions answered
Pre-purchase questions
Installation questions
System Drive/Users//Documents/Native Instruments/UserContent/Kontakt/PC Snapshots Folder:
C:UsersDocumentsNative InstrumentsUser ContentKontakt
https://pulsedownloader.com
The code starting with XM or APD is NOT a serial number and it is not a PULSE KEY; it is a voucher to be used to re-purchase the library in this page at no cost, so you will receive the actual PULSE code to install your library.
All other questions
For Mac and Windows users, also a batch reserve is suggested, for libraries that have a very high count of samples. Batch resave procedure is included in Kontakt’s manual.
If you are referring to the PULSE CODE, you will find it in an email sent by FASTSPRING when you purchased the library.
If you are referring to a folder inside the main library folder, then you will not find it there. PULSE DOWNLOADER installs the presets and moves them to the correct path automatically. If you need to find it, follow the path:
Mac OS Snapshots Folder:
System Drive/Users//Documents/Native Instruments/UserContent/Kontakt/
PC Snapshots Folder:
C:UsersDocumentsNative InstrumentsUser ContentKontakt
Also read further info here.
REV DI versions presets and sequences will have to be made while an AMP simulator (Guitar Rig, Bias Amp, Amplitube etc..) is added after Riffendium, and of course it would be impossible for us to foresee which amp simulator each user owns, and how he intends to use it, and consequently do all presets for each possible choice.
Custom presets for all REV DI version will have to be made by the user.
Another option is to copy and paste REV version’s snapshots in REV DI’s snapshot folder, deactivate all pedals effects (chorus reverb etc…) and the cabinet (choose the last option in the cabinet menu, “NO CABINET”), then insert an Amp simulator and add effects like reverbs/delays etc…
We are not currently looking for new beta testers. But for info: in order to become a BETA TESTER you need to be very observational and curious. You need to have some time at your disposal to really check the library in different scenarios. We don’t pay beta testers for their time. All they get is a copy of our libraries. A beta tester must not share the library with anyone, or use it commercially before it is officially released, or even speak about it to mates or in forums or blogs.
Not really. We do not hand out NFR copies anymore, unless very specific unique cases.

