The [AF1]/[AF2] buttons are assignable. They are the Assignable Function buttons, which means that they can be used within a Voice’s Control Set to directly address the available internal parameters. And as with most physical controllers it generates a MIDI footprint... meaning when you press the button it generates a Control Change (cc) message. The purpose of generating a MIDI message is so that it can be documented (recorded) and played back to the MOXF via MIDI IN.

What cc# it generates when pressed is programmable globally for the MOXF, as follows:

Press [UTILITY]
Press [F4] CTL ASN (Controller Assign)
Press [SF1] ASSIGN

AF 1 defaults to cc86
AF 2 defaults to cc87

EXAMPLE:
Sending cc86 with a value 64-127 will turn the AF1 switch On
Sending cc86 with a value 0-63 will turn the AF1 switch Off

Default condition for the AF buttons is OFF (this means when a program is recalled on the MOXF, the AF buttons will default to minimum).

You can operate these button via MIDI when you send the appropriate MIDI message and value.

This is great. Thanks. Good to know I can send the AF1 and AF2 from a different MIDI keyboard!

I have the above working nicely so thank you for the info. It allows me to play with my MOXF8 from the MIDI controller on my desktop.

I do have another related question. I checked my "MIDI monitor" software and it seems that turning the top row of knobs doesn't generate MIDI CC messages. I'd like to map not only those, but and also the ARP button on my MIDI controller.

For example, I might wish to adjust the cut off from a knob on my MIDI controller.

To be clear, my MIDI contoller is connected via a USB cable, as is my MOXF, both to a Mac.

I can use the MOXF Editor to make changes on the computer but that's not very performance oriented. I am using Logic, not Cubase, so there is no VST option, per sec.

Is such a thing possible? I can play the MOXF from my other keyboard. I just can't access some of the finer controls.

Thank you!

I do have another related question. I checked my "MIDI monitor" software and it seems that turning the top row of knobs doesn't generate MIDI CC messages. I'd like to map not only those, but and also the ARP button on my MIDI controller.

What the Knobs generate at any time is a function of what that knob is assigned to do to the MOXF engine. That, quite naturally, is their primary function.

I’m not clear about what you are attempting to do since you mention you are using the external Controller on your desktop. To me that says you are NOT interacting directly with the MOXF Knobs. So it begs the question — what do you care what they are sending.

If you are using an external device as controller, shouldn’t you be concerned with what the Knobs of that controller is sending.

If you want the MOXF Knobs to send custom CC # messages, you should activate the REMOTE Editor and then you can setup the MOXF knobs to any cc number you may desire.

The MOXF6/MOXF8 REMOTE EDITOR (port 5) allows you to assign the three rows of four buttons to CC# - useful for when using the MOXF as your controller.

MOXF6/MOXF8 Remote Editor - allows you to create control templates for controlling plugins (including the MOXF VST). This Editor does NOT run in the DAW, it is launched along side of it. On launch, it will search your installed VSTi and create a catalog of your plug-in synths, you can recall from among its 50 Preset Templates; if your plugins template does not appear, this Editor allows you create a custom one for that plugin.

I’m not clear about what you are attempting to do since you mention you are using the external Controller on your desktop. To me that says you are NOT interacting directly with the MOXF Knobs. So it begs the question — what do you care what they are sending.

I think what he really cares about is not having those knobs send some MIDI CC (though that's how he put it when talking about his use of MIDI Monitor), but rather having those knobs receive (respond to) MIDI CC (probably assuming that whatever they'd have sent would correspond to what they would respond to). And the reason it would be nice to have them receive/respond in that way is that the knobs are often providing control of parameters which would not otherwise be easily accessible from an external controller, since the underlying parameters may be listening for sysex rather than CC. Since programming knobs on an external controller to send sysex rather than CC is more difficult (or impossible, depending on the controller), there would be value in being able to have a knob on a controller send a CC that would tell the MOXF to so the equivalent of turning one of those knobs.

The knobs can send any CC# 0-127, but you must use Remote Editor to program them. It includes a template already made of the MOXF VST
I’m still unclear about the question, unless trying to replace your external controller with the MOXF.

When the MOXF is in normal mode, the knobs address the MOXF... They are not designed to control anything external. Yes some of them send standard CC #s, but their primary function is to address the MOXF.

The Master Mode, allows you to reprogram the Knobs Upper/lower row
The Remote layer, allows you to reprogram the Knobs A, B, C, D

In general, Master Mode is used to set Zone control Out via MIDI for as many as four Zones (A Zone in the MOXF can be designated for internal or external control.
The Remote layer allows you to reprogram the front panel to both control the DAW and to address specifically VSTi plugins.