Before sending a mail to our technical support please check these frequently asked questions to see if your issue is addressed here.
Please see details here: macOS 13 Ventura Compatibility
Yes, we’ve heard that Steinberg have announced that their products will stop supporting VST2 in the next 2 years. Don’t worry, by that time all our non-legacy instruments will have VST3 available.
More immediately is the announcement that Cubase 12 on Apple Silicon Macs doesn’t support VST2. It would seem that Apple Silicon Cubase users will receive best compatibility by running Cubase 12 in Rosetta mode:
https://helpcenter.steinberg.de/hc/en-us/articles/4488195658002-Cubase-12-Using-the-native-Apple-silicon-version
Where VST2 support is still continuing:
https://helpcenter.steinberg.de/hc/en-us/articles/4409561018258-VST-2-Discontinued
Please check your spam or junk folder before contacting support. If it’s not there, please contact support and we’ll happily reset your password manually.
Minimonsta and Oddity 2 will not work correctly on macOS Big Sur. They do however work on macOS Monterey, so please update to Monterey for compatibility.
All other GForce instruments work on Big Sur.
Unfortunately there is no PC AAX format for M-Tron Pro, VSM, Oddity2, impOSCar2 and Minimonsta.
Provided you have a license registered to your account, you can find your installation codes by clicking on the orange View Instrument buttons in your account.
Conversion to other currencies is handled by your payment provider.
We use this website for currency conversion indications when buying.
Yes, all our current instruments are available to download directly from this website.
For specific download instructions for VSM and M-Tron Pro please see their FAQ sections.
We offer educational pricing on all our products.
You will need to prove that you currently attend, or teach at, an educational establishment. If you feel that you could benefit from an educational discount please drop us a line.
We deal with all requests individually.
Please Note* Educational discounts can only be applied to full priced purchases and cannot be combined with any other offer.
Please create or log in to your account, you’ll find an option to register your serial number or Activation Code on the main account page.
In previous lives, serial numbers may be referred to as Registration keys or numbers. They’re the same thing.
As long as your product isn’t listed as “NFR”: In your account, click on the View Instrument button for the product that you’d like to transfer. You can transfer it to another registered GForce user using the box on the right-hand side. Or at the bottom on mobile browsers. The recipient’s licence is marked as NFR and cannot be transferred again.
Yes. On your account page.
Sometimes an over zealous spam filter may stop our email from getting to you. Try changing the settings and asking for the password to be sent again. If this doesn’t solve the problem, email us and we’ll provide you with your details.
All technical issues with regards to our instruments and Receptor are handled directly by Muse.
Upgrade – something you pay for.
Update – something you don’t pay for.
Did you buy the product from our website? If so, registration is automatic and there’s no need for you to do anything. So the number is taken… but by you! If you didn’t buy from us, contact support with your serial number.
Over the years we have used these terms interchangeably, causing some confusion. They are, however, the same thing.
Create an account, then register your activation code with us. You’ll then be given a serial number to use when installing the instrument itself. The activation code cannot be entered into the instrument.
Mac | Run the installer again (download a new one if you need to). When it comes to the installation selection screen keep clicking the tickbox until the text reads Uninstall. Do this for each format you want to uninstall then complete the installation process.
PC |Find the uninstaller in Add/Remove Programs and run.
New UI sizes are now available for M-Tron Pro and VSM. We’re looking into our development options for increased UI sizes with Oddity2 and Minimonsta.
We never pay artists for endorsements nor enter into an endorsement with an artist who has never used our instruments. Artists may be eligible to endorse our products provided they meet all of following conditions:
The artist must already own at least one GForce Instrument and express a genuine love for it.
The artist must prove popularity, e.g. have produced at least 1 top ten hit in a significant charts system in the last 24 months.
The artist must provide scans of at least 5 interviews in music oriented magazines, such as Groove or Bravo, alternatively video interviews on MTV or music shows on local television.
The artist must provide scans of at least 5 interviews published in magazines focussed on music production, such as Future Music, Electronic Musician, Keyboard, Sound & Recording or a combination of both magazine types.
If the artist has an existing or prior endorsement by another audio company (hardware or software), the artist must send signed confirmation that the existing or prior endorsements do not conflict with endorsement by GForce. For example, if the artist still has to mention an existing and prior product endorsed by another company he can not be endorsed by GForce.
The artist must provide prominent mention of GForce instruments in each booklet during the period of endorsement.
The artist agrees to mention GForce instruments prominently in any production centric interview within the period of endorsement.
The artist agrees to supply patches and demo tracks for inclusion in GForce products and use on the GForce website.
The artist must send a set of photographs (cleared for publishing by GForce), to be updated every 2 years.
The artist must provide a list of at least 5 appearances of GForce instruments on each album within the endorsement period, e.g. “Ambient background on track 02 using impOSCar2 preset ToDieFor”
Failure to meet any of the above conditions will result in termination of the agreement and any licenses that have been issued under this agreement will be revoked. GForce Software Ltd reserves the right to revoke any NFR license at any time for any reason.
The artist can end the endorsement period at any time by buying normal single user license.
Our licence agreement allows for up to two concurrent installations as long as both computers are owned (and mainly used by) the registered licence holder.
This is designed to allow users to have one installed on a studio and one on a live performance rig.
Yes. There are discounts available for registered owners of:
This discount will be automatically applied in the basket or checkout if you’re logged in.
Please note we’re aware of an issue that prevents the automatic discount from detecting second-hand or NFR licences. If this affects you please contact support to request the upgrade.
Further more, if you have two of the instruments listed above and one is second-hand (or NFR) and the other isn’t, you may then see the wrong upgrade price. In this case, contact support.
No. M-Tron Pro IV does not replace M-Tron Pro (v3 or older) in your DAW or projects automatically. They can run together simultaneously and even share the library files on your computer.
Yes it can! If you have your M-Tron Pro patches saved as a .mtron file, do this:
On Mac, if you have your M-Tron Pro patches saved as a .aupreset file, you can do the same as above. But those patches will be initially found here: ~/Library/Audio/Presets/GForce/M-Tron Pro
No. M-Tron Pro IV will detect any pre-installed library from earlier versions and immediately start to use it without the need to redownload and install a new Library.
The cpt2 file will be added directly to your library folder and the patches and tapes added into the browsers.
Yes. You can find detailed instructions for how to do this here.
This is likely to be either because you’ve not installed the library yet, or because you first ran M-Tron Pro IV before installing the Library.
The library is a separate download and installation available from your account. After installing it, please reopen M-Tron Pro IV and click the refresh button in the Patch Browser.
If you’ve tried the demo you will have been using a reduced library file. Please log in to your account and download and install the full Library. After installing it, please reopen M-Tron Pro IV and click the refresh button in the Patch Browser.
Only patches which use installed Tape Banks are shown in your browser. If you have imported patches which use tape banks that are not in your library they will be imported but not visible. If you later install the correct library or expansion pack, they will show after a browser refresh. To refresh the browser press the cycling arrows icon.
It seems that a recent update to Logic Pro has broken certain aspects of the MIDI 2.0 converter in Logic that Minimonsta2 uses. We’re still evaluating if this is an error on Apple’s part, or if we need to update the instrument.
In any case, please open the MIDI settings in Logic Pro and disable MIDI 2.0. This will get it working again.
Minimonsta2 contains a raft of updates over Minimonsta. Including; new preset browser, macros, reverb, pulse width modulation, fully scalable UI with three skins, improved audio engine, and VST3 and Apple Silicon native support. See the product page for more details.
Yes. Registered Minimonsta owners will get a 50% discount on Minimonsta2 automatically applied in the basket.
Log in to your account and add Minimonsta2 to you basket to view the discount the basket page.
Yes, please find the manual online here:
https://www.gforcesoftware.com/user-manuals/minimonsta2
Or via the button in the Settings window of the instrument.
No. Minimonsta2 has many different features to Minimonsta, it would not successfully automatically replace Minimonsta in your DAW projects. As far as your DAW is aware these are two unrelated instruments.
Our recommendation is that you complete unfinished projects started with Minimonsta with Minimonsta and start new projects with Minimonsta2. Alternatively, you can save your Minimonsta presets and load them into a new Minimonsta2 track.
Yes. However it can only read the first sub-patch slot in a saved .mmm file.
To do this:
PC: C:\ProgramData\GForce\Minimonsta
Mac: /Library/GForce/Minimonsta
PC: Documents\GForce\Minimonsta2\User Patches
Mac: Users/~/Library/Audio/Presets/GForce/Minimonsta2
Minimonsta2 has two different modulation methods represented by glowing controls on the UI.
Sliders and Knobs that are glowing blue have some level of XLFO or XADSR modulation applied.
Parameters with green glowing markings can be controlled by a macro. They will only display during macro use.
Please see the manual for more on these two features.
Drag the crosshair from the macro you wish to use to the parameter you wish to control. After that you’ll need to set an amount of control. By default this is done with right-click and drag, but you can change this in the Settings window to either cmd/ctrl or alt-drag to suit you.
This is a known issue that occurs on Apple Silicon Macs after resizing Minimonsta2’s UI. If you close the UI and reopen it Logic will allow keystrokes to be sent to Minimonsta2. Until you resize it again of course!
Yes. If you purchased Minimonsta at full price on or after 1st December 2022 we will offer you a free upgrade to Minimonsta2.
Users who purchased Minimonsta directly from GForce should find Minimonsta2 automatically in their accounts. If you purchased Minimonsta via a 3rd party retailer please contact support@gforcesoftware.com with a copy of your purchase receipt and GForce account email address.
The original Minimonsta contained over 500 “meta-patches” which each contained 12 variants that we called sub-patches. These 12 sub-patches were all designed to work together with patch morphing.
As patch morphing has been replaced by Macros in Minimonsta2 we decided not to include all 6000+ sub-patches in Minimonsta. It would have filled the Minimonsta2 browser up with similar sounding patches with unnavigable names. So for the interest of clarity Minimonsta2 only contains the 1st patch in each of Minimonsta’s Meta-patches.
However, we do have all of the 6000+ meta-patches converted for Minimonsta2 tucked safely away. It’s a bit of a confusing mess, but if you would like a particular sub patch that you may have be using in an old track or you just liked, please get in touch with Technical Support and request the patch in question. Please provide the meta-patch name and the sub-patch slot if you can recall it.
It seems that a recent update to Logic Pro has broken certain aspects of the MIDI 2.0 converter in Logic that Oddity3 uses. We’re still evaluating if this is an error on Apple’s part, or if we need to update the instrument.
In any case, please open the MIDI settings in Logic Pro and disable MIDI 2.0. This will get it working again.
Oddity3 contains a raft of updates over Oddity2. Including; new preset browser, macros, distortion, independent VCO2 glide, fully scalable UI with three skins, improved audio engine, and VST3 and Apple Silicon native support. See the product page for more details.
Yes. Registered Oddity and Oddity2 owners will get a 50% discount on Oddity3 automatically applied in the basket.
Yes, please find the manual online here:
http://gforcesoftware.com/user-manuals/oddity3
Or via the button in the Settings window of the instrument.
No. Oddity3 has many different features to Oddity2, it would not successfully automatically replace Oddity2 in your DAW projects. As far as your DAW is aware these are two unrelated instruments.
Our recommendation is that you complete unfinished projects started with Oddity2 with Oddity2 and start new projects with Oddity3. Alternatively, you can save your Oddity2 presets and load them into a new Oddity3 track.
Yes, if you have your Oddity2 presets saved in either .aupreset or the native .pbk format.
Move the .pbk or .aupreset files into your Oddity3 user preset folder and click the refresh button in the browser (the cycling arrows). Oddity3 will detect Oddity2 presets and ask if you’d like to convert them to the new Oddity3 format.
Please note that Oddity3 already contains all Oddity2’s factory patches.
User preset default locations:
Mac: ~/Library/Audio/Presets/GForce/Oddity3
PC: Documents\GForce\Oddity3\User Presets
Oddity3 has two different modulation methods represented by glowing controls on the UI.
Sliders and Knobs that are glowing blue have some level of XLFO or XADSR modulation applied.
Parameters with green (or purple on the MkI skin) glowing markings can be controlled by a macro. They will only display during macro use.
Please see the manual for more on these two features.
Drag the crosshair from the macro you wish to use to the parameter you wish to control. After that you’ll need to set an amount of control. By default this is done with right-click and drag, but you can change this in the Settings window to either cmd/ctrl or alt-drag to suit you.
This is a known issue that occurs on Apple Silicon Macs after resizing Oddity3’s UI. If you close the UI and reopen it Logic will allow keystrokes to be sent to Oddity3. Until you resize it again of course!
Oddity3 was rebuilt from the ground up as a dedicated instrument plugin. We’re sorry that this focusing has meant that we’ve not created an FX version.
Yes. If you purchased Oddity2 at full price, or upgraded to Oddity2 from Oddity 1, on or after 1st August 2022 we will offer you a free upgrade to Oddity3.
Users who purchased Oddity2 directly from GForce should find Oddity3 automatically in their accounts. If you purchased Oddity2 via a 3rd party retailer please contact support@gforcesoftware.com with a copy of your purchase receipt and GForce account email address.
NOTE: The import button is only visible on an expanded SEM.
Please update to Oberheim SEM version 1.0.3 or newer for Ventura compatibility.
View Downloads (login required)
Oberheim SEM is our first instrument without a physical or PDF manual. You can find the new manual here.* Or via the “Online Manual” button in SEM’s information screen.
*External site will open in a new tab.
The core sound-creating engine is the same as OB-E’s. However SEM has a few tricks OB-E doesn’t have, things we thought worked well for a mono specialist, like an arpeggiator and simple but powerful 32 step sequencer. It can also do different portamento rates between VCO1 and 2.
Mostly, however, it’s more of a workflow thing. SEM is quick and easy, and accessible to use. You can very quickly achieve great sounding mono patches for basses and leads etc.
Why not try the demo? See what you make of it. We hope that you’ll find it inspiring as we have.
Yes! SEM can load individual SEMPresets saved in OB-E, and OB-E can load presets from Oberheim SEM into the individual SEMs via the SEM LOAD button on the flip side of each SEM.
I appreciate that sentence may need reading a couple of times.
Check out the SEM manual for details.*
*External site will open in a new tab.
No. The FX will initialise even if they were locked. So the INIT button really takes it all back to the start. Use with caution.
Sort of.
It’s not polyphonic, so MPE is mostly redundant. However, it can pitch bend +/-48 steps to enable glide control and you can assign the vertical axis CC to anything you like. So it gives a pretty good MPE experience on monophonic playing.
But if you attempt to send it poly aftertouch from a ROLI it’ll make some strange noises!
Please update to Oberheim OB-E version 2.1.3 or newer for Ventura compatibility.
View Downloads (login required)
In the new Oberheim OB-E we have made significant improvements to the background engineering of the instrument. However, this unfortunately means that any automation that previously controlled grouped SEMs on OB-E v1 will not work on OB-E v2.
These automations will need to be changed to control SEM 1, then activate group mode.
Eg: Previous automation label: ALL VCF Cutoff
New Automation needed: SEM 1 VCF Cutoff
This may be done easiest by using OB-E v1 before updating to Oberheim OB-E (v2). We will keep v1 available to download so that you may roll back if required. Change any ALL automations to SEM 1 automations in current projects and then update to v2.
We’re sorry for this inconvenience and hope that you enjoy the new Oberheim OB-E.
Yes it is. In conversation with Oberheim we have changed the overall effect of the detune knob to be more inline with the original instrument sound and variations found between SEMs. Please note that patches that were saved with the old detune knob will still sound identical on v2.
First, check that you’re not using VST3. Then look for the “Program” folder in your filesystem. It’ll be here:
PC: C:\Program Files\GForce\OB-E\Presets\Presets\Program
Mac: /Library/Application Support/GForce/OB-E/Presets/Program
Move/copy the patches that you wish to be able to change between into this folder, you can put unto 128 patches in here. Patches will be alphabetically assigned a program change number (usually displayed as 0-127), so you may wish to rename the patches 01, 02, 03, etc to organise them.
From here, load up OB-E in the DAW of your choice and send Program Change messages to select those patches.
I’m sorry, Steinberg have dropped MIDI Program Change from the VST3 specification. If you wish to use MIDI Program Change, please use either the AU (Mac only) or original VST version of OB-E.
OB-E v2 comes with VST3 included. Depending on your DAW, you may have a different experience switching over to VST3.
Cubase users should have a seamless experience switching projects from OB-E v1 (vst) to OB-E v2 (vst3). All previously saved .vstpresets and project statuses will be recalled. These DAWs will automatically adopt the VST3 in favour of the VST2.
Ableton Live doesn’t seem to automatically switch over old projects to VST3. So we have provided a VST2 version of OB-E to aid transition between the two formats. Whilst you may wish to use the VST2 for any current projects that you’re working on, we would highly recommend using the VST3 or AU for all new projects. If you have any presets saved as a .fxp file (Live’s VST default), please take the time to load them up in the provided vst2 and resave them in OB-E’s patch browser. The VST3 and AU will pick them up automatically.
Studio One switches to VST3 automatically as long as you’re not running natively on an Apple Silicon chip, where it seems only AU is currently supported. If this is you, please load Studio One using Rosetta and swap the VST out of current projects in favour of the AU. Then you can run in native mode. Or continue to use Rosetta if you prefer.
The preset browser saves and loads .xml and .aupreset files. If you wish to use .vstpreset files you’ll need to do so via your host DAW’s patch management system.
The OB-E demo will work for 7 days from installation or for 6 full hours, whichever is shorter. It has a limited selection of factory patches and cannot load user patches. You can save user patches for use in the full version later.
For MPE to control of pitch please make sure that your controller is using MIDI channels 1-8 and that the patch has the maximum possible bend range (48 steps). You then need to assign each of the 8 SEMS to your controller individually. This takes a few seconds, but it does allow you to control any parameter on any SEM. You must switch off Group and Offset more for MPE and Poly Aftertouch to work correctly.
There’s a video tutorial available here: https://youtu.be/Sd-XvGASKHc
There is a known issue with Ableton Live that prevents the AU switches from correctly writing to the timeline if they’re controlled from OB-E’s UI. There are two options:
a) Please add the switch you wish to automate to Live’s Configure panel before automating it. It will then work correctly.
b) Use the VST3.
OB-E v2 has had to changed it’s native preset type away from AU presets as part of introducing PC compatibility. On Mac, OB-E can still read .aupreset files, so your previously saved user patches are still there. However all factory presets are now in .xml format.
A recent change in Ventura seems to have blocked MkII’s initial setup windows from appearing on Apple Silicon Macs. Please place your DAW into Rosetta mode for the initial setup. Then you can put it back into regular native mode for normal use. To do this:
M-Tron MkII does not replace the M-Tron Pro.
No, at the moment MkII contains original Chamberlin, MkI & MkII tape-banks. We will offer additional tape-banks at a later date.
No. If Geoff Unwin didn’t need it, neither do you.
PC: After clicking the host sync button a tempo box will appear. Click the box and drag.
Mac: After clicking host sync M-Tron MkII will conform to the tempo set in the Preferences window (cmd-comma)
The demo version of M-Tron MkII contains a very limited sound library, specifically Station 1 (see the M-Tron MkII Manual) of both the Chamberlin and MkI, plus two Chamberlin tape-banks from Station 7 available for the Rhythm and Accompaniment manual. MkI Station 1 Rhythms and Accompaniments are the same as the MkII. The demo MkI Leads are the DI variant, with the Mic recorded variations only available in the full version.
The demo allows you to trial all M-Tron MkII modes (Lead & Rhythm & Accompaniment) plus the provides the ability to load the Chamberlin Violins and Flutes into the left manual for a 2 x 35 note (G-F) double manual experience.
Additionally, the demo is limited in use by an audio fade and silence occurring every 20 seconds. The purpose of this demo is (a) to give you an understanding of the MkII’s capabilities, and (b) to make sure it functions correctly on your system.
The MkII demo Library size is 365MB. The full version Library size is 4.7 GB
There are 142 Patches in the Demo version
On Apple Silicon chipped Macs there is an additional layer of security that prevents DAWs from accessing certain areas on your Mac. For some reason this includes some locations that you’d think a DAW might just want to access, like /Library/Audio for example.
If you have placed your Library in one of these locations the standalone M-Tron MklI will be able to read it, but the plug-in won’t. The best solution is to move the Library somewhere else, we recommend /Library/Application Support/GForce as a good location on your system drive.
After doing that M-Tron MkII will ask to be relinked to the library folder when you next run it.
It’s coming. Currently if you’d like to run MkII as a VST on your Apple Silicon Mac, please enable Rosetta on your host application. Do this from the application’s Get Info window in Finder.
Check if the brake is on and if the mod wheel is turned up slightly. With the brake on and the mod wheel not at 0 you will hear a flattening of the side the Brake is affecting. This can be particularly noticeable when brake is only set to one manual.
Key Clicks are only audible when Tape Rewind is enabled.
Please make sure you have downloaded and installed all components of M-Tron MkII.
On PC there are three installers, one software, two for the library. Please run all three before trying to run M-Tron MkII
On Mac, please make sure all three sound library files are inside the MkII Library folder. Library.cpt5, Accompaniment.cpt5 and Leads.cpt5.
We have noticed quite a few reports of this recently. Whilst we are looking into this with some urgency, so far the issue has been resolved by restarting the Mac.
Additionally to the restart a couple of users have found that they need to reinstall impOSCar2 installing all formats. VST, AU and Standalone.
Yes, impOSCar2 works well on Monterey.
There are a couple known issues with Big Sur:
The wrong default patch loads when you first start the instrument and there’s an issue where the waveform and filter display windows may not update in real time.
Over the years we have had to change the format of our serial number system a couple of times. This has led to a bit of a confusion of names when it comes to your licence codes needed for installation.
In your account click the View Instrument button next to impOSCar2.
You will see two lines of text for the licence code. The first line is your “product username”, if you bought it on the new site it will begin with the letters “IMP”. Older buyers may have a username that they had on our old site here.
The second line is the registration key, or licence code, or serial. It is always a long code of numbers and letters.
If an instrument is not being detected by Logic (or any other Audio Unit host), please try the following procedures.
1. Run the AU Manager from within Logic Pro X.
2. Depending on your OS, go to:
Macintosh HD/Users/Library/Caches or Macintosh HD/Users/Library/Caches/AudioUnitCache
Move the com.apple.audiounits.cache file to the Trash then empty the Trash. When you next restart Logic or Digital Performer they will freshly scan installed Audio Units and your instrument should now appear in the Audio Units list.
3. Go to Macintosh HD/Library/Audio/Plug-ins/Components.
If you can see your plugin in the list of Audio Units, select the file and move it to the Desktop. Restart the Mac and start Logic or Digital Performer. Follow this by shutting down Logic or Digital Performer then move the Audio Units from the desktop back into the HD/Library/Audio/Plug-ins/Components folder. Restart Logic or Digital Performer and your instrument should now appear in the Audio Units list.
There is no AAX version of impOSCar2 for Mac or PC.
Please consider using a VST wrapper plugin to use impOSCar2 within Pro Tools. We have tested the following:
Blue Cat Audio MB-7 Mixer
Blue Cat Audio Patchwork
DDMF Metaplugin64
The manual for impOSCar2 is installed to the following locations and is named impOSCar2_Manual.pdf.
Mac:
User/Documents
PC:
C:/Program Files/GForce/impOScar2/Documentation
Native Instruments uses a service called NIHardwareAgent which monitors the USB bus for the Maschine controller. Whenever this service is running, Imposcar 2 may crash and the kernel panics point to the VST, not the service. However, disabling this service gives consistent performance.
Thanks to William Buchanan for the fix.
Please navigate to the following location on your computer:
C:/Program Files/GForce/impOSCar2/Support
Open the file ‘impOSCar2.sup’ with notepad and add the following line into the file after the {Knob Mode} line at the top:
{Linear Knob Mode Cursor Move}{off}
Save the ‘impOSCar.sup’ file
A recent change in Ventura seems to have blocked VSM’s initial setup windows from appearing on Apple Silicon Macs. Please place your DAW into Rosetta mode for the initial setup. Then you can put it back into regular native mode for normal use. To do this:
Yes. You’ll need the latest version, available to download here.
Apple Silicon Macs have an additional layer of security preventing DAWs from accessing certain areas of your hard drive. If you have placed your String Machine Library in one of these locations the plugin version of VSM won’t be able to read it, but the standalone will.
We recommend that you move your library to:
/Library/Application Support/GForce
and relink it when you next run VSM.
/Library
/Library/Audio
Make sure that your host’s VST folder locations list does not contain the folder that contains the 32bit version of M-Tron Pro. If a 64bit host scans the 32bit version at all it will ignore the 64bit version.
A Mac installation video can be found here.
Please fully extract the downloaded zip file before running the installer.
M-Tron Pro and VSM require the use of an ASIO compliant sound card or interface. If you don’t have a dedicated sound card or interface you can often convert your PC’s standard audio drivers by downloading and installing the free, tiny and great ASIO4all third-party driver here.
Library 2 and Expansion Pack 2 contain stereo samples that require VSM v3.x or newer to run. Please download and install a new version of VSM, which you can do in your Account.
There is no AAX version of VSM for PC.
Please consider using a VST wrapper plugin to use VSM within Pro Tools. We have tested the following:
Blue Cat Audio MB-7 Mixer
Blue Cat Audio Patchwork
DDMF Metaplugin64
The cpt2 file will be added directly to your library folder and the patches and tapes added into the browsers.
Platform: MAC/PC
Mac – Run M-Tron Pro and click the show MIDI CC button. A file path of your library will be shown.
PC
By default: C:/ProgramData/GForce/M-Tron Pro Library
ProgramData is a hidden folder, so make sure you enable Show hidden files and folders in Windows to find it.
Please note that during installation of M-Tron Pro you can select a custom location. If you’ve done this and can’t remember where you put it, run M-Tron Pro and click the show MIDI CC button. A file path of your library will be shown.
A recent change in Ventura seems to have blocked M-Tron Pro’s initial setup windows from appearing on Apple Silicon Macs. Please place your DAW into Rosetta mode for the initial setup. Then you can put it back into regular native mode for normal use. To do this:
Yes. You’ll need the latest version, available to download here.
Apple Silicon Macs have an additional layer of security preventing DAWs from accessing certain areas of your hard drive. If you have placed your M-Tron Pro Library in one of these locations the plugin version of M-Tron Pro won’t be able to read it, but the standalone will.
We recommend that you move your library to:
/Library/Application Support/GForce
and relink it when you next run M-Tron Pro.
/Library
/Library/Audio
If an instrument is not being detected by Logic (or any other Audio Unit host), please try the following procedures.
1. Run the AU Manager from within Logic Pro X.
2. Depending on your OS, go to:
Macintosh HD/Users/Library/Caches or Macintosh HD/Users/Library/Caches/AudioUnitCache
Move the com.apple.audiounits.cache file to the Trash then empty the Trash. When you next restart Logic or Digital Performer they will freshly scan installed Audio Units and your instrument should now appear in the Audio Units list.
3. Go to Macintosh HD/Library/Audio/Plug-ins/Components.
If you can see your plugin in the list of Audio Units, select the file and move it to the Desktop. Restart the Mac and start Logic or Digital Performer. Follow this by shutting down Logic or Digital Performer then move the Audio Units from the desktop back into the HD/Library/Audio/Plug-ins/Components folder. Restart Logic or Digital Performer and your instrument should now appear in the Audio Units list.
Mac – Run M-Tron Pro and click the show MIDI CC button. A file path of your library will be shown.
PC
By default: C:/ProgramData/GForce/M-Tron Pro Library
ProgramData is a hidden folder, so make sure you enable Show hidden files and folders in Windows to find it.
Please note that during installation of M-Tron Pro you can select a custom location. If you’ve done this and can’t remember where you put it, run M-Tron Pro and click the show MIDI CC button. A file path of your library will be shown.
A Mac installation video can be viewed here.
Please extract the downloaded zip file before running the installer.
M-Tron Pro and VSM require the use of an ASIO compliant sound card or interface. If you don’t have a dedicated sound card or interface you can often convert your PC’s standard audio drivers by downloading and installing the free, tiny and great ASIO4all third-party driver here.
Make sure that your host’s VST folder locations list does not contain the folder that contains the 32bit version of M-Tron Pro. If a 64bit host scans the 32bit version at all it will ignore the 64bit version.
There is no AAX version of M-Tron Pro for PC.
Please consider using a VST wrapper plugin to use M-Tron Pro within Pro Tools. We have tested the following:
Blue Cat Audio MB-7 Mixer
Blue Cat Audio Patchwork
DDMF Metaplugin64
Currently, the Minimonsta installer will fail in macOS Ventura. An upgrade to Minimonsta2 will be required for future support and compatibility.
If you have Minimonsta installed before updating the OS it will continue to work as it did in Monterey.
Apple have fixed the issue that broke Minimonsta in Big Sur (macOS 11). Therefore, at this time it would seem that Minimonsta is functioning within Monterey as a plugin. We have released a standalone patch to install after the main plugin versions for standalone compatibility.
This fix has not been put into Big Sur, so Minimonsta is still not compatible with macOS 11. A long term fix for these potential issues is still being worked on by GForce.
No. Unfortunately Minimonsta will not work correctly on Big Sur. Fixes for this major issue may take a long time to do.
Update 30/10/21:
Preliminary checks suggest that these issues are resolved by Apple in macOS 12, Monterey. The plugin works as designed but the standalone remains inoperable.
Unfortunately Minimonsta is not compatible with Big Sur. Fixes for this major issue may take a long time to do.
Update 30/10/21:
Preliminary checks suggest that these issues are resolved by Apple in macOS 12, Monterey. The plugin works as designed but the standalone remains inoperable.
Over the years we have had to change the format of our serial number system a couple of times. This has led to a bit of a confusion of names when it comes to your licence codes needed for installation.
In your account click the View Instrument button next to Minimonsta.
You will see two lines of text for the licence code. The first line is your “product username”, if you bought it on the new site it will begin with the letters MMM. Older buyers may have a username that they had on our old site here.
The second line is the registration key, or licence code, or serial. It is always a long code of numbers and letters.
If an instrument is not being detected by Logic (or any other Audio Unit host), please try the following procedures.
1. Run the AU Manager from within Logic Pro X.
2. Depending on your OS, go to:
Macintosh HD/Users/Library/Caches or Macintosh HD/Users/Library/Caches/AudioUnitCache
Move the com.apple.audiounits.cache file to the Trash then empty the Trash. When you next restart Logic or Digital Performer they will freshly scan installed Audio Units and your instrument should now appear in the Audio Units list.
3. Go to Macintosh HD/Library/Audio/Plug-ins/Components.
If you can see your plugin in the list of Audio Units, select the file and move it to the Desktop. Restart the Mac and start Logic or Digital Performer. Follow this by shutting down Logic or Digital Performer then move the Audio Units from the desktop back into the HD/Library/Audio/Plug-ins/Components folder. Restart Logic or Digital Performer and your instrument should now appear in the Audio Units list.
Yes, there are more patches in the full version.
The full version comes with 582 Meta-patches which equates to 6402 patches.
The Minimonsta responds to program change in the following manner:
Each of the Meta-Patches within the selected folder is assigned a program change number starting at 1 and running sequentially thereafter.
If you send the instrument Program Change No. 1, the first sound in the list is loaded into the instrument RAM, but it is only activated when a key on the Melohman Octave (the black octave on the left) is pressed. Doing this loads the Patch for that key of the new sound (this will be a variation on the sound that has been loaded into RAM, and each key in the Melohman Octave loads a different variation). This can easily be automated within a host.
The manual incorrectly lists Osc 2 & 3 Transpose as having the same CCs assigned as the Delay Left & Right Times (CCs 12 & 13). The values should be as follows:
Osc 2 Transpose = 27
Osc 3 Transpose = 28
There is a very simple way to check which CC is assigned to which parameter:
There is no AAX version of Minimonsta for PC.
Please consider using a VST wrapper plugin to use Minimonsta within Pro Tools. We have tested the following:
Blue Cat Audio MB-7 Mixer
Blue Cat Audio Patchwork
DDMF Metaplugin64
Yes. Registered Oddity and Oddity2 owners will get a 50% discount on Oddity3 automatically applied in the basket.
Currently, the Oddity2 installer will fail in macOS Ventura. An upgrade to Oddity3 will be required for future support and compatibility.
If you have Oddity2 installed before updating the OS it will continue to work as it did in Monterey.
Apple have fixed the issue that broke Oddity2 in Big Sur (macOS 11). Therefore, at this time it would seem that Oddity2 is functioning within Monterey as a plugin. We have released a standalone patch to install after the main plugin versions for standalone compatibility.
This fix has not been put into Big Sur, so Oddity2 is still not compatible with macOS 11. A long term fix for these potential issues is still being worked on by GForce.
No. Unfortunately Oddity2 will not work correctly on Big Sur. Fixes for this major issues may take a long time to do.
Update 30/10/21:
Preliminary checks suggest that these issues are resolved by Apple in macOS 12, Monterey. The plugin works as designed but the standalone remains inoperable.
Unfortunately Oddity2 is not compatible with Big Sur. Fixes for this major issue may take a long time to do.
Update 30/10/21:
Preliminary checks suggest that these issues are resolved by Apple in macOS 12, Monterey. The plugin works as designed but the standalone remains inoperable.
Over the years we have had to change the format of our serial number system a couple of times. This has led to a bit of a confusion of names when it comes to your licence codes needed for installation.
In your account click the View Instrument button next to Oddity2.
You will see two lines of text for the licence code. The first line is your “product username”, if you bought it on the new site it will begin with the letters “O2”. Older buyers may have a username that they had on our old site here.
The second line is the registration key, or licence code, or serial. It is always a long code of numbers and letters.
If an instrument is not being detected by Logic (or any other Audio Unit host), please try the following procedures.
1. Run the AU Manager from within Logic Pro X.
2. Depending on your OS, go to:
Macintosh HD/Users/Library/Caches or Macintosh HD/Users/Library/Caches/AudioUnitCache
Move the com.apple.audiounits.cache file to the Trash then empty the Trash. When you next restart Logic or Digital Performer they will freshly scan installed Audio Units and your instrument should now appear in the Audio Units list.
3. Go to Macintosh HD/Library/Audio/Plug-ins/Components.
If you can see your plugin in the list of Audio Units, select the file and move it to the Desktop. Restart the Mac and start Logic or Digital Performer. Follow this by shutting down Logic or Digital Performer then move the Audio Units from the desktop back into the HD/Library/Audio/Plug-ins/Components folder. Restart Logic or Digital Performer and your instrument should now appear in the Audio Units list.
All Oddity .pbk (preset banks) can be imported into Oddity2.
No.
Code 1014 is a permissions error. Please ensure you have write permissions to the directory you’re attempting to save the bank into. You can adjust permissions using the Get Info (Apple key + i) screen of the folder provided you have an admin on your Mac. Alternatively, try repairing permissions from Disk Utility on your hard drive.
There is no AAX version of Oddity2 for PC.
Please consider using a VST wrapper plugin to use Oddity2 within Pro Tools. We have tested the following:
Blue Cat Audio MB-7 Mixer
Blue Cat Audio Patchwork
DDMF Metaplugin64
We are aware of an issue that seems to affect M1 chipped Macs on Big Sur. If you get this message when you run M-Tron Pro LE, there is a fix.
1) Use Finder to navigate here:
HD/Library/Audio/Sounds/
2) Move the “M-Tron Pro LE Library” folder that you find there somewhere else. We recommend:
HD/Library/Application Support/GForce
3) Run M-Tron Pro LE. When the message pops up, use the following dialogue box to select the M-Tron Pro LE Library folder.
Users with a registered copy of M-Tron in their account will automatically receive a 50% discount when buying M-Tron Pro. Add M-Tron Pro to your basket and then click View Basket to see the discount applied.
Please contact us, providing as much information as you can about the following:
Once we have these details we will contact you with registration details or for more information.
M-Tron was replaced by M-Tron Pro a decade ago! It is no longer available to download at all. It won’t work on any modern computer.
Users with a registered copy of impOSCar in their account will automatically receive a 50% discount when buying impOSCar2. Add impOSCar2 to your basket and then click View Basket to see the discount applied.
Users with a registered copy of Oddity in their account will automatically receive a 50% discount when buying Oddity2. Add Oddity2 to your basket and then click View Basket to see the discount applied.