Receptor support:
click here
For questions regarding version 1.2 Mac and x64 visit this FAQ:
click here
For more general help topics visit the main support site:
click here
NOTE: 1.1 Update available which might fix your issue if you're still working with 1.0.
To get 1.1 simply replace the 10 with 11 in your download link.
General Note: OP-X PRO-II needs good and stable ASIO drivers to run. So get a decent
soundcard or at least Asio4all drivers. All crappy Direct-X or MME Windows drivers are
not supported and may even cause crashes. Use a sample buffer size between 128 and 1024 samples
(not higher), dependent on your system and drivers.
EDIT: Version 1.1 is much less demanding on drivers and might even work with windows drivers.
Here is some quick help for some stuff that might occur, based on some support
requests we've collected so far:
1. I've upgraded OP-X/OP-X PRO but have not yet received my license mail. Any help?
2. When I try to license the plugin it says "can't create license file". Any help?
3. Frozen GUI, no sound, no reaction on launching licensing window. Any help?
4. Clicks and pops using Asio4all drivers in Windows Vista or 7. Any help?
5. Crash on exporting a session to mp3 in Fruity Loops. Any help?
6. The bank load button does not work in Live 8. Any help?
7. Artefacts at the loop return points when looping tracks in Live. Any help?
8. I can't manage to download the file from the link in my email. Any help?
9. I can't find my custom banks and presets in the "OP-X PRO-II" folder. Any help?
10. What are the sytem requirements for OP-X PRO-II?
11. I have Protools 8 on Windows. Will OP-X PRO-II work using the Fxpansion adapter?
12. Sonar 8 (32bit) in Windows 7 64bit: Crash on opening synth GUI. Any help?
13. Can I install and use OP-X PRO-II anlongside with OP-X PRO and OP-X?
14. Can I load my former OP-X PRO patches with OP-X PRO-II?
15. Will there be released further sounds for OP-X PRO-II in the future?
16. Is there somewhere a list in text format of all OP-X PRO-II presets?
17. Cubase 5.5.2: Largo loses GUI when OP-X PRO-II is instantiated. Any help?
18. FL Studio 10: OP-X PRO-II makes no sound or only for a few seconds. Any help?
19. NI Kore 2: Crashes when loading OP-X PRO-II. Any help?
20. Live 8: Bank load button points to sessions folder instead of correct place. Any help?
21. Can't write banks or patches when trying to save bank or patches. Any help?
22. VFX crashes after switching to OS-X Mountain Lion. Any help?
23. VFX: No keyboard reaction when trying to enter key, VFX freezes and crashes. Any help?
24. Compressed zip files can't be unpacked after downloading. Any help?
25. JBridge: Dispatcher opcode error message after closing and re-opening GUI. Any help?
26. Brainspawn Forte: Doesn't save and retrieve sounds for scenes. Any help?
27. Asio4all: No sound in Windows 8. Any help?
28. VFX: Can't import OP-X PRO-II or can't be launched. Any help?
29. Sonar X3: Sound changes or not correctly recalled sounds. Any help?
30. Laptop: Crackling or distorted sound even using asio4all. Any help?
31. OS-X Yosemite: No instrument interface and no sound in VFX. Any help?
32. Cubase Pro 8: OP-X PRO-II not listed anymore after updating to Pro 8. Any help?
33. A button or knob is moving by itself on certain actions. Any help?
1. I've upgraded OP-X/OP-X PRO but have not yet received my license mail. Any help?
First of all too check your spam box. If the mail should not appear in your inbox
or spam box within 30 minutes, then your mailserver probably has blocked the mail,
which is sent automatically immediatly after the purchase.
In that case just send and empty email with the subject line "RESEND" to info@sonicprojects.ch.
Important: The mail must be sent from the same email address that has been used in your
order, so e.g. your paypal email address.
We will resend your license mail then manually to your purchase email address within one up to eight hours, if possible
of course immediatly. Also in this case too check your spam box.
If we notice that the provided email address permanently blocks incoming mails then
we try to re-send you the license mail from an alternative gmail account, and if this
does not work too we will look up your original OP-X (PRO) purchase address and try
to send it there.
2. When I try to license the plugin it says "can't create license file". Any help?
Just run your vst host program / sequencer once in administrator mode just for licensing.
Then the error message won't appear. To do this right-click on the application shortcut
and choose "run as administrator" (item with shield).
Since the blocking of writing also could affect writing of banks and your synth may turn unlicensed
again after re-launching the host without administrator rights you better may change
the default running mode of your vst host to "administrator" permanently which gives it
back full writing rights. For this right-click on the vst host application shortcut, choose
properties->compatibility and here check "run as administrator" and confirm. Now licensing
should work.
Alternatively you also can change the rights of the "OP-X PRO-II" folder to allow writing for the user.
This folder can be found next to the plugin within the "SonicProjects" folder in your vst plugins folder.
So right-click on the "OP-X PRO-II" folder, choose
properties->security, and here choose the "user" line. Click on the "edit" button to change the
rights. In the popup-list check "write" to allow for writing to this folder as user and save.
From now on you will be able to save patches and banks to this folder.
You by the way also can do this for your whole vst plugins folder and choose to include all sub-folders.
This is a very good measure to avoid such types of errors (caused by windows user account protection)
also in the future and for other plugins.
Read more technical background info about this here:
Windows uac virtualization
If it still shouldn't work then create the license file manually. Use the text editor (start->accessoires->text editor)
to create a file called "license.txt" (the suffix is written automatically, so just name the file "license"). In the
top line copy your license key like this: Prename Name ID:XXXX,0000-0000-0000-0000-00000
So first on your full user id, then your key, separated by comma, just one line (of course your own data, not the example
one above). Then copy this "license" text file into the "OP-X PRO-II" folder next to the dll (both are in the "SonicProjects"
folder in your vst plugins folder).
Alternatively to this manual method you also simply could license the plugin with
SaviHost, which is a very easy to use one-file VST host that simply can be copied
next to the dll, renamed to the dll name and launched with the synth by doubleclicking it.
Then you can license it from here. Here's the download link and installation guide
(VST Host box):
SaviHost Download
3. Frozen GUI, no sound, no reaction on launching licensing window. Any help?
These are errors mainly caused by windows protection within a standard user account
when your plugin folder resides within the system's program files folder. Read more
about it here
The easiest way to get rid of it is to set the default running mode of your sequencer or
vst host to "administrator". For this right-click on the application shortcut, choose
"properties->compatibility" and check "run as administrator", then save this setting. This gives back
full writing rights.
Another clean solution is generally only to use the administrator account for your
music system; this one has no restrictions compared to a normal user account where you
are treated like a non adult person; the administrator account is not active by default,
but it can be activated somewhere in the system settings; afterwards it will be
showed as login option at startup
Read more technical background info about this here:
Windows uac virtualization
4. Clicks and pops using Asio4all drivers in Windows Vista or 7. Any help?
While the free Asio4all drivers sometimes can be a workaround if you have no
dedicated ASIO soundcard, they don't work satisfyingly in all systems and
configurations. Get a decent soundcard with good ASIO drivers (M-Audio, RME or
similar) for serious work, which also will give you much better performance and
lower CPU load. Using proper ASIO drivers you won't meet any of those artefacts.
5. Crash on exporting a session to mp3 in Fruity Loops. Any help?
The additional task of encoding audio while exporting often seems to overload the
system since OP-X PRO-II is quite demanding on ressources. Generally export sessions
to uncompressed wav first, which is better anyway and will work without a crash. You can
create your mp3 file later on from the wav source.
6. The bank load button does not work in Live 8. Any help?
Fixed in OP-X PRO-II version 1.1.
To get OP-X PRO-II 1.1 simply replace the 10 with 11 in your download link.
Old 1.0 fix:
This can happen when you move around the plugin manually by your own after installing
which you shouldn't do. Choose the right path already during installation, which lets
you point the installation destination to any place of choice. If you move (still not recommended
since the start menu items and the uninstaller will lose their path) then move both
the OP-X PRO-II.dll AND the accompanying "OP-X PRO-II" folder which build a unit and
must remain in the same relative position to each other (so both in the same folder).
We've tested OP-X PRO-II in Live 8.2 by ourselves, and the banks loading button works
fine if you install OP-X PRO-II correctly.
If you nevertheless should have troubles loading banks with the banks button then forward your system
specs to us so that we could look into it. Banks in any case still can be loaded using the file menu in the
instrument block. The banks are located in the "OP-X PRO-II" folder next to the
OP-X PRO-II.dll within the installed "SonicProjects" folder.
7. Artefacts at the loop return points when looping tracks in Live. Any help?
Fixed in OP-X PRO-II version 1.1.
To get OP-X PRO-II 1.1 simply replace the 10 with 11 in your download link.
Old 1.0 fix:
Since OP-X PRO-II is quite a demanding synth on CPU and ram ressources it often
seems not to be suited for looping stuff. Use the lighter standard OP-X PRO for it
(contact us for a license if you only own OP-X PRO-II). OP-X PRO-II has a much more
complex inner life than OP-X PRO, in fact almost double as complex because of the
doubled polyphony featuring separate voice design, which works with a separate mono
synth for each single voice. So OP-X PRO-II is not suited for erverything. It's
recommended to render its MIDI tracks to disc/audio files for critical looping stuff
or very big mixes/arrangements.
8. I can't manage to download the file from the link in my email. Any help?
Maybe it was only the server that was down, so try again later. If it still doesn't work
then try to use a different browser to download, or oven try it from a different
computer. If it generally doesn't work directly from the email then copy the
link and paste it into the address field of your browser and hit enter. Deactivate
any third party download managers before. You should be promted then to enter your
personal access pass. Then you should be able to download and save the file to a
place of choice on your computer.
9. I can't find my custom banks and presets in the "OP-X PRO-II" folder. Any help?
If you can see the banks and presets from the synth's browser but can't find them
there when browsing the folder from windows when you e.g. want to make a backup of
your custom sounds then windows has written them to a mirrored place in the "virtual store"
area instead. Windows Vista and 7 will do this when the plugin resides somewhere within
the system's program files folder and at the same time your vst host is not run with
administrator rights. Then windows restricts writing rights within this area and redirects
all written files to this mirrored "save" place. This is called "virtualization".
To be able to access this mirrored "virtual store" place you before need to activate
hidden files view. To activate it do the following:
Windows Vista:
Start->Control Panel->Folder Options->View ->activate "Show hidden files and folders".
Windows 7:
Start->Control Panel->Appearance and Personalization->Folder Options->Show hidden files and folders->
view: Files and Folders->Hidden files and folders: Check "Show hidden files, folders and drives"
Now you can find the mirrored files in this place:
Computer->Local drive->Users->Your User Name->AppData->Local->VirtualStore
as root and then in the same specific location as your original "OP-X PRO-II" folder
is located it, so e.g for Cubase 5:
VirtualStore->Program Files(x86)->Common Files->Steinberg->VST2->SonicProjects
You will only find the banks and presets there that you have saved by yourself after installation.
Windows makes the synth look in both the original and the mirrored folder for its files.
Read more technical background info about this here:
Windows uac virtualization
10. What are the sytem requirements for OP-X PRO-II?
The system requirements are listed here.
Please note that we can't give any guarantees that the sysnth will work in your exact system since there are countless
possible vst host / hardware / operating system combinations which makes it impossible for us to test all of them. So
it's up to you to check it out with the demo version. If the demo version works then the full version will too.
We have successfully tested it with the following:
Operating systems: Windows XP, Windows Vista, Windows 7
CPUs: Intel Pentium 4 3.2 gHz, Intel Core2duo 2,53 gHz, Intel Core i7 920
Hosts: Cubase SX 1.x, Cubase 5, Live 7, Live 8, SaviHost, Protools 8 (with Fxpansion adapter)
Soundcards: M-Audio Delta 2496, RME Hammerfall HDSP 9632, Realtek onboard with Asio4all
But as you know it will always depend on the dedicated combination of components. So the only way to to find out is
the demo version.
11. I have Protools 8 on Windows. Will OP-X PRO-II work using the Fxpansion adapter?
Yes it works. We have tested it successfully with Pro Tools 8.0.4 and the Fxpansion VST to RTAS adapter v2.1.1
in Windows 7 Professional 64 with favourable results. We however can't guarantee that it will
work with other versions of Protools and Fxpansion and other operating systems. So check it out
by yourself with the demo version.
More infos and a video can be found here.
Note: It will only work in Protools Windows, not Mac!
12. Sonar 8 (32bit) in Windows 7 64bit: Crash on opening synth GUI. Any help?
This can happen when your plugin folder is not located in the 32bit area of the
system. The 32bit area is the (x86) are. The correct place for Sonar vst plugins is:
C:\Program Files(x86)\Cakewalk\Vstplugins (or similar)
13. Can I install and use OP-X PRO-II anlongside with OP-X PRO and OP-X?
Yes, OP-X PRO-II is an independent synth with its own installation path and files,
so it won't affect your currently installed OP-X PRO or OP-X in any way. All OP series synths can be
installed and used in parallel at the same time, since they all are independent from
each other and have a separate installation path, so noone will overwrite the other.
The only thing they share is the same SonicProjects root folder.
UPDATE: Some hosts (e.g. Cubase 5 ff, Receptor) can't run multiple plugins having
the same unique plugin ID at the sime time which means in these you can't run OP-X PRO and OP-X PRO-II
alongside since these two share the same plugin id because of patches compatibility. When
you install both then these hosts only will list one of them. So regarding OP-X PRO and
OP-X PRO-II you have to decide which one to use in these hosts. But since OP-X PRO-II can
do all OP-X PRO can and too can load all its sounds you don't lose anything just running
OP-X PRO-II.
The same is the case for OP-X PLAYER and OP-X which too share the same ID. But also here
OP-X can do all OP-X PLAYER can and too can load all of its sounds.
All other combinations, like e.g. OP-X and OP-X PRO-II, OP-X and OP-X PRO, OP-X PLAYER and
OP-X PRO or OP-X PLAYER and OP-X PRO-II however too will work in these hosts since they
have different plugin IDs.
14. Can I load my former OP-X PRO patches with OP-X PRO-II?
Yes, OP-X PRO-II can load all former OP-X PRO patches and will play them with identical
sound. Of course you can enhance them then with the new features, increase polyphony, add
effects, and so on. The only important thing you should know is that once loaded and saved again
with OP-X PRO-II the patches and banks can't be loaded anymore with the standard OP-X PRO.
So keep the patches separate.
If you want to keep using the old OP-X PRO banks library in OP-X PRO-II then you'll be pleased
to hear that we provided all former OP-X PRO banks in cleaned form (there sometimes was some
trash in the sub preset 64 area which then shows up in OP-X PRO-II since this one uses the full
128 presets area of banks, this trash has been cleaned) in one single package for download on
the OP-X PRO-II sound reloads page. Scroll to the headline "Former OP-X PRO library":
/opxpro2/userarea.html
The sounds of OP-X and OP-X PLAYER can't be loaded directly in OP-X PRO-II, but the OP-X PRO banks
library which you can download on the site linked above includes all original OP-X / OP-X PLAYER
banks and too their factory default banks.
So you can turn OP-X PRO-II into an OP-X PLAYER, OP-X or OP-X PRO with identical sound and identical
patches anytime you need it.
15. Will there be released further sounds for OP-X PRO-II in the future?
Yes, although the built in library already includes more than 1'500 sounds, this won't
stop us extending the library furthermore with new free downloads. There already are
some new packages available. The sound reloads site is:
/opxpro2/userarea.html.
16. Is there somewhere a list in text format of all OP-X PRO-II presets?
Yes, our customer Rob Mitchell has created an excel format file containing all preset
names sorted by banks to share it with all users. Thanks a lot Rob!
Download Preset List (Excel format, zipped).
17. Cubase 5.5.2: Largo loses GUI when OP-X PRO-II is instantiated. Any help?
Update eLicenser (used by both Largo and Cubase) to the newsest version and the issue will be gone.
Seems to be a highly specific behaviour of Largo in Cubase 5.5.2 only when eLicenser has not the newest version.
18. FL Studio 10: OP-X PRO-II makes no sound or only a few seconds. Any help?
Fixed in OP-X PRO-II version 1.1.
To get OP-X PRO-II 1.1 simply replace the 10 with 11 in your download link.
Old 1.0 fix:
Check the option "use fixed size buffers" within the FL wrapper in the section "procesing". You may also
open the gear box and click brigded on the second page if this isn't applied automatically. After the changes
are done you need to reload the plugin.
19. NI Kore 2: Crashes when loading OP-X PRO-II. Any help?
Fixed in OP-X PRO-II version 1.1.
To get OP-X PRO-II 1.1 simply replace the 10 with 11 in your download link.
Old 1.0 fix:
It's not yet clear what exactly causes this, but it has been reported that changing of the sample rate
from standard 44.1 kHz to 48 or 96 kHz fixes it. Higher sampling rates too have the positive effect of
lower latencies, so recommended.
20. Live 8: Bank load button points to sessions folder instead of correct place. Any help?
This sometimes can happen after updating from 1.0 to 1.1 out of not yet solved reasons. To
fix it do the following: Create a folder in the place the bank load button wrongly points
to (normally the place you've open the last live session from) and copy one of the fxb banks
from the OP-X PRO-II folder (which can be found next to the dll) into this folder. Now open
the bank using the bank load button of OP-X PRO-II from there and restart live. From now on
the bank load button should always point to the correct place.
21. Can't write banks or patches when trying to save bank or patches. Any help?
This can occur in some hosts if the plugin resides within the protected area (program
files folder) and the host isn't run with administrator rights. The windows user account
protection (Vista and 7) then doesn't allow the plugin to write to the protected area.
In most cases the writing then is re-directed to a mirrored place called virtual store,
but with some hosts this doesn't work correctly.
Read more technical background info about this here:
Windows uac virtualization
To re-achieve full writing rights you either could set the default running mode of the
host to administrator (right-click on program shortcut, choose properties->compatibility
and here check "run as administrator" and save). You also could have your plugins installed
to a different place than the program files folder.
But there's also another easy fix if you
don't want to change anything: Change the rights of the "OP-X PRO-II" folder which is the
place the banks and patches are saved to. This folder can be found next to the plugin. So
right-click on the "OP-X PRO-II" folder, choose properties->security, and here
choose the "user" line. Click on the "edit" button to change the rights. In the popup-list
check "write" to allow for writing to this folder as user and save. From now on you will
be able to save patches and banks to this folder.
22. VFX crashes after switching to OS-X Mountain Lion. Any help?
Apple has changed some things regading X11 in Mountain Lion which VFX needs to
display the graphical user interface of the plugin. X11 isn't installed anymore
by default and older existing versions in upgraded sytems may not work anymore
properly in mountain lion. But there's an updated new version that works.
That's what apple writes on their homepage:
„About X11 and OS X Mountain Lion: X11 is not included with Mountain Lion, but X11
server and client libraries for OS X Mountain Lion are available from the XQuartz
project:
http://xquartz.macosforge.org
You should use XQuartz version 2.7.2 or later.“
The article link on the apple homepage:
http://support.apple.com/kb/HT5293.
After installing the new compatible X11 version VFX works fine again.
23. VFX: No keyboard reaction when trying to enter key, VFX freezes and crashes. Any help?
This can happen when the installed X11 is a too old version (e.g. 2.0). The page
below has all available versions listed for download. Download and install the highest
version available for your system. You may restart the system after installing so
that the newest version becomes active. You can check the installed version by bringing X11 to
the foreground (click on X11 in the dock) and choose File->About X11.
Here are all available X11 versions listed for download:
http://xquartz.macosforge.org/trac/wiki/Releases.
24. Compressed zip files can't be unpacked after downloading. Any help?
Some users have reported that after downloading a zip file (demo or full version)
the system was not able to unpack it putting out some error codes or saying the file
is invalid. After some in depth investigation we found out that this is google chrome
related which seems to manipulate the integrity of zip files while downloading in
some circumstances, mainly if they require a pass to download. We don't know why
exactly at the very moment. The files themselves all are ok.
Solution: Simply use a different webbrowser to download the file, e.g. internet explorer,
firefox or safari which all don't seem to suffer from this issue.
UPDATE: We found out how you can get rid of this misbehaviour in Google Chrome itself
so that you nevertheless can use Google Chrome to download the compressed zip file. Click
on the Chrome settings icon (the square button with the three horizontal lines) on the top
right of the browser toolbar, choose "Settings", scroll down and click on "show advanced
settings" and here, below "Privacy", uncheck "Phishing and malware protection". Then
chrome won't damage the zip file anymore when downloading it and you'll be able to open it.
25. JBridge: Dispatcher opcode error message after closing and re-opening GUI. Any help?
Problem: Closing and re-opening the GUI of OP-X PRO-II in bridged mode using JStuff
JBridge for bridging sometimes makes the sequencer hang for about 30 seconds and then puts out the error message
"Dispatcher opcode 14 failed" or similar.
Solution: The author of JBridge advises to use the "separated GUI mode" option since
jBridge's integrated mode doesn't work well with the synth in some situations. To activate this
option click on the "Edit" button in the bottom area of the JBridge window frame (just below
the GUI) and here check "Switch to separate GUI mode". Now you have to remove and re-instantiate
the plugin to make the changes work.
Also some JBridge users say it helps to activate the "Dispatcher 19 error" option
within JBridge which is said to eliminate too a lot of other possible issues with
other plugins. Activating this option seems to be sort of a secret trick.
26. Brainspawn Forte: Doesn't save and retrieve sounds for scenes. Any help?
Problem: After updating Brainspawn Forte doesn't save and retreive sounds for OP-X PRO-II
saved with a scene. Forte loses or forgets the sounds on scene changes.
Solution: This unwished behaviour is caused by an obsolete wrong setting in the forte
startup file. To fix it do the following:
1. Go to the directory where Forte in installed.
For the 32 bit version the default install path is: c:\Program Files (x86)\brainspawn\forte 3 Performer Edition\
For the 64 bit version the default install path is: c:\Program Files\brainspawn\forte 3 Performer Edition\
2. In that directory there is a file called DeviceCompatibility.xml
3. Open the a writable version of the file with notepad, wordpad or whatever text editor you wish to use.
4. In the file you will find a section like the following:
<Device Name="OP-X">
<saveFXB bool="1"/>
<saveFXP bool="0"/>
<saveProgramNumber bool="0"/>
<saveParams bool="0"/>
</Device>
5. Delete the entire section (all 6 lines)
6. Save the file and you should be good to go.
NOTE: This is currently added in the default DeviceCompatibility.xml file, so if you upgrade, you may have to do this again with the new version.
Note that this issue already has been reported to Brainspawn, so it might be fixed already in newer versions of Forte.
27. Asio4all: No sound in Windows 8. Any help?
This mainly can be caused if the audio playback device still is in use by a different
application in the background. In the Asio4all control panel you can see this if you open the
advanced options (spanner icon on the bottom right) and then collaps the audio devices
list by clicking on the "+" on the top left. When there's a red cross in the output device
line this is the reason.
To fix this rickt-click on the volume icon in your system tray and choose "playback devices".
You also can get there from the control panel -> hardware and sound -> sound. Here right-click
the speaker, choose properties, and here on the "advanced" tab uncheck "allow applications to
take exclusive control of this device" and "give exclusive mode applications priority". After
this is done reboot your system and check if it works now. If it still doesn't work then again
goto the advanced settings of the asio4all control panel and check "always resample 44.1kHz <-> 48 KHz".
This still should fix possible sample rate incompatibilities.
28. VFX: Can't import OP-X PRO-II or can't be launched. Any help?
First of all make sure you have the newest X11/XQuartz installed. It can be downloaded here:
http://xquartz.macosforge.org/
Since OS-X normally blocks new Non-Apple software first on launch VFX from within the
applications folder via context menu. For this open the Finder, goto "Applications", and
here look for the yellow VFX icon. Right-click/Ctrl+Click/Two-Finger-Tap on it so that the
context menu is shown, and here choose "Open". Then you normally have to confirm the start.
From now on the app is unblocked and also can be launched from the launchpad or via a
connected file like vfxlibraries.
You also might check if VFX has Read & Write permissions activated for the current user. For
this again goto Finder->Applications and Richt-Click/Ctrl+click/Double-Finger-Tap the yellow
VFX icon so that the context menu is shown, and here choose "Get Info". In the info window
expand the "Sharing & Permissions" tab at the very bottom, and go sure that the "Privilege"
for the current user is set to "Read & Write" and not just read. If not change it to "Read & Write".
If doublecklicking the OP-X PRO-II.vfxlibrary nevertheless doesn't launch VFX and start import then
you also can manually import it from within VFX. For this first on launch VFX, click on the small white
vfx icon at the top left, and here choose "File->Import from VFX Library..." and browse to the
OP-X PRO-II.vfxlibrary file and import it.
29. Sonar X3: Sound changes or not correctly recalled sounds. Any help?
Issues of this kind could be caused by two reasons: On one hand missleaded re-directions
of the MIDI output of OP-X PRO-II (which sends a program controller dump by default on
program change) to the input of another instance caused by MIDI input echo. On the other
hand there's been traced a small bug regarding recalling sounds in Sonar X3d sometimes leading
to loading the standard sound instead of the chosen one when the sound was chosen from
the GUI. This issue will be fixed in the Sonar X3e update.
To avoid the MIDI issue simply always unckeck the "enable midi output" option in the
insert software synth properties dialog box when you load an instance of OP-X PRO-II.
This will prevent MIDI coming from the MIDI output of OP-X PRO-II going anywhere.
30. Laptop: Crackling or distorted sound even using asio4all. Any help?
First of all, if you don't use an external audio interface and just use the onboard
sound then download and install the free ASIO drivers from Asio4all:
http://www.asio4all.com/
Once installed choose them as your used audio drivers in the audio properties of your
vst host. They should show up as "ASIO: ASIO4ALL v2". If you can choose a buffer size
then choose 512 which should give you a reasonable low latency. You also could try 256
which would result in lower latency but higher cpu load.
However even using ASIO drivers there can be crackling when your laptop hasn't been optimized
for running virtual instruments. This however is extremely easy to do:
1. Power management to high performance: Open the control panel (win 7: start->control panel, win 8:
charmbar->settings->control panel), and here choose "system and security" -> power options, and here
check the "high performance" option. Once it's chosen click on "change plan setting" and set all
time fields to "never".
2. Processor scheduling to background services: Open the control panel (win 7: start->control panel, win 8:
charmbar->settings->control panel), and here choose "system and security" -> "system" and here doubleclick
"advanced system settings" on the left side. In the settings window choose the "advanced" tab, and in the
"performance" section click on the "settings" button. In the performance options window choose the "advanced" tab and
here in the "processor scheduling" section select "background services" instead of programs and apply.
This will do the trick and your laptop is ready for playing vst instruments.
If Asio4all should deliver no
sound when it's active then do the following to prevent the windows GS wavetable synth to be always active and blocking asio4all if not
wanted: Open the Control panel->Hardware and Sound->Sound->doubleclick on Speakers->Advanced->uncheck exclusive mode.
Now reboot your system and check if it works now.
If there's still no sound
then open the advanced settings of the asio4all control panel and here check "always resample 44.1kHz <-> 48 KHz".
This trick still should fix possible sample rate incompatibilities.
31. OS-X Yosemite: No instrument interface and no sound in VFX. Any help?
First on make sure you have the newest X11 installed. Older versions remaining from
previous systems may not work anymore after updating the system, and a fresh Yosemite doesn't
have X11 pre-installed anymore. You can download it here:
http://xquartz.macosforge.org/landing/
If the newest version shouldn't work then go for version 2.7.5 which has been reported to work
ok in OS-X 10.10.1 with VFX. Here are all versions:
http://xquartz.macosforge.org/trac/wiki/Releases
After installing X11, VFX and OP-X PRO-II re-boot your system. It has been reported that possible crashes
have disappeared after re-booting the system.
Since OS-X blocks apps not downloaded from the app store for security reasons you may
launch X11 manually for the first time. The same for VFX. So goto the applications folder,
right-click X11 and choose "open". Then quit it again. Do the same for VFX. Once launched
like this they should be unlocked and ready for normal launching via launchpad or dock.
If you can't see any OP-X PRO-II instrument interface after launching VFX then click
on the small white "vfx" icon on the top left and here in the list check "Show VST Editor".
The same can be done from the "Window" menu item in the top menu. Here "VST Editor" has
to be checked. Also, the instrument interface simply can be in the background of VFX
since it's processed by the separate X11 app. To bring it to the foreground click on
the X in the dock.
If you're using an external audio interface and have no sound then this is because VFX
always sends its audio to the system's standard output. This can't be changed within VFX,
so to make the sound of VFX come out of your external audio device you have to make it
the system's default output in the OS-X audio/midi settings. In order to do this launch the OS-X
audio/midi setup from applications->utilities or in the launchpad from "other". As you can see the black
speaker icon is on headphones/internal which is the standard output. To change it to your
external audio interface right-click its entry and choose "use this device for sound output".
32. Cubase Pro 8: OP-X PRO-II not listed anymore after updating to Pro 8. Any help?
Based on our research Cubase Pro 8 has a bug which lets it forget former added VST pathes. They are
still listed, but Cubase doesn't take any notice of them. The fix is easy: From the top menu goto
"Devices->Plugin Manager", and here at the bottom left click on the cogwheel symbol. Here your custom
pathes are listed. Now to make Cubase again recognize all of them click on the refresh-icon (circle arrows)
on the top right. Then Cubase again will use and scan the custom pathes, and OP-X PRO-II should be listed again.
33. A button or knob is moving by itself on certain actions. Any help?
If this is the case you probably unintentionally learned the knob or button to a CC the action which
causes the movement is sending out, or the pre-mapped CC matches this CC. As a temporary measure to stop
it you can block all incoming CCs by setting the left button below PROCC in the grey top bar from
RCE (=receive) to BLO (=block) by clicking three times on it. For a permanent solution, if you don't
use any custom CC mappings (so if you haven't learned controls by yourself), you can do a full reset
of the CC mapping to its default state by clicking the RES button below LEARN in the grey top bar (so
the right one) and hold it depressed for about 4 seconds until the blue led in the lever's section flashes
red. But note that this also will re-set all other potentially existing custom mappings. If you use a custom
mapping or if the knob still moves after the full reset you could simply learn it to a different CC, or use
the full CC blocking described above. In the Mac and x64 versions you also can unlearn the single control
by clicking on the LEA button below LEARN in the grey top bar, move the knob and then click on the RES
button on the right. You also might check why the external action is sending out a controller message.
Don't hesitate to contact us by email if your question could not be answered here.
Contact us
