Do you have the dreaded “OAX_Rotor_Click_Sound”? – We have a fix!

Well, really we don’t have a fix but the Wersi team does! We are just passing along what we learned over the past 48 hours in a conversation with other OAX owners. First, take a listen to the audio clip below. It’s nothing more than a recording made using the “Audio Record” feature of OAX as we hit the Rotor “Fast/Slow” button.


It might vary depending on which OAX instrument you own but this is what it looks like on a Sonic OAX700. The “button” we are talking about is located to the left of the Upper Keyboard:










Your next step?

  1. Listen to the audio clip above.
  2. Select any of the “VB3 Drawbar” sounds on your OAX instrument.
  3. Simply switch back-n-forth between Rotor Slow/ Fast sound.
    1. Hint – You might need to plug in your headphones to hear it.
  4. If that “noise” bothers you there is a fix available from Wersi.
    1. We will admit that we never heard it until it was pointed out to us by another WersiClubUSA member.
    2. Is it a bad thing or simply the sample is “so good” that you can hear the mechanical switch taking place along with the spin up/ down” of the speaker rotor?
    3. Whichever side of that discussion you are on, there is a change you can make that will cleanup what you hear.
  5. The fix involves replacing the *.ini file located in c:\wersi\Plugins\drawbars\VB3 and c:\wersi\Plugins\drawbars\VB3
  6. We are not authorized to distribute the fix however, you can contact the Wersi support team for an updated *.ini file.

7 thoughts on “Do you have the dreaded “OAX_Rotor_Click_Sound”? – We have a fix!

  • 08/05/2017 at 11:12

    Hi Bill,

    I wasn’t actually suggesting that users should make changes to the VB3.ini file unless they really know what they’re doing ! Although this is a standard GSI file, there are some Wersi specific settings in there e.g. MIDI channel numbers that shouldn’t be altered.

    There will be some users however that have an interest in the way in which settings on the Wersi VB3 menu get translated to the actual VST, and now we know how this is done. The VB3.ini file provides this mechanism. And since Wersi have implemented a reduced version of VB3, the options on the ‘Global Options Menu’ give a good indication of what’s been left out, and how Wersi have catered for this in the VB3.ini file. So it’s just additional information for those who may be curious.

    The best way to change any of these ‘hidden parameters’ is to install the full feature version of VB3, and then these can be set to the required values on the additionally provided menus.


  • 08/05/2017 at 10:04

    Hi All

    I would not recommend you alter any of the ini settings in OAX unless instructed by Wersi, as they may have unintended consequences, (If you do decide to mess at least make a copy first) best to wait until Wersi adds more features in a future update.


  • 08/05/2017 at 09:51

    Hi Jerry and Curt,

    Many thanks Jerry for your feedback on the Wersi fix, and confirmation of my thinking. I heard the wobbling noise in Curt’s file and assumed that it was the rotor wind noise, which is what got me wondering what would happen to the rotor click if we switched this off. I have the commercial version of VB3 installed so was able to set this option to ‘Off’, and sure enough the click disappeared.

    Thanks for the further information on the VB3.ini file Curt, we can now see what’s going on here. The relevant parameter is ‘RotWindLvl’ which controls the level of the rotor wind noise. These are the settings that were stored in the VB3.ini file when I set this parameter in the VB3 software to it’s various values.

    RotWindLvl = 1 Off
    RotWindLvl = 2 Low
    RotWindLvl = 3 Medium
    RotWindLvl = 4 High
    RotWindLvl = 5 Very High

    So our suspicion was correct, the Wersi fix is to set this parameter to 1, which turns off both the wind noise and the rotor click.

    There’s lots of other parameters in this file that relate to options that Wersi have not included in the VB3 ‘Wersi Edition’. The ‘Global Options’ menu described in the VB3 manual available on the GSI website contains most of these.

    Have fun.


  • 08/04/2017 at 20:50


    I loaded the fix file on my OAX-1. It is completely silent now. The wobbling noise in Curt’s file above is suppose to be the wind noise. You can view the ini file with note pad and can edit it. It has all the parameters for the VB3 setup.


    • 08/05/2017 at 06:31

      Before I installed the fix I renamed the original file. I’ll could go in and compare the files to find the setting(s) that were changed.

      Lot’s of interesting settings when browsing the file.

      • 08/05/2017 at 07:40

        Not clear if some of these values are a result of the last time I used VB3 drawbars and they very well could be. A quick compare of the two files and what is different.

        Parameters in the “new” file that are different from the original file:


        And from the “old” file”

  • 08/04/2017 at 14:23

    This is very interesting. As I understand it, in the original design of the Leslie Speaker the rotor speed was switched by an electro-mechanical relay driven by an electronic valve (tube). The valve was used to power up the signal coming from the Chorale/Tremolo control that was attached to the organ. The noise from this assembly had a tendency to leak into the Leslie Speaker’s audio, hence the click.

    The commercial version of VB3 has an option to specify the volume level of the rotor’s wind noise from Off to low/medium/high/very high. What’s interesting is that when this control is set to ‘Off’ there is no audible click, but with any of the other settings it comes through loud and clear. It would seem that the VB3 model ties these two effects together. The ‘Wersi Edition’ of VB3 doesn’t provide this option for the user, but my guess is that it’s set to a particular value in the VB3 *.ini file, and the Wersi fix is to switch it off. It would be good to know from anyone who has implemented the fix whether this also switches off the rotor wind noise.

    If indeed Wersi are using the *.ini file to define specific values for those options that are available in the VB3 model, but have not been implemented in the ‘Wersi Edition’, and if this is a readable text file, then it raises the intriguing proposition that we now have the secret of man’s red fire. The user would have access to a whole bunch of additional parameters that could be configured according to personal preference.

    There’s a lot of ‘ifs’ and ‘buts’ here folks, but it would be interesting to hear if this is possible from anyone who has tried out the fix.



Leave a Reply

Your email address will not be published. Required fields are marked *