OAX Controller Deep Dive

A follow up to our last video where we looked at some of the OAX controller data that can be sent to external MIDI devices or VST’s. This time we look a little deeper at the controller data that OAX can send.

On a side note, we connected up a PC running Cakewalk using the “MIDI over USB” port, and it worked just fine.

At this point we are going to leave OAX and MIDI controllers “open for comment” and move back to looking at different ways of using a Ketron SD xx Arranger module with OAX.

Make sure to comment, ask questions, “whatever” so we can continue to explore and share what we find with all OAX owners.

11 thoughts on “OAX Controller Deep Dive

  • 01/27/2019 at 07:54

    Hi Curt, just wondered ! If you remember the last time we
    spoke I was about to connect a Ketron SD 40 to the Abacus
    Duo Pro, this was before having Chemo as you can imagine
    it had to take a back seat, all is well now with me and the
    SD 40, I have now gone a stage further and bought the
    Mid J Pro which has taken the place of the SD 40, the SD 40
    is now connected to my Roland FA 06 synth which gives me
    a Ketron Arranger and is a damn site lighter to carry than
    the SD 7.

    I don’t know how Ketron are presented in the U.S. but over
    in the U.K. I can not go anywhere to hear a demonstration
    why this is the case I have no idea when Ketron are a
    fantastic product leaving Yamaha and Korg standing, having
    owned the SD 7 for over twelve months I never want to
    own or play Yamaha or Korg again, to this end I am looking
    to set up an agency, I will keep you posted.


  • 01/26/2019 at 10:40

    Hi Curt, am I missing something ? all of your videos show
    how to connect something to OAX which no doubt has been
    very useful, then you try to control something else and tear
    your hair out trying to make it work, I would have thought
    putting the same amount of effort playing the instrument
    would have been more beneficial, why do you need all these
    additional modules daw’s etc, when Wersi is supposed to be
    the bee’s knees judging by the exorbitant price they command

    • 01/27/2019 at 06:49

      Ha, Good one Dave!

      Well, I spent 38+ years in the world of computers doing about everything you can do in that career path so we like to tinker and a Sonic is nothing but a computer. You are correct, OAX on its own is capable of about anything musically that one would want to create. Having said that OAX also offers the ability to integrate with whatever MIDI setup you might own. There are a few folks out there enjoy this tinkering stuff as much as me, so we share and learn with and from them.

      When not messing with “the mess” downstairs we are upstairs in our office where we have a MIDI controller, a Mac full of VST’s and do pretty much the same thing on that gear! As my wife says – “Boys and their toys”!

      Oh yeah, once in a while we actually play a tune… 🙂

  • 01/24/2019 at 23:38

    I tried to get the manual controller to control some of the functions in Kontakt but had no success. I guess they only work for midi out and not Internal VST instruments.


    • 01/25/2019 at 06:32

      Hi Jerry
      Apart from the basic midi controls Pitch, Modulation wheels, Volume etc. you have to set the cc controls up in Kontakt as well as OAX. (Click on the Automation tab in Kontakt and drag the cc you wish to use to the button/knob you wish to control, alternatively you can right click the button/knob and choose Midi learn, then move the slider in OAX that you have already assigned a cc to)

  • 01/24/2019 at 15:34

    Ah right John, if we wanted to change a CC number, I’m guessing that’s what the “Edit CC’ button is for.

    Curt, would it be possible to do a couple of screenshots of what see on the ‘Edit CC’ menus, one for the Manual Controller and one for the Sound Controller, then I can include them in my upgrade writeup.


  • 01/24/2019 at 14:28

    From the video the manual and sound controllers are interchangeable, (You can assign any cc you want) however to maintain consistency with the inbuilt sounds, it is probably wise to assign them as Jeff has suggested. (From what I gather from the manual (it’s a pain having keep translating everything from German to English, particularly as every other manufacture has English manuals available) it just says that there are 14 programmable controllers available)

  • 01/24/2019 at 10:27

    Hi Curt,

    Yes I agree, the difference between the Manual Controllers and the Sound Controllers isn’t clear. Here’s what I think.

    The CCs on the Manual Controller menu are general controllers that can be applied to ALL sounds, e.g. reverb, chorus, delay etc. The CCs on the Sound Controller menu would be SPECIFIC to a particular instrument, e.g. the Breath effect in your example, or the fret noise on a guitar, or the hammer noise on a piano. On OAS these are also on two separate menus, the former on a ‘Selectors’ menu, the latter on a ‘Sound Controls’ menu, and the same two menus are used for both the internal and external sounds. The general CCs are routed to the OAS MIDI out ports. For applications software with a MIDI Learn facility (which is pretty well all software), these additional CCS can be used to control any kind of function. None of this is explicit in OAS, I discovered it quite by accident, but it does mean that the MIDI out facility is more comprehensive than you might at first realise.



Leave a Reply

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

This site uses Akismet to reduce spam. Learn how your comment data is processed.