You can contact support here if nothing here sorts you out.
When I try to install the plug, the installer tells me me that my key is invalid.
I've lost my plug-in registration key.
Which standard are supported?
My plug-in does not seem to receive MIDI.
When I load a preset from the "load" button, the sound does not change.
What's the best way to save my presets?
How do I send these mysterious NRPN MIDI commands to adjust LFO phases?
The plug-in does not pass AU validation.
The plug-in crashes validation.
The plug-in crashes the host
I experience cracklings and CPU spikes using Melohman synthesizers
The installer reports an error while installing.
Make sure that your email is correctly entered. If you think that password is wrong or if you can't remember it, there is an option to recover it (see below).
You can have your password sent to your email using the "Forgot password?" option in the Login box.
First of all, make sure that your purchases are registered. Log in to your site account and register all your Ohm Force products. Then click on your username to go to your products'page. Here you will find available installers (pack license offers all existing formats and free upgrades) for registered products.
Open the plug-in to register, and select 'register' in the setup menu of the plug-in. You can also register here.
Be sure to enter both username and keycode as they were sent to you. If you received authorization by e-mail, please copy/paste those two informations. If you are using a boxed version, check for letter 'O' and number '0', as well as letter 'I' and number '1'
If your plugin is already registered, then just log in and go to the list of your products. You will be able to have it sent to your email. If you never registered your product, please contact us giving us as most details (invoice number is perfect) about your purchase as you can.
We sell and provide customer support for the following formats (for the non legacy products):
When available you can also download other deprecated standards (RTAS for instance) but we don't provide support on those. And as stated, we also don't provide support for the legacy plugins.
In the plug-in setup menu, check the MIDI input device. It should be set to VST (or AU) MIDI in if you want to receive MIDI from the host.
You can choose any other MIDI device as long as it's not used by another application (or the host).
Our preset files are in fact bank presets files. Use the 1-8 buttons to activate a particular preset.
Using the new Ohm Force system to save your presets allows you to :
- use them on any other platform (be it AU, VST, AAX, Mac, PC...)
- benefits from extra data - description, and if you're willing to, images
That being said you may prefer to use DAW level presets, especially if using Maschine and NKSFX format.
Let's suppose you want to send the NRPN command number "k". NRPN data are actually specific Control Change (CC) commands. You have to send at least 3 of them to constitute one NRPN command, in this order :
To know the NRPN-LFO associations, check your product's manual.
If you're using a legacy plugin the most likely cause is a mistake in the manual install process (which is admittedly painful). If using a product from the new line (Ohmboyz Infinity and later) please download the latest version of the plug-in. If it still does not pass validation, please send the validation report here.
If using a product from the new line please download the latest version of the plug-in. If it still crashes validation, please send the validation report and the crash log here. The crash log can be found in your ~/Library/Logs/Crash Reporter/ folder. The file to send is the file which name contains something about auval.
Please download the latest version of the plug-in. If it still crashes the host, please send the crash log here. The crash log can be found in your ~/Library/Logs/Crash Reporter/ folder. The file to send is the file which name contains the host name.
Open the Energy Saver options panel, and set the CPU to "Highest". Contact the mac support if the problems persist.
Search for the installer log, open it with a text editor.
Cubase is sometimes overzealous in blacklisting plugins. If that happens to you, simply open the plug-in manager and white list them. See Cubase documentation if needed.