1. I've ordered a plugin but got no license mail yet. What can I do?
2. Where are all the additional soundbanks?
3. How can I load the additional banks? I can't see a menu for it.
4. When I try to enter my unlock key nothing happens. What can I do?
5. When I start the host there's a message complaining about missing modules. Why?
6. When I doublecklick on the dll the plugin does not run. What's the reason?
7. What are the exact differences between OP-X and OP-X PRO? Is this anywhere listed?
8. I've lost my plugin and registration data. Do I need to purchase again?
9. Where can I get the Receptor version? Are there additional costs for it?
10. Stringer: When I click on the a preset button the preset does not change.
11. Do the plugins run within Windows Vista?
12. Is there a Mac version available?
13. What are the newest version numbers? Where can I get an update?
14. I'm new in the vst world. What do I need to run the plugins?
15. There's a delay between playing a key and the outcoming sound. Any help?
16. Cubase 5: There's only an empty window when I try to load and unlock OP-X. Any help?
17. Is there a way to use the plugins in a 64bit operating system (windows)?
18. Ableton Live 8 within Vista: Problems with loading the plugins! Any help?
19. Ableton Live within Vista: Audible crackling using multiple instances. Any help?
20. VM Bundle: Occasional audio artefacts within the V-Machine. Any help?
21. Windows Vista & 7: Reg-window not popping up by clicking into blue area. Any help?
22. Windows Vista & 7: Multiple "missing" errors on loading the plugin. Any help?
23. OP-X Blue Reaktor: How do I install it? Where do I put my ensemble?
24. OP-X Blue Reaktor: Only receiving MIDI on channel 1, no reaction in Logic. Any help?
25. The plugin always is unlicensed again after re-launching the host. Any help?
1. I've ordered a plugin but got no license mail yet. What can I do?
The processing time of your order can take one up to eight hours, dependent on
the daytime. So a bit of delay is just normal. It's important that you also check
your bulk or spam folder because some email providers consequently delete mail
from unknown senders as spam, first of all yahoo and mac.com.
You can avoid this
by adding our email address to your contacts or remove it from existing black lists.
In very rare cases our emails are completely rejected and returned to us. In that
case we will try to reach you from an alternative email address, normally a gmail
account.
But sometimes we have no chance to cut through at all. In that case we
are dependent on an action from your side which includes unblocking our sender address
and contacting us by email for a resend, otherwise we are completely helpless.
The email address from which your license
mail is sent and which has to be added or unblocked is info@sonicproject.ch.
But in any case you don't have to worry because your order always reaches us and
can't get lost.
2. Where are all the additional soundbanks?
They are in the folder "additional banks" which is included in the downloaded zip
package. Next to it there's an info text file that briefly describes the contents
of the included banks. You just have to extract and place the folder to a place that suits you
best. You can rename the folder if you like. You can browse and load the bank
then from your vst host. Loading and managing the banks is not done by the plugin
itself. You have to look for the function "load bank" or "load/import fxb bank"
which normally can be found in the "Plugin" menu or as load option directly in
the plugin window. Also have a look at the manual.
If you don't have a vst host then have a look at some of the free vst hosts we
have tested with the plugins and which we can recommend:
free vst hosts.
3. How can I load the additional banks? I can't see a menu for it.
Loading and managing the banks is not done by the plugin
itself, it's done by the vst host. You have to look for the function "load bank"
or "load/import fxb bank"
which normally can be found in the "Plugin" menu or as load option directly in
the plugin window. Place the "additional banks" folder to a place you like, rename
it if you wish, and browse and load the banks from your vst host. Have a look
at the manual, section "load and save sounds" for detailed information. There's an
info text file next to the "additional banks" in your zip package that briefly
describes the contents of the individual banks.
4. When I try to enter my unlock key nothing happens. What can I do?
If nothing happens when clicking on "enter key" after entering the key then this normally
means that the license data hasn't been entered correctly. Use copy and pase to avoid typing mistakes. Also
be sure to enter the whole user-id expression you can
find below "user id" in your license mail, including your name plus id and number, not just a number. Have a look
at the pdf manual, section installation. Also be careful not to add any space bars at the
beginning or at the end of the lines. Cut them back if necessary. 0 is always zero, no letter.
After successful unlocking you have to reload
the plugin. From then on it will be ready and working.
If nothing happens at all whenn you click into the blue window, so no registration window is
launched doing this, or if on one hand licensing worked and was confirmed with "thank you for
registering", but upon re-launching the host the plugin nevertheless remains unlicensed showing
the frozen licensing data entered already when you click on the blue window then this is caused
by windows user account control protection which prevents plugins to write data when they reside
within the protected area (which includes the program files folder) and at the same time the host
has no administrator running rights.
The fix is easy: Simply give your vst host administrator running rights. This in most cases even is
recommended by the host providers. To do so richt-click on the vst host shortcut, choose
"properties->compatibility" and here check "run as administrator" and save. Now licensing will
work. It may be needed to license the plugin now again.
Read more technical background info about windows uac here:
Windows uac virtualization
5. When I start the host there's a message complaining about missing modules. Why?
The reason for this can be that you did not update your plugin correctly or without
being logged in as administrator in windows vista, or also when you tried to do it
manually by moving the extracted dll to the place where the old version was before.
In all these cases there's the danger that the old modules have not been cleanly
removed before the new dll has been placed. That's why you should use the installer.
There's however an easy fix without the need of a new installation: Goto the place
where the plugins have been installed. This can be your shared vst plugins folder or
any other place you chose while installing. In any case there will be a folder called
"SonicProjects" which contains the plugins. Apart from the plugin dlls you'll find a
folder for each plugin containing a set of dat files in it. Delete all these dat
files in these folders, so that you'll have an empty folder in the end, then restart
the sequencer. The correct modules will be extracted now. Concerning Stringer it's
not necessary because this one is not affected. If so, then it's important to leave
the big sample data file undeleted.
If you should have the same issue with Stringer then you've probably forgot to install
the sample data before loading the plugin. You always should install the Stringer
plugin first, then the sample data, without changing the installation path. The
sample data fill find its destination location automatically by reading the registry.
Only load the plugin when you've installed both, the plugin and the sample data.
If this issue appears in Ableton Live 8 within Windows Vista then it has to do with
administrator rights. Without them Vista can block important write functions. You have
to run your application in administrator mode to avoid this. Read more about it
here.
Read more technical background info about this here:
Windows uac virtualization
UPDATE: This issue has been fixed by providing new installers in the newest versions
of OP-X (2.1) and OP-X PRO (1.2).
6. When I doublecklick on the dll the plugin does not run. What's the reason?
You need a vst host to run the plugins. You can't run the plugins as standalone applications.
A vst host is an application that can load and run vst dll files. There are commercial ones
with sequencer functionality like Cubase, Nuendo, Sonar, Live, Orion, Tracktion and many
others. But there are also a lot of free ones that also can be used to run a plugin
standalone. We've set up a dedicated site where we've listed some recommended free vst hosts.
Here's the link:
Free vst hosts
7. What are the exact differences between OP-X and OP-X PRO? Is this anywhere listed?
Yes. Here's a comparison table that lists and compares the features of OP-X PRO,
OP-X, OP-X Player and OP-X Free. Here's the link:
Comparison table
8. I've lost my plugin and registration data. Do I need to purchase again?
No! Just send us an email. We can re-deliver your license mail, however only
to the original purchase address. We also may ask you for some additional data
like purchase id or id number. So you don't have to worry. Once you've purchased
a plugin you are saved and registered within our database. However we nevertheless
highly recommend to make a backup copy of your items and data to a non-crashable
medium.
9. Where can I get the Receptor version? Are there additional costs for it?
No. If you own the standard version then crossgrade to the Receptor version is free.
You can apply for free crossgrade on Plugorama. Choose the plugin you own and click on
"Already own it? Crossgrade to the Receptor version today!". Be conscious that the
support for
the Receptor version is done by Muse Research. Here's the link to plugorama:
Plugarama
10. Stringer: When I click on the a preset button the preset does not change.
This can occur when the host does not initialize the current patch correctly.
Simply click once on the already active preset button before changing to a new
preset. Also be sure that Stringer is actually running ant active, otherwise
the presets buttons won't be active and working.
UPDATE: The radio buttons behaviour has been techically improved in the newest
version 2.0 of Stringer so that they aren't susceptible to this possible issue anymore.
11. Do the plugins run within Windows Vista?
Yes, the are tested within windows vista 32bit. It's however extremely important
that you do installations and updates with administrator rights, otherwise windows
vista can block the access to the registry and other important write functions which
can cause errors and uncomplete installations. So be sure to log in as administrator
to install and update. The administrator account normally is the default account
with all rights.
Furthermore you should run the installer and your vst host in administrator mode.
Otherwise vista can block important write functions. To run the installer in
administrator mode rightclick (instead of doubleclick) on it and choose "run as
administrator". Do the same for uninstallation, by rightclicking on the uninstaller
shortcut in the start menu (Start->SonicProjects) and again choose "Run as administrator".
This will allow the uninstaller to delete everything cleanly. Concerning your VST host
program it's advisable to set the default running mode too to "administrator" too. For this
rightclick on the application shortcut, goto "Properties->Compatibility" and check
"Run as administrator", then save your settings.
So you see most Vista related problems have to do with rights and the exaggerated
protection scheme, and as well as never with the software itself. So generally do
everything in administrator mode, including installation, running of applications
and uninstallation.
Windows vista 64bit is not supported. If you want to run the plugins in a 64bit
system then you have to "wrap" them with a 64bit capable vst host like
Xlutop Chainer.
In any case we always recommend to check it out with the demo version.
Another way is using a 64bit bridge tool. A recommended and tested one is "jBridge"
from j's stuff, which allows to use 32bit plugins glitch free in a 64bit environment.
It's very affordable and yet great. You can get it
here
12. Is there a mac version available?
No, but there's a version of OP-X for Native Instruments Reaktor which is cross
platform. However you need Reaktor 5 to run it, which also will allow to use it
as AU or RTAS plugin then. Here's a demo version:
OP-X Reaktor demo
There will also soon be a way to use the plugins stand alone with the help of the
free VFX application from SM PRO-Audio. We will provide an optimized version for
it as soon as the software will be out:
VFX software
Our flagship synth OP-X PRO-II offers an optimized version for this host featuring a
dedicated installer for easy doubleclick installation. Check this site:
OP-X PRO-II VFX Edition
13. What are the newest version numbers? Where can I get an update?
Have a look at the dedicated section on our standard support site. Click on
"support" in the top menu and scroll down to "Updates and latest versions".
As an owner of a plugin you will automatically receive an update mail when
a new update is out. Unfortunately update mails often are deleted or rejected
as spam. If you own one of the vst versions of the OP series, you simply can
access the update by exchanging the version number in your original download
link (but without the use of a point, e.g. opx20 -> opx21) and use your access
data to download it. You can also send us a mail to request a resend of your
update mail if you didn't receive it.
14. I'm new in the vst world. What do I need to run the plugins?
Have a look at the dedicated section on our standard support site. Click on
"support" in the top menu and scroll down to this topic to learn more about
it. In short, you need a windows computer and a vst host to run the plugins,
as well as a midi interface if you want to play the plugins with an external
hardware keyboard, and an asio soundcard or at least the free asio4all driver
for low latency playing.
15. There's a delay between playing a key and the outcoming sound. Any help?
You need a proper ASIO driver. Standard onboard windows audio drivers are not
suitable for low latency playing, they add too many processing buffers between
the software and the audio output. That's why you can hear a delay. You can
either buy a good ASIO soundcard, like M-Audio Delta 2496, or at least download
the free asio4all driver which can give even onboard audio cards acceptable
low latency performance. Here's the link:
www.asio4all.com.
In any case, should you just use asio4all or a dedicated soundcard, you have to choose
the right ASIO driver in your vst host audio setup. You should also set the buffer size
to at least 512 samples or lower for accurate response. You can find more information
about this on our freeware vst host site:
Free vst hosts
16. Cubase 5: There's only an empty window when I try to load and unlock OP-X. Any help?
This issue has been fixed now - users please read:
It was caused by the automatically popping up licensing window. This has been removed
now in all concerned plugins, including demo versions. All concerned files simply have
been replaced with the fixed ones (without a new version number). To replace your installer
with the fixed one simply delete the old package and download your files again. Then simply
use this installer. Licensing works the same, exept that the registration window has to
be launched manually after loading the plugin by clicking into the blue window. As you
will remember this option was there already before.
Old turnaround text (before it was fixed):
The new Cubase 5 seems to have changed some things in the windows management system
which causes a conflict with the popping up reg window that is launched
to unlock the plugin before the actual GUI is loaded.
There's an easy turnaround for this: Instead of adding an instrument track go directly
to the vst instruments list and load the synth directly from there, then say "yes" to
creating tracks. Now cubase will let you activate the plugin.
If this should not work there's another working turnaround: Simply unlock the plugins within a different VST
host, e.g. the free Herman Seib SaviHost. You can download it from here:
Free vst hosts
Place the SaviHost exe file next to the dll file in the SonicProjects folder and rename it to the same name as the dll
file (e.g. for OP-X.dll: OP-X). Then doubleclick the renamed blue exe and the plugin will
be launched. Unlock as usual. The codes will be written to the registry. Now the plugin is
ready to be used in Cubase 5.
17. Is there a way to use the plugins in a 64bit operating system (windows)?
There's a very cheap and yet perfectly working bridge called "jBridge" from j's stuff,
which allows to use 32bit plugins glitch free in a 64bit environment. It has been tested
with all our plugins. You can get the bridge on this site:
http://jstuff.wordpress.com/
Many hosts already have a bit-bridge included and they will bridge a detected 32bit plugin
automatically. Examples are Cubase, Reaper and Sonar. In these you only need to add the
path of the 32bit plugin(s) you want to use and the rest is done automatically.
Of course you don't need to run a 64bit host in a 64bit system, this is just an option.
You can run normal 32bit host in 64bit systems as before. The only advantage of 64bit hosts
is that they can access more RAM which may be needed if you run large huge libraries or
use lots of ram-heavy plugins at the same time.
18. Ableton Live 8 within Vista: Problems with loading the plugins! Any help?
There's a Vista based issue that can cause Live 8 to stop booting the plugins with
strange error messages concerning missing modules. This issue is caused by the
completely exaggerated protection mechanisms of Windows Vista. This behaviour can be stopped by
running Live 8 in administrator mode. If Live is not run in administrator mode
Vista declares several actions as dangerous which are not dangerous at all.
To switch the default runninmg mode to "administrator" rght click on the Live 8 shortcut
and choose "Properties->Compatibility". In this area check "Run as administrator" and
save the new settings.
Furthermore it's highly recommended to run the installer in administrator mode too. So
instead of doubleclicking right-click on it and choose "run as administrator". This will
give the installer the rights do do what it needs to do, otherwise vista can block
important things. For uninstalling do the same: Rightclick instead of doublecklick on
the uninstaller in the start menu (Start->SonicProjects) and again choose "run as
administrator". Then everything will be cleanly removed, otherwise vista will block the
removal of some stuff.
UPDATE: This issue has been fixed by providing new installers in the newest versions of
OP-X (2.1) and OP-X PRO (1.2).
19. Ableton Live within Vista: Audible crackling using multiple instances. Any help?
This again is a Windows Vista related problem and has nothing to to with the plugins.
It only appears when Ableton Live is not run with administrator rights and multicore
support is activated (which allows to distribute the load to multiple cores). The
crackling has nothing to do with the drivers or a CPU overload as you might suppose
(it's also there when CPU load ist just 20% and buffer size is at a high value).
To get rid of this behaviour you should run Live with administrator rights.
To switch the default running mode to "administrator" right-click on the Live 8 shortcut
and choose "Properties->Compatibility". In this area check "Run as administrator" and
save the new settings. Then the crackling will be gone.
If Ableton Live is not run with administrator rights Windows Vista can block important
read and write functions that can limit the functionality of the plugins, which also
can lead to other issues (e.g. licensing issues, see above).
20. VM Bundle: Occasional audio artefacts within the V-Machine. Any help?
If the V-Machine occasionally produces bad audio artefacts similar to short machine
gun like sample repetitions ("rrrr") then you've forgot to replace the standard GUI
dlls on the stick by the Non-GUI ones from the "Replacement" folder of the package
before transferring the banks and plugins to the V-Machine.
These dlls are a bit smaller and have no GUI at all (only the dsp side) which guarantees
stable and glitch free performance in the V-Machine. The GUI (graphical user interface)
of the standard versions can disturb the V-Machine's internal processing and produce those
artefacts. So it's extremely important that you follow the installation guide step by
step rather than just doing what you're used to do. Then there will be no artefacts,
never ever, this is guaranteed by the bundle if having been installed correctly.
To fix this by replacing the wrong GUI-dlls of OP-X and Stringer in the V-Machine with
the Non-GUI ones do the following: 1. Clear the banks. Like this they will remain at the
same position ready to be overwritten. To do this, choose the "SonicProjects OP-X" bank,
depress both "menu" buttons and scroll to "Menu:Clear". Now clear the bank. Do the same
with the "SonicProjects Stringer" bank. Alternatively you also can completely delete them
(the newer version of the firmware might no offer "clear" anymore) by choosing Menu:Delete->bank".
2. Now delete the "SonicProjects OP-X" and "SonicProjects Stringer" plugins by again holding down
both "menu" buttons and scroll to "Menu:Delete->Plugin" and choose "SonicProjects OP-X" and
"SonicProjects Stringer" to delete. Now everything is ready for a new import.
On your stick open the "plugs" folder, then "SonicProjects OP-X". Here delete the
"SonicProjects OP-X.dll" and replace it by the one from the "Replacement" folder of the
download package. This dll is a bit smaller and has no GUI. Do the same with the
"SonicProjects Stringer.dll" in the dedicated folder. Now you can mount the stick and
import the bank again. Of course everything is described in the pdf installation guide.
For a visual support you also can have a look at this video which shows all installation
steps performed on a mac. On the PC it's the same, exept the location of the VFX library,
which on PC is in a hidden folder (see manual) and in the coming new version of VFX in
user/username/music/VFX Library.vfxlibrary:
VM Bundle Installation Video
21. Windows Vista & 7: Reg-window not popping up by clicking into blue area. Any help?
If your vst host is not a certified Wibdows Vista/7 program (so does not contain a
so called "trustinfo manifest") and your vst plugins reside within the system's
program files folder, then windows can restrict activities and writing rights, and
prevent the registration window from popping up when you click into the blue area
to enter your license key.
To get rid of this behaviour just run your host with administrator rights by default.
To switch the default running mode to "administrator" right-click on the application shortcut
and choose "Properties->Compatibility". In this area check "Run as administrator" and
save the new settings. This won't harm functionality in any way, it just gives back
the program full writing rights, as it should be. Now licensing will work again.
Read more technical background info about it here:
Windows UAC virtualization
22. Windows Vista & 7: Multiple "missing" errors on loading the plugin. Any help?
If your vst host is not a certified Wibdows Vista/7 program (so does not contain a
so called "trustinfo manifest") and your vst plugins reside within the system's
program files folder, then windows can restrict activities and writing rights, and
prevent the plugin to extract needed modules. That's why it can't find them.
To get rid of this behaviour just run your host with administrator rights by default.
To switch the default running mode to "administrator" right-click on the application shortcut
and choose "Properties->Compatibility". In this area check "Run as administrator" and
save the new settings. This won't harm functionality in any way, it just gives back
the program full writing rights, as it should be. Now it should work again. If not, then
once more uninstall and install the plugin.
UPDATE: This issue has been fixed by providing new installers in the newest versions of
OP-X (2.1) and OP-X PRO (1.2).
23. OP-X Blue Reaktor: How do I install it? Where do I put my ensemble?
It's recommended to put your ensemble file into the Ensembles folder of the user library
which is here:
Finder->Documents->Native Instruments->Reaktor5->Library->Ensemble.
So put or copy your ensemble file into this folder. When you launch Reaktor 5 be sure
the browser tab is chosen (the one with the reading-glass icon). Here you have a FACTORY
tab and a USER tab. Change to the USER tab. Here, at the bottom left, you will now see
your ensemble file. To launch it for playing simply drag it into the empty area on the right.
24. OP-X Blue Reaktor: Only receiving MIDI on channel 1, no reaction in Logic. Any help?
This can be the case if the default MIDI channel of the OP-X instrument is set to 1
instead of 0 (Omni). To change it to omni launch Reaktor 5 as stand alone, load OP-X,
click somewhere on its GUI so that the instrument is chosen, and in the top menue of
Reaktor 5 choose "View" and here check "Edit Mode". Now you can see 4 instead of 3 tabs
on the left. Choose the one with the checkbox icon at the very right. Here choose the
"Connect" tab at the very right. Here, below MIDI INPUT, there's a box on the right side
entitled "Channel" which has value "1". Doubleclick into this box, enter "0" instead and
then hit enter on the keyboard. The content of the box now should turn to "Omni". From
the Reaktor 5 top menue again unckeck "Edit Mode" in "View". Now close Reaktor, and
in the upcoming dialogue box asking if you want to save changes choose "Yes". Now your
OP-X ensemble will receive MIDI on all channels.
25. The plugin always is unlicensed again after re-launching the host. Any help?
If on one hand licensing worked and was confirmed with "thank you for
registering", but upon re-launching the host the plugin nevertheless remains unlicensed showing
the frozen licensing data entered already when you click on the blue window then this is caused
by windows user account control protection which prevents plugins to write data when they reside
within the protected area (which includes the program files folder) and at the same time the host
has no administrator running rights.
The fix is easy: Simply give your vst host administrator running rights. This in most cases even is
recommended by the host providers. To do so richt-click on the vst host shortcut, choose
"properties->compatibility" and here check "run as administrator" and save. Now licensing will
work. It may be needed to license the plugin now again.
Read more technical background info about it here:
Windows UAC virtualization
Don't hesitate to contact us by email if your question could not be answered here.
Contact us
