products reviews buy news support
OP-X PRO-II out!      Click here for infos!
description     flashdemo     vst-version     reaktor-ens     comparison     audioclips     testimonials     purchase     freedemo
Frequently Asked Questions related to OP-X PRO-II version 1.2 Mac and Win x64

For questions regarding version 1.1 (32bit) visit this FAQ:   click here
For more general help topics visit the main support site:   click here

Frequently asked questions:

1. OS-X: When I doubleclick the installer OS-X is blocking it. Any help?

2. Windows 8: When I doubleclick the installer Windows SmartScreen is blocking it. Any help?

3. Mac: The sequencers don't see OP-X PRO-II after installation. Any help?

4. Mac: Ableton Live doesn't see OP-X PRO-II although the system is supported. Any help?

5. Mac: When I jump to the lower field the entered text in the upper field disappears. Any help?

6. When I enter my license key and click on "enter key" nothing happens. Any help?

7. When I try to paste my key it says "no items available in the clipboard". Any help?

8. MAC: No matter what I do I always get an invalid user id/license key message. Any help?

9. After successful licensing the licensing window remains on top and there's no sound. Any help?

10. After licensing some parts of the entered text remains on the interface. Any help?

11. Do I need to remove the demo version before installing the full version?

12. When I click on BANK > LOAD I can see no banks to load. Any help?

13. When I click on PRESET > LOAD I only can see five presets. Where are the 2'500 presets?

14. After loading a bank there's suddently distorted sound. Any help?

15. My former fxp presets and fxb banks aren't seen and can't be opened. Any help?

16. OP-X PRO-II VFX Edition: How can I load my custom sounds in the new AU and VST3 versions?

17. Presonus Studio One: When I switch patches the sound doesn't change. Any help?

18. When I try to enter a space character in a text field nothing happens. Any help?

19. After installing windows says "this program might not have installed correctly". Any help?

20. When I click on the "COPY" button nothing happens. Any help?

21. MIDI program changes have no effect in version 1.2 of OP-X PRO-II. Any help?

22. I read there was a new bank release. Where can I download newly released banks?

23. Apple MainStage: Saved patches aren't recalled. Any help?

24. OS-X Yosemite and Mavericks: The GUI occasionally freezes during playing. Any help?

25. MAC: Installation fails or the plugin can't be found after installation. Any help?

26. The synth seems to be completely out of tune when I play it. Any help?

27. Bitwig Mac: Is there a way to run OP-X PRO-II athough VST2 isn't provided for Mac?

28. Windows: The installer doesn't start after skipping SmartScreen and seems to hang. Any help?

29. Mac: OP-X PRO-II is crashing Ableton Live when trying to create a track. Any help?

30. When changing the sample rate OP-X PRO-II is being re-set to the default patch. Any help?

31. Ableton Live Mac: Unlearn not working and jumping when switching presets forward. Any help?

32. Does OP-X PRO-II work in OS X 10.11 El Capitan or do I have to expect issues?

33. I installed 1.2.1 or 1.2.2 but the blue startup screen only still shows 1.2. Any help?

34. When I click on the right list button the preset list remains frozen on top. Is this a bug?

35. I only can see 128 presets. Where are the 2500 presets that were claimed to be included?

36. Does OP-X PRO-II work in macOS Sierra? Can I upgrade my system?

37. There seems to be inaccurate timing in Logic Pro X sometimes. Any help?

38. Ableton Live: Pitchbend and modulation events flood the undo list. Any help?

39. A button or knob is moving by itself on certain actions. Any help?

40. Recalling a session: Recalled sound is preset 1 and bank not recalled. Is this a bug?

41. Windows: Version 1.2.5 sometimes crashes on instantiation. Any help?

 

1. OS-X: When I doubleclick the installer OS-X is blocking it. Any help?

If Gatekeeper is active OS-X will block normal double-click installation of downloaded software not coming from the Appstore.

To install right-click / ctrl + click the installer and choose "Open" from the context menu. In the upcoming warning window then once more confirm by clicking "Open". For details read page 3 of the pdf manual.

 

2. Windows 8: When I doubleclick the installer Windows SmartScreen is blocking it. Any help?

Upon double-clicking the installer in Windows 8 after downloading there can arise the following message: "Windows protected your PC - Windows SmartScreen prevented an unrecognized app from starting. Running this app might put your PC at risk."

Don't worry, there's no risk at all. To execute installation click on "More info" and then click on the left button saying "Run anyway". Then installation will start.

If the installer doesn't launch immediatly after having skipped smartscreen this may be caused by your virus scanner scanning the installer. If so simply wait until it's done. This sometimes can take longer than one would expect. If it shouldn't launch at all afterwards even after waiting 5 minutes or so then temporarily deactivate your virus scanner for installation. No worries, as said our installers are clean and save and don't wirite any system files. They just place the plugins to the correct places and the needed SonicProjects data folder to the public documents folder. So nothing hidden. Also all our installers have been pre-scanned and examinated by a virus scanner.

 

3. Mac: The sequencers don't see OP-X PRO-II after installation. Any help?

If this is the case the OS-X version in your mac probably is older than 10.8.0 and doesn't support OP-X PRO-II. The minimum OS-X version supported by OP-X PRO-II is 10.8.0 (Mountain Lion). To check the version number of your system click the apple icon at the top left of the finder bar and choose "About This Mac". If your computer's hardware supports it you can update your system by downloading a newer OS-X version from the Appstore.

If your OS-X version is 10.8 or newer and the plugin nevertheless isn't listed then it probably simply wasn't scanned yet. Based on our experience you sometimes need to launch Logic Pro X twice until it will be scanned. Once scanned it sould appear in AU Instruments->SonicProjects->OP-X PRO-II. In Ableton Live be sure to activate AU support (see question 4) since Ableton only can use the AU version of the plugin since Live doesn't support VST3 at this date (date of this writing: version 9) which is the VST version we provide for Mac.

 

4. Mac: Ableton Live doesn't see OP-X PRO-II although the system is supported. Any help?

Since Live doesn't support VST3 and OP-X PRO-II for Mac only is offered in VST3 and AU format you have to use the AU version in Live. The use of AU plugins by default is deactivated in Live. To activate it goto Live > Preferences > File/Folder, and here below "Plug-In Sources" set "Use Audio Units" to "On". Then OP-X PRO-II should be immediatly listed under Plug-Ins > SonicProjects.

 

5. Mac: When I jump to the lower field the entered text in the upper field disappears. Any help?

In some sequencers like Logic Pro X you need to confirm the entered text by hitting the "Enter" key. So after entering your user id in the upper field hit the "Enter key" to confirm the entry, then the entered text will remain when you click into the lower field to enter the key.

It may be necessary to do the same in the lower field too. So after entering the key in the lower field hit the "Enter key" once more to fix the entered text.

 

6. When I enter my license key and click on "enter key" nothing happens. Any help?

When nothing happens upon clicking on "enter key" this means the key hasn't been entered correctly or completely. Be sure to enter the whole expression that can be found below the "User ID:" headline in your license mail, not just a number. To avoid typing mistakes use copy and paste (windows: copy: Ctrl + C, paste: Ctrl + V, mac: copy: cmd + C, paste cmd + V). If paste doesn't work then right-click (mac ctrl + click) into the field and choose "paste".

 

7. When I try to paste my key it says "no items available in the clipboard". Any help?

This can be the case if your host uses "always on top" windows or blocks entering characters by keyboard because they're used as sequencer shortcuts. In this case simply right-click (mac: ctrl + click) into the field and choose "paste".

 

8. MAC: No matter what I do I always get an invalid user id/license key message. Any help?

Confirm the entered data in both fields with the computer keyboard's enter key after entering the data before you proceed. So like this:

1. Enter user-id expression in upper field
2. Hit enter
3. Enter key in lower field
4. Hit enter
5. Now make sure no field is highlighted anymore (click somewhere outside if so)
6. Only now click on the "Enter Key" button

Then licensing should work. If you get a "thank you for registering!" and there's still no sound and the licensing window remains on top then uninstantiate and re-instantiate the synth.

If licensing still shouldn't work then try to paste the data using right-clicking the field and choosing "paste" from the context menu instead of using cmd + V. Alternatively you also could try to enter the data manually. Also using these entering methods follow the steps above. If it still shouldn't work then try to license within a different host/sequencer.

 

9. After successful licensing the licensing window remains on top and there's no sound. Any help?

If this is the case and you had a "thank you for registering!" message before then you simply have to re-instantiate the synth once until it will finally start working. So either quit and re-launch your sequencer or un-instantiate the synth and re-instantiate it.

This behaviour means the synth actually was successfully licensed, but it was not be able yet to read the license data on the fly. We only observed this behaviour in Cubase Pro 8 Windows so far. Based on our experiences it depends on how you paste the license data. If you paste it by right-clicking and choosing "paste" this behaviour isn't there anymore and the synths starts working immediatly after licensing.

 

10. After licensing some parts of the entered text remains on the interface. Any help?

If this happens (e.g. can be the case in Reaper) simply click somewhere on the GUI and the text will disappear. If not close and re-open the interface.

 

11. Do I need to remove the demo version before installing the full version?

No. If you still have the demo version installed you simply can install the full version over the demo version which will replace it., so no need to delete it first. If you re-install the Presetbase too eventual newly created banks and presets won't be overwritten and can be furthermore used with the unlimited full version. Of course you don't necessarily need to re-install the presetbase if you already installed it with the demo version. But in the end it doesn't make a difference.

 

12. When I click on BANK > LOAD I can see no banks to load. Any help?

First of all make sure you have installed the "Presetbase". If the bank load button doesn't point to its banks folder by default, which can happen if you e.g. loaded or saved stuff with your sequencer and pathes got messed up, then simply click all 4 load/save (banks/presets) buttons once which should reset the path. If not then again go to the correct places manually by browsing folders. The correct load/save pathes are:

PC - Banks:

C:\Users\Public\Documents\SonicProjects\OP-X PRO-II\Presetbase\Banks

PC - Presets:

C:\Users\Public\Documents\SonicProjects\OP-X PRO-II\Presetbase\Presets

Mac - Banks:

/Users/Shared/SonicProjects/OP-X PRO-II/Presetbase/Banks

Mac - Presets:

/Users/Shared/SonicProjects/OP-X PRO-II/Presetbase/Presets

 

13. When I click on PRESET > LOAD I only can see five presets. Where are the 2'500 presets?

There are only some basic init patches available as single presets. All other presets (about 2'500) are collected in banks (66 in total) which can be loaded using the BANK > LOAD button.

 

14. After loading a bank there's suddently distorted sound. Any help?

This can happen when anything went wrong during loading the bank. In this case simply load the bank once more and the sound again should be clean.

UPDATE: This shouldn't happen anymore in the newest 1.2.5 version.

 

15. My former fxp presets and fxb banks aren't seen and can't be opened. Any help?

The new version 1.2 64bit VST2/VST3/AU version of OP-X PRO-II uses a new proprietary patch format (opxpreset and opxbank) which is independent from plugin-format (vst2/vst3/au) and platform (mac/win). In order to use your former custom fxp presets and fxb banks you need to transfer them to the new format. Your user area offers dedicated plugins for this.

Note you only need to transfer your own custom sounds since all factory banks and all banks from the download page available at the date of the 1.2 release (September 2015) already have been converted by us and are available ready-to-load in the new presetbase which is included in the installers. New coming bank reloads will be offered in both the new and the old format.

 

16. OP-X PRO-II VFX Edition: How can I load my custom sounds in the new AU and VST3 versions?

Your user area offers a special patch transfer plugin "Patchtransfer VFX" which can transfer your custom patches to the new format needed. There's a detailed pdf guide as well a supporting video showing all steps.

Note that all factory banks and all free downloads released until the date of the native Mac version release (September 2015) already have been converted by us and are available ready-to-load included in the "Presetbase" provided in the VST3/AU installer.

 

17. Presonus Studio One: When I switch patches the sound doesn't change. Any help?

In Presonus Studio One the patch manager doesn't work in VST3. The knobs and buttons change, but the sound doesn't because of a Studio-One-only specific behaviour regarding handling of parameter access. But it's only VST3 that's concerned, in the VST2 (win) and AU version (mac) the patch manager works fine.

So in Mac simply only use the AU version instead, and in Windows only install and use the VST2 version. Note that Studio One only lists the VST2 version when the VST3 isn't installed, otherwise only the non-working VST3 is listed. If you already installed the VST3 then simply again delete it by deleting the "OP-X PRO-II" folder in C:\Program Files\Common Files\VST3. Then Studio One will list the working VST2 version. In Mac both the VST3 and the AU are listed in Studio One, so you don't need to remove the VST3 here. Simply only use the AU version.

UPDATE: In the newest 1.2.5 version the VST3 patch manager now works in Studio One.

 

18. When I try to enter a space character in a text field nothing happens. Any help?

In some sequencers the space bar key is tied to sequencer control (start and stop) even when editing a plugin. So pressing the space bar key actually will start playback instead of entering a blank space character. The only way to work around this is copying the space character from a text editor using ctrl + c and then paste it in the field using ctrl + v or if paste doesn't work by right-clicking the field and choosing "paste". You of course also can copy and paste the whole text you want to enter instead of just the non-working space character.

 

19. After installing windows says "this program might not have installed correctly". Any help?

Simply ignore this. Choose "this program installed correctly".

 

20. When I click on the "COPY" button nothing happens. Any help?

In version 1.2 the former COPY button has a new function. It "freezes" edits so that they remain after switching presets in a bank. If it's not applied the edits get lost and again the original unedited patch will be loaded after switching presets. This was on top of the wishlist by many OP-X PRO-II users. Since the COPY button anyway was used very rarely if at all we gave this button this new function (copy changed settings to the bank's preset slot). Of course you also can "keep" an edited patch by simply saving it as single preset. You don't need to freeze it before for this.

In the newest 1.2.5 version the COPY button now also "freezes" changes of the patch name into the bank, which formerly remained after changing presets.

 

21. MIDI program changes have no effect in version 1.2 of OP-X PRO-II. Any help?

The new cross-platform 1.2 engine of OP-X PRO-II is built around the newest VST3 SDK which doesn't support program changes. That's why direct MIDI program changes don't work anymore in version 1.2. To compensate this shortcoming we however implemented no less than 4 different very sophisticated ways to switch programs using MIDI Controllers. It e.g. even is possible now to do increment/decrement (toggle presets forwards and backwards) by MIDI CC. All of these new features make remotely controlled program changes even more comfortable than before. Read page 85 ff of the new pdf manual to learn all about the new methods.

 

22. I read there was a new bank release. Where can I download newly released banks?

New bank reloads are placed for free download on the sound reloads page which is:

http://www.sonicprojects.ch/opxpro2/userarea.html

The newest reloads always are placed at the very bottom. Note the new 1.2 64bit VST2/VST3/AU version of OP-X PRO-II already includes all reload banks released until September 2015 (exept for the "Former OP-X PRO library") in its installed library ("Downloaded" folder), so you don't need to re-download these. Of course it's nevertheless useful to read the dedicated infos and to listen to the clips to get an idea what the banks do. Beginning at September 2015 we will release all new bank reloads in both the old fxb format for version 1.1 32bit and the new opxbank format for version 1.2 x64 and Mac at the very bottom of the reloads page.

 

23. Apple MainStage: Saved patches aren't recalled. Any help?

This issue has been fixed in the newest 1.2.2 version.

Former issue description for documentation: Upon recalling a concert using OP-X PRO-II MainStage only recalled a saved patch when it was selected/active. In not selected/inactive patches OP-X PRO-II lost its patch setting and was re-set to the default patch.

UPDATE: The issue unfortunately again is there in the newest MainStage 3.2.4. We'll investigate to solve the issue.

UPDATE: We finally were able to solve the issue in the newest 1.2.5 version.

 

24. OS-X Yosemite and Mavericks: The GUI occasionally freezes during playing. Any help?

Based on our own long-time testing this occasionally can happen in OS-X Yosemite, rarely also in Mavericks. It's not yet clear if it's Yosemite to blame or something else. But fortunately it's not that severe since it doesn't affect functionality. When the GUI freezes it just simply doesn't re-draw anymore. You still can operate the GUI and change settings and patches - you simply only can't see what you do since the GUI remains at the frozen setting.

To make the frozen GUI work again simply close and re-open it. Then it again will work and also will show the changes you've done while it was frozen if so. If these freezes occur too often then deactivate the virtual keyboard and voice LEDs animation by switching the blue square button next to "A" in the levers section to off. This will stop the keyboard animation and voice LEDs flashing which takes off load from the GUI processing. This doesn't affect functionality in any way. You even still can play the virtual keyboard with the mouse. With deactivated animation there won't be any freezes anymore.

In the new OS-X 10.11 El Capitan we haven't seen this issue occur so far during our long time tests. So it seems that Apple has improved some stuff related to graphics in El Capitan. Which means we can recommend to upgrade to El Capitan if you plan to do this.

UPDATE: The freeze issue too isn't there in the new macOS Sierra. So the best measure to get rid of it is upgrading to El Capitan or Sierra which both seem to have better and more stable graphic performance than their predecessors.

 

25. MAC: Installation fails or the plugin can't be found after installation. Any help?

This issue has been fixed in-place in the concerned installers shortly after it was reported to us. Only the very first installers were concerned. So either re-download them (1.2) or use one of the newer versions. Former issue description for documentation:

We made a mistake in the Mac installers, both demo version and full version, but differently. Until we fixed it simply don't uncheck/unselect items on installation, so install both the VST3 and AU version. You can delete stuff manually after installation if you don't need it.

In the demo version installer we by mistake interchanged the items' labeling. So if you check AU the VST3 plugin will be installed, and when you check VST3 the AU plugin is installed. Silly mistake and confusing if you don't know about it. But it doesn't affect functionality of the plugins. As falsly supposed by some the VST3 and AU plugins aren't dependent on each other. So you can delete the items you don't need after installation.

In the full version installer we by mistake have put the wrong pre-installation and post-installation scripts (which create folders and set the correct access rights) to the wrong items (the ones for VST3 to AU and vice versa). That's why installation fails when you only check the AU version, and when you only check the VST3 version a non-openable (missing access rights, labeled with a red minus) VST3 folder is created if no one exists already. If done so again delete the folder manually (only if you didn't have a VST3 folder before and it can't be opened, labeled with a red cross), and again repeat installation without unchecking any items until we fixed it.

UPDATE: Both installers have been fixed now (date: Sunday October 4 19:30 MEZ). Please delete the old ones are re-download them. Full version Mac installer: If you only have installed the VST3 version and had no VST3 folder before then you will have a non-openable VST3 folder marked with a red dot in the bottom right corner. (see pic below). If so delete this folder and re-install the plugin.

 

26. The synth seems to be completely out of tune when I play it. Any help?

This bug has been fixed in version 1.2.1. Former issue description for documentation:

There's unfortunately a bug that makes the synth go out of tune and change brightness/timbre when not used at the standard 44.1 kHz sample rate - proportionally to the sample rate. Since also the sound is changed this can't be corrected by adjusting the master tune knob.

We know that's a severe issue for people working at other sample rates than 44.1 kHz, that's why we posted it as warning everywhere. Unfortunately we weren't aware of it. We'll try to fix it as soon as possible. So until it's fixed only use the synth at 44.1 kHz.

UPDATE: The sample rate tuning issue has been fixed in the newest 1.2.1 version

 

27. Bitwig Mac: Is there a way to run OP-X PRO-II athough VST2 isn't provided for Mac?

Yes. A customer of ours reported that OP-X PRO-II can be run in Bitwig Studio using the free meta-plugin "Minihost Modular" from Image-Line.

Stability doesn't seem to be perfect, but at least it's a way to use it without any additional costs. Bitwig announced they plan to support AU anytime in the future which would solve the problem. Here's the product site of Minihost Modular:

http://www.image-line.com/documents/news.php?tag=minihost+modular

There are also commercial meta-plugins like DDMF Metaplugin and Blue Cat PatchWork which allow to host plugins in various different formats and also are able to target other not supported formats like RTAS and AAX.

 

28. Windows: The installer doesn't start after skipping SmartScreen and seems to hang. Any help?

If this happens this is highly probably caused by your virus scanner which tries to scan the installer file while it already was launched by Windows after skipping SmartScreen. The two dedicated cases reported to us were caused by Avast, and the installer started fine after deactivating Avast.

So if this should happen to you simply temporarily deactivate your virus scanner for the time of installation, and before again launching the inastaller kill possible open instances in the task manager (ctrl + alt + del). Our installers are 100% clean and are being tested numerous times in all supported windows systems (Windows 7, 8, 8.1, 10) before they're uploaded, so they're proven to work fine if they're not stopped by 3rd-party software. They also don't access any system areas and not even the registry. All they do is copying the plugins to your plugin folders and writing the needed SonicProjects folder including the sounds to the public documents folder. So it can't harm your system in any way. There are no hidden files. If you nevertheless want to go sure then scan the installers manually before installation and then deactivate the scanner during installation if the scanner blocks the installer.

UPDATE: In most cases this process delay seems to be caused by the virus scanner scanning the installer which often can take some time. If so simply wait until it's done, and only use the described above measure of temporarily deactivating the virus scanner if the installer won't launch even after 5 minutes or so.

 

29. Mac: OP-X PRO-II is crashing Ableton Live when trying to create a track. Any help?

If you have this then update Ableton Live to the newest version and also make sure to use the newest version of OP-X PRO-II. Based on customer reports this possible issue has been fixed in Live 9.5. On our side we however never could replicate the issue even in lower versions of Live and different systems, so it may depend on the exact setup.

 

30. When changing the sample rate OP-X PRO-II is being re-set to the default patch. Any help?

Don't change the sample rate during a running session. If you want to work at a different sample rate then change the sample rate before you launch the session, respectively if you change it while the session is opened then after changing it quit the sequencer (without saving before!) and launch the session anew. Also make sure your audio interface actually is set to the same sample rate as the session is set to. Professional interfaces will normally sync up automatically, but not all interfaces do. Also be sure to render using this sample rate then and not at a different one. You never should mix up sample rates. Some plugins may forgive this, but using audio you would have changed pitch or quality loss caused by eventual resampling doing this. OP-X PRO-II has to re-initialize all its components to the new sample rate when you change the sample rate which causes it to be re-set to its default state. That's why you can't change the sample rate during a running session unlike you're willing to loose your settings and load the used sounds anew. But changing the sample rate during a running session anyway is an absolute no-go, and also different rates never should be mixed. Also be aware that using higher sample rates will consume more cpu, which could lead to crackling if you don't have enough cpu overhead or if you don't rise the used buffer size accordingly. So make sure if you really need higher sample rates. The difference in sound in most cases is hardly perceptible in the end, and this at the price of a dramatically increased cpu load and also a dramatically increased use of hard disk space when working with audio.

 

31. Ableton Live Mac: Unlearn not working and jumping when switching presets forward. Any help?

This is not fully resolved yet but it seems that it's caused by Live feeding the MIDI output of the plugin back into the input.

But you easily can stop the faulty behaviour by deactivating the MIDI output of the plugin. For this set the right button below PROCC in the grey top bar from OUT to BLO (=block) by clicking once on it. Then MIDI unlearn and increment/decrement (jumpy behaviour only is there when they are learned) again will behave correctly. We'll try to fix the bug in future updates so that these functions also act correctly in Live without the need to deactivate the MIDI output.

UPDATE: This issue is fixed now in the newest 1.2.5. version.

 

32. Does OP-X PRO-II work in OS X 10.11 El Capitan or do I have to expect issues?

OP-X PRO-II has been tested in EL Capitan in Logic Pro X and Ableton Live and some other sequencers and it works fine. There are no audio unit scanning issues initially reported by some plugin companies, and there haven't been any even in the initial release edition of which was the version which made problems with some. To our knowledge possible issues with some other plugins mentioned above have been fixed in the newest update of El Capitan. But you may check with the dedicated manufacturers. Based on our testing so far El Capitan seems to be the better and more robust system than Yosemite.

 

33. I installed 1.2.1 or 1.2.2 but the blue startup screen only still shows 1.2. Any help?

The sub-version unfortunately isn't shown in 1.2.1 and 1.2.2 on the blue startup screen, only still 1.2. We will change this in the future. But the installers are fully labeled. So if you're not sure if you have the newest installed simply install it once more. You also can easily find out if you have 1.2.2 by loading a single preset, close the GUI and re-open it. When the displayed preset name of the before loaded preset still is there then you have 1.2.2. When the name got lost and returned to what it was before then you have an earlier version.

UPDATE: In the newest 1.2.5 version the sub-version is displayed now in the full version.

 

34. When I click on the right list button the preset list remains frozen on top. Is this a bug?

This is no bug but conceived to be like that. There's a reason why there are not only one but two list buttons: The left one launches a temporary list which again disdappears once you picked a preset from it. That's probably what you're used to from other synths. The right list button however launches a sticky list which remains opened until you click a second time on the right list button. This can be handy to browse around a bit in the preset list and quickly check sounds without having to re-open the list everytime again after having chosen a preset. So since there are both options you're free which one to use. You even can make the temporary list launched with the left list button sticky/always on top too after launching by simply clicking the right list button.

 

35. I only can see 128 presets. Where are the 2500 presets that were claimed to be included?

The 128 presets you can see after loading the synth just are the presets of the factory default bank. To load one of the many included banks click on the BANK > LOAD button in the grey top bar. This will present you a total of 66 banks including about 2500 sounds in total. The root folder contains the basic soundset (32 banks) while the two subfolders contain another 34 banks. The "Downloads" subfolder contains all the additional banks released on the sound reloads page that were published before October 2015. For the 32bit windows version these still have to be downloaded, while they already are included in the newer Mac and x64 versions. We however will keep on releasing further new reloads in the future which then too have to be downloaded for the Mac and x64 version. The "Extrabanks" folder contains some surprise banks including some we used for various song demos. Generally, a bank can contain up to 128 presets, but some have fewer or just a few. Banks are useful to collect sets of presets in theme groups, which can be indicated by the name of the bank. E.g. the PROII_FAMOUS bank contains the famous 80s sounds. To return to the factory default soundset load the PROII_DEFAULTBANK bank. Single presets are mainly used to save your own custom single sound creations (PRESET > SAVE), for later loading or to create your own custom banks somewhen. For this you can load the PROII_EMPTY bank, load your before saved single presets into it in any order you like, and then save the bank using a custom name of your choice. To keep things organized and group stuff or separate your own sounds and banks from the factory ones you are free to create subfolders in both the banks and presets folder. To learn more about the patch browser and creating sounds read the dedicated section in the synth's pdf manual.

 

36. Does OP-X PRO-II work in macOS Sierra? Can I upgrade my system?

Based on our first basic testing in os Sierra 10.12.1 everything seems to be fine. AU validation passes and the plugin works in Logic Pro X 10.2.4 and Ableton Live 9.7. We tested with the newest 1.2.2 version of OP-X PRO-II. We however didn't have the time yet for any sort of long time testing. Also we tested in a clean installation of osSierra (no upgrade, macOS Sierra installed to a separate partition) and only in a MacBook Pro Retina mid 2015. But osSierra seems to be not much different regarding basics than the former 10.11 El Capitan, and in this sytem the synth always has worked perfectly, regarding graphics actually better than in 10.9 and 10.10.

UPDATE: In the meantime we found the time for some more deeply testing. These's one small bug which occurs in macOS Sierra 10.12.1 which wasn't there in the previous OS-X El Capitan 10.11.x: If you somewhen during the session saved a single preset or a bank with OP-X PRO-II's patch manager or even just clicked PRESET->SAVE or BANK->SAVE and aborted saving the host will put out an error message after quitting saying "Logic/Live whatever quit unexpectedly". This wasn't the case in 10.11 so it's probably an early version Sierra bug which might (hopefully) be fixed in coming updates. This is however a harmless bug and has no influence on your work. So at this time if there's no urge to update we recommend to still remain on 10.11 until this bug will be fixed. 10.11 is perfectly stable and based on our testing the most stable of the systems we support (10.8 - 10.12).

UPDATE1: We already found a fix for it which is included in the newest 1.2.5 version. So macOS Sierra is officially supported now.

 

37. There seems to be inaccurate timing in Logic Pro X sometimes. Any help?

This issue has been solved in the newest 1.2.5 update.

 

38. Ableton Live: Pitchbend and modulation events flood the undo list. Any help?

This issue has been solved in the newest 1.2.5 update. Pitchbend, modulation and CC 128 and CC 129 auxiliary events now don't go to Live's undo list anymore.

 

39. 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. As an immediate 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 default blank 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 delete all the other potentially existing custom mappings. If you use a custom mapping you also can unlearn the affected 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. Finally you also might check why the external action which caused the movement is sending out a controller message.

 

40. Recalling a session: Recalled sound is preset 1 and bank not recalled. Is this a bug?

No. This is conceived to be like that. The x64 and Mac versions can't save and recall a whole bank with a session as it was the case in the windows 32bit version which still worked with Steinberg's fxb format which could save whole bank chunks. The new versions use a new core technology which only allows to save and recall a single preset through the host. In the x64 and Mac versions banks are only simulated by the synth's own custom patch manager engine so that everything remains familiar for people who came from the former windows 32bit version. Also we think that banks are very handy for collecting and distributing patches since 128 patches can be grouped thematically and stamped into one single handy file. And banks somehow are good old oldschool synth's spirit as well. That's why we simulate them internally. When the synth is launched it always loads the defaultbank soundset in the background so that you immediatly have 128 presets available for switching through without having to load a bank first by yoursef. When a session recalls a sound we make this one overwrite the first preset of the loaded default bank so that you still could switch forth and back in the pre-loaded default soundset without losing the recalled sound. Of course, loading the default bank in instances of a recalled session in fact wouldn't necessarily be needed.

 

41. Windows: Version 1.2.5 sometimes crashes on instantiation. Any help?

Version 1.2.5 initially had a bug which could lead to a crash on instantiation, mainly at sample rates higer than 44.1 kHz, and only when there already were other tracks. This issue has been fixed "in place" in version 1.2.5 on March 27 2017. So if you downloaded it before this date delete the dowload, re-download it and install it over the existing one. Then the issue will be fixed. Note that only the windows version was concerned.

Don't hesitate to contact us by email if your question could not be answered here.

Contact us