FAQ - Content
Installation Pre Sales Authorization Software Installation Guides Cross grade from EA
Installation Issues
TPkd Driver Required in Windows XP
Problem
I get an error message upon installation "The software requires installation of device driver TPkd and a reboot before running. Please reboot and re-install software."
Answer
You need to update your driver software for InterLok copy protection. It is available here.
Digital Performer doesn't see the plug-in
Problem
I updated or installed a new plug-in, but the plug-in does not show up in Digital Performer.
Answer
After updating or installing a new plug-in, you must authorize it when the plug-in starts up for the first time. If you do not authorize, the plug-ins will fail to load. Digital Performer tracks plug-ins that have failed to load and will not, generally, attempt to load them again.
You should perform the following steps:
1. Quit Digital Performer if it is running.
2. Remove the following file, which Digital Performer uses to track Audio Units that have loaded or failed to load. This file is automatically generated if it is not found.
~/Library/Preferences/Digital Performer/Audio Unit Info Cache.
3. Start Digital Performer. After following these steps, Digital Performer should re scan your Audio Units and make the plug-in available for use.
Logic 7 doesn't show plug-in
Problem
You have installed a plug-in, but you do not see it in Logic 7.
Answer
The most likely cause of this problem is that the plug-in is not authorized or Logic was started at some point when the plug-in was not authorized.
What happens: Logic tests Audio Unit plug-ins to ensure they meet certain criteria before making them available for your use. If a plug-in is not authorized, it will fail to completely load and will consequently fail Logic's test. If a plug-in fails this test, Logic will not make it available to you and will not test the plug-in again on its own.
How to fix it: After ensuring the plug-in is authorized, you need to launch the Logic AU Manager and have it re-scan your Audio Units. After performing those steps, you should see the plug-in available in Logic 7.
Can't see Inspector Free in my host
Problem
I installed you free Inspector plug-in but it does not app rear in the list of available plug-ins when I try to insert it in a track.
Answer
Inspector is a stereo only plug-in, as such it will only appear if inserted into a stereo track.
Pre Sales Issues / Demos
Did not get e-mail with download info
Problem
I went to your download request form and submitted it. The reply said that I will get an e-mail with the download link sent to me. I never got an e-mail.
Answer
The download request page uses an automated reply system that simply sends the link to the e-mail you typed into the form. If you don't get the e-mail then you either misspelled your e-mail address or our reply gets caught by the junk mail/ spam mail filter you may use in your e-mail editor. The senders e-mail address of our reply is DoNotReply@rndigital.org.
Drop us an e-mail to sales@rndigital.org asking for the download link and we will send it to you manually.
Authorization Issues
Challenge/ Response Authorization Crash
Problem
I tried to authorize your plug-ins on my mac using challenge/ response when I press the "read response" button on the authorization screen, my mac freezes.
Answer
There is a problem with the interlock copy protection software causing this freeze up. Do not use the button "read response" and paste the response directly into the text window.
Authorize Pro-Bundle using Challenge/ Response
Problem
I bought the Pro-Bundle and want to authorize it using the Challenge/ Response method, but Pro Bundle
is not in the option list in the authorization form on the web.
Answer
Pro Bundle consists of four different plug-ins. They need to be authorized separately since they each create a unique challenge and therefore require a unique response. You therefore need to send us the challenge created by each plug-in that is part of Pro Bundle separately using the web form http://www.rndigital.biz/authorizechallenge.html
OSX 10.3.9. No TRY Button and no Challenge Response Option
Problem
After installing your plug-ins, when starting up the DAW software and authorization window appears. But there is no "TRY" button. When clicking "Authorize" there is also no Challenge/ Response Option only ilok.
Answer
There is a known issue with our software installation that causes this error under Mac OS 10.3.9 We are currently finishing new versions of our plug-ins that will authorize correctly under 10.3.9 as well. In the meantime please e-mail to support@rndigital.org and ask for a 10.3.9 version of the plug-in you are interested in and we can send you a temp. link.
Software Issues
No Bitchin-izer in Pro Tools
Problem
Detailer Version 1.2. has two presets that are called "Bitchin-izer" and "Too Bitch-in", they are supposed to change the name from Detailer to Bitchin-izer, but in my Pro Tools that does not happen.
Answer
The Factory Presets that are stored within Pro Tools can unfortunately not remember the commands needed to change the GUI screen. However, if you can't live without the GUI displaying Bitchin-izer you can either CTRL-click on the DETAILER name or recall the preset using Detailers Load and Save buttons.
No Factory Presets in Digital Performer
Problem
I downloaded and installed your version 1.2. plug-ins that now have new factory presets included. But when I load the plug-in in DP there are no new presets. Where are they?
Answer
Digital performer does not re scan the preset files of our updated plug-ins.
To force DP to re scan all plug-ins you must go to ~user/library/preferences/Digital Performer/and delete the file Audio Unit Info Cache.
Digital Performer will then re scan all plug-ins upon restart and our new presets will magically appear.
Digital Performer 4.61 under OS X 10.3.9. crash
Problem
I run Digital Performer 4.61 under Mac OS 10.3.9. After installing your plug-ins DP crashes every time I try to start it.
Answer
There is an issue with DP 4.61 only when being used with Mac OS 10.3.9. It works well with Tiger. Here is what MOTU had to say about this:
We've taken a look at these crash logs. Apple changed the C++ runtime under 10.3.9. The crash is in the C++ runtime code. So, this is probably some slight incompatibility between your code and the 10.3.9 C++ runtime. DP 4.61 was built under Metrowerks, and so it was not using the Apple C++ runtime. Don't know why that would cause a problem, but it might be related.
Since we are talking about OS and software versions that are more than a year old, I think your best bet is to convince the customers who are having this problem to upgrade to Tiger. Or upgrade to DP5. Or both. DP 5.0 and 5.01 will run under 10.3.9, but our latest, 5.1, requires Tiger.
Peak Pro 5.2 VST Plug-ins crash
ProblemI run Peak Pro 5.2 and run it on intel mac. Sometimes when I try to insert VST versions of your plug-ins Peak crashes when I close the plug-in windows.
Answer
VST versions in Peak Pro 5.2. Universal Binary behave erratically, we have verified this with other non RND plug-ins as well.
The AU (Audio Units) versions of our plug-ins are not causing this problem. Since Peak Pro can use both VST and AU type plug-ins you just use the AU versions instead.