In order to fully test a VST plug-In, please follow these steps and report back here.

Firstly please try and get these informations.

1) Plugin Name & Manufacturer

2) Plugin version: Which version? Full version or demo version?

3) OS version: what is your operating system?

At this point you may want to uninstall and then reinstall the Ohm Studio if you believe that the plug-in you're testing is not working properly.See here for the uninstall procedure.Removing the cache and preferences should be enough (step 1 and 2 on Mac, step 4 and 5 on Windows).

4) VST Scan: Does the initial scanning process make the ohm studio crash/freeze? Dou you see the VST plug-in in the Gear-List?

5) Instantiating the plugin. Does the plug-in make the Ohm Studio crash when you drag&drop it on the Gear Panel?

6) Audio. Does it make any sound (VST instruments)? Or does it process audio correctly (VST effects) ?

7) Changing presets/parameters. Does changing the preset (or any parameters if the plugin doesn't have presets) on the plug-in's GUI affect the sound?

8) Inspector. Can you control the plug-in's parameters from the Plugin Inspector?

9) Loading presets/parameters : If you change the plug-in's preset (or any parameters if the plugin doesn't have presets), close the project, then open it again, does the plug-in load the right preset or does it load the default preset? In other words, does the plug-in remember the changes you made last time you worked on that project?

1. impOSCar, GForce2. v 1.0.1 full3. Windows 7 64-bit4. VST scan - OK5. Instantiating - OK6. Audio - OK7. Presets work on initial load8. Inspector - OK9. Upon closing/reopening, all tweaks/knobs remained where they were when closed, but all presets are absent from the instanced plug-in. Tested without tweaking from preset, and also had all presets disappear.

1. Akoustik Piano, Native Instruments2. v 1.1.3.001 full3. Windows 7 64-bit4. VST scan - OK5. Instantiating - OK6. Audio - OK7. Presets work on initial load8. Can control some basic parameters from Inspector but not all9. Upon closing/reopening, all tweaks/knobs were reset, the previous preset was not loaded, and all presets are available.

1. Battery, Native Instruments2. v 3.2.2 full3. Windows 7 64-bit4. VST scan - OK5. Instantiating - OK6. Audio - OK7. Preset change - OK - Will load kits8. Can control some basic parameters from Inspector, but no midi cc control9. Upon closing/reopening, all tweaks/knob positions were lost where they were when closed, loads the last kit sans any previous adjustments, and all kits are still available.

1. Brass, Arturia2. v 2.0.5 full3. Windows 7 64-bit4. VST scan - OK5. Instantiating - OK6. Audio - OK7. Preset change - OK - Loads kits and individual instruments8. Can control parameters through Inspector - however most control is based off of velocity so Inspector is not useful for this plugin. Turning any of the parameters to zero creates a c# error and crashes the vst9. Upon closing/reopening, all tweaks/knobs were reset, the previous preset was not loaded, and all presets are available.

1. Kontakt, Native Instruments2. v 4.2.3 full3. Windows 7 64-bit4. VST scan - OK5. Instantiating - OK6. Audio - OK7. Preset change - OK - Will load instruments etc.8. Can control some basic parameters from Inspector, but no midi cc control9. Upon closing/reopening, all tweaks/knob positions were lost where they were when closed, loads the last instrument used without any adjustments, and all instruments are still available.

1. Guitar Rig 3, Native Instruments2. v 3.1.0.005 full3. Windows 7 64-bit4. VST scan - OK5. Instantiating - OK6. Audio - OK7. Preset Load - OK - Will load instruments etc.8. Inspector - Only some parameters can be controlled through the Inspector9. Reloading project - OK - Upon closing/reopening, all tweaks/knob positions were where they were when closed, loads the last instrument used without any adjustments, and all instruments are still available.

1. Massive, Native Instruments2. v 1.2.1 full3. Windows 7 64-bit4. VST scan - OK5. Instantiating - OK6. Audio - OK7. Preset change - OK - Will load instruments etc.8. Inspector - OK9. Upon closing/reopening, all tweaks/knob positions were kept until the vst was opened - it then reverted to the preset that was altered, and all presets are still available.

Maschine will sometimes lock up Ohmstudio when instantiating the plugin. When it does instantiate, loading a new kit while the project is playing will cause Ohmstudio to lock up. If you Force Quit Ohmstudio while it is locked up, the Maschine interface will be left on screen on top of all other windows and will not disappear unless the computer is restarted. This is a horrible way to handle this type of situations.

Maschine will sometimes lock up Ohmstudio when instantiating the plugin. When it does instantiate, loading a new kit while the project is playing will cause Ohmstudio to lock up. If you Force Quit Ohmstudio while it is locked up, the Maschine interface will be left on screen on top of all other windows and will not disappear unless the computer is restarted. This is a horrible way to handle this type of situations.

Hi.

In order to force quit Ohm Studio, you have to launch a utility program called "Activity Monitor" and kill 2 different processes (see picture below) because Maschine as well as other VSTs run in a separate process.

This a "less horrible" way to deal with that type of situation where you had to restart your computer.

Could this list be transferred to a single file (sorted by plugin name alpha) which is linked - and can be updated accordingly ? Would make it way easier to see if a plug in has been tested for this list to be updated

8) Inspector parameters not named, changing them does not seem to do anything, altough the plugin interface is onseveral pages, so I'm not sure

9) Re-loading project: Does not remember preset, I need to re-load the preset with sounds again manually.

Also, there is a screen update problem where the screen does not update unless I move the window around. I have 1024x768 px resloution on my X60s Lenovo laptop. The plugin also seems to cause crashes sometimes. On my 1600x1200 px desktop with WinXP the screen updates correctly.