Hi, Everyone (especially you MIDI Mavens)!

I’ve had my head buried in the Data List document, wading though the MIDI implementation as I’ve been configuring an external source (in this case Brainspawn Forte) to automatically set up my MOXF8 when I load a set.

The only thing I lack now is the automation for setting up the audio/midi parameters the same way that “Quick Setup” does. I initially hoped I could just send a message to select a one of the six setups (I know, I’m lazy), but I think what I’m discovering is there is no such message and that I will need to send individual messages to set each audio & midi parameter as desired.

Can anyone confirm that?  I need a break from hexadecimal for awhile, and I’d like to verify my conclusion before I dive back into the base 16 world…

Many thanks,
John

I don’t own a MOXF, but this should do the trick…
See (3-6-3-1) NATIVE PARAMETER CHANGE, MODE CHANGE on page 121 of the MOXF Data List, for the general form of the message(s). Then see Config Number Audio and Config Number MIDI on page 127, for the Address High/Mid/Low and Data bytes.

5pinDIN - 24 June 2014 03:01 PM

I don’t own a MOXF, but this should do the trick…
See (3-6-3-1) NATIVE PARAMETER CHANGE, MODE CHANGE on page 121 of the MOXF Data List, for the general form of the message(s). Then see Config Number Audio and Config Number MIDI on page 127, for the Address High/Mid/Low and Data bytes.

Hi, 5pin.  Thanks for jumping in.  Yes, I was playing around with those earlier. They allow you to alter the parameters of each setup; however, I still haven’t found a message that allows me to choose which setup to activate…

jwatilo - 24 June 2014 03:36 PM

Hi, 5pin.  Thanks for jumping in.  Yes, I was playing around with those earlier. They allow you to alter the parameters of each setup; however, I still haven’t found a message that allows me to choose which setup to activate…

The Data List can sometimes be “fun” to interpret, and without a MOXF I can’t verify MIDI messages. However…

Please try sending the following, and let us know what they do:
F0 43 10 7F 1C 00 00 51 08 00 F7
F0 43 10 7F 1C 00 00 52 09 00 F7

5pinDIN - 24 June 2014 04:17 PM

jwatilo - 24 June 2014 03:36 PM

Hi, 5pin.  Thanks for jumping in.  Yes, I was playing around with those earlier. They allow you to alter the parameters of each setup; however, I still haven’t found a message that allows me to choose which setup to activate…

The Data List can sometimes be “fun” to interpret, and without a MOXF I can’t verify MIDI messages. However…

Please try sending the following, and let us know what they do:
F0 43 10 7F 1C 00 00 51 08 00 F7
F0 43 10 7F 1C 00 00 52 09 00 F7

Right, so the first one sets the AUDIO config for SETUP2 to nothing ("-----" ); the second sets the MIDI config for SETUP3 to nothing ("-----"), just as the documentation indicates.  Works like a charm.  But these changes have no real-time effect until I actually *select* SETUP2 or SETUP3.  And so far, the only way I’ve found to select which SETUP to use is by physically pressing the buttons on the keyboard.

See what I’m saying?

Again, I appreciate the help!

--John

could you work backwards?
record into a sequencer the sys ex info sent out of the MOX when you press the setup buttons then dissect the hex?

jwatilo - 24 June 2014 05:08 PM

Right, so the first one sets the AUDIO config for SETUP2 to nothing ("-----" ); the second sets the MIDI config for SETUP3 to nothing ("-----"), just as the documentation indicates.  Works like a charm.  But these changes have no real-time effect until I actually *select* SETUP2 or SETUP3.  And so far, the only way I’ve found to select which SETUP to use is by physically pressing the buttons on the keyboard.

See what I’m saying?

Again, I appreciate the help!

--John

Interesting - it wasn’t clear what “-----” meant, since page 150 of the Reference Manual only indicates allowable setting of config1~config6, with no mention of a choice of “nothing”. Just out of curiosity, is “-----” what shows on the MOXF’s display when those messages are sent?

Have you determined if the MOXF sends a message when you manually select a Setup at the panel?

5pinDIN - 24 June 2014 06:15 PM

Interesting - it wasn’t clear what “-----” meant, since page 150 of the Reference Manual only indicates allowable setting of config1~config6, with no mention of a choice of “nothing”. Just out of curiosity, is “-----” what shows on the MOXF’s display when those messages are sent?

Have you determined if the MOXF sends a message when you manually select a Setup at the panel?

Yes, “-----” is what is displayed in the panel.

When I manually select a Setup, the keyboard sends out a series of messages mostly corresponding to the individual settings that are changed as a result, except there are a couple (???) that I could not identify based on the documentation:

Audio Connection Mode = 2StereoRec
F0 43 10 7F 1C 01 00 00 0E 01 F7

Direct Monitor Switch A/D In/Part = on
F0 43 10 7F 1C 01 00 00 0F 01 F7

Direct Monitor Switch Part = on
F0 43 10 7F 1C 01 00 00 10 01 F7

Local Control = off
F0 43 10 7F 1C 01 00 00 09 00 F7

???
F0 43 10 7F 1C 01 70 07 00 00 F7

Midi Sync = auto
F0 43 10 7F 1C 01 00 05 0B 02 F7

Midi Clock Out = off
F0 43 10 7F 1C 01 00 05 0C 00 F7

Voice ARP MIDI Out Switch = off
F0 43 10 7F 1C 01 00 00 28 00 F7

ARP MIDI Out Switch (parts 1-16) = off
F0 43 10 7F 1C 01 38 00 01 00 F7
F0 43 10 7F 1C 01 38 01 01 00 F7
F0 43 10 7F 1C 01 38 02 01 00 F7
F0 43 10 7F 1C 01 38 03 01 00 F7
F0 43 10 7F 1C 01 38 04 01 00 F7
F0 43 10 7F 1C 01 38 05 01 00 F7
F0 43 10 7F 1C 01 38 06 01 00 F7
F0 43 10 7F 1C 01 38 07 01 00 F7
F0 43 10 7F 1C 01 38 08 01 00 F7
F0 43 10 7F 1C 01 38 09 01 00 F7
F0 43 10 7F 1C 01 38 0A 01 00 F7
F0 43 10 7F 1C 01 38 0B 01 00 F7
F0 43 10 7F 1C 01 38 0C 01 00 F7
F0 43 10 7F 1C 01 38 0D 01 00 F7
F0 43 10 7F 1C 01 38 0E 01 00 F7
F0 43 10 7F 1C 01 38 0F 01 00 F7

Keyboard Transmit Channel = 1
F0 43 10 7F 1C 01 00 00 0B 00 F7

???
F0 43 10 7F 1C 01 70 02 00 00 F7

I wonder what those mysterious message with the ‘70’ in the high address could be?

This is what I get for trying to push the limits of my gear!  :)

jwatilo - 24 June 2014 07:33 PM

???
F0 43 10 7F 1C 01 70 07 00 00 F7

???
F0 43 10 7F 1C 01 70 02 00 00 F7

I wonder what those mysterious message with the ‘70’ in the high address could be?

This is what I get for trying to push the limits of my gear!  :)

I don’t know what those messages are, but I’ve run into a similar situation with the XF, where I was able to determine what a particular “70” message did. See http://www.motifator.com/index.php/forum/mem/viewthread/469926/

It would be nice if the Data Lists didn’t omit any of the SysEx.

Have you tried sending those “70” messages back to the MOXF? If that doesn’t seem to do anything, you might try changing the sixth byte (model ID) from 01 to 00, and see if that appears to accomplish something.

Pushing the limits should be OK, unless they start pushing back. :-)

There are some hidden items. You can call Yamaha and have someone put in a query about this - if it is important to you. Not sure anyone will have it on the top of their head but could be… 714.522.9000 Mon-Fri 8:30-5:00pm PDT (may take some time but they can find out).

5pinDIN - 24 June 2014 11:10 PM

Have you tried sending those “70” messages back to the MOXF? If that doesn’t seem to do anything, you might try changing the sixth byte (model ID) from 01 to 00, and see if that appears to accomplish something.

I’m quoting myself in order to expand on the model ID issue. All the messages that have the sixth byte as “01” will not be recognized by the MOXF if sent back to it. Rather than explain why, I managed to find related threads on the topic in the XS forum…

http://www.motifator.com/index.php/forum/viewthread/469807

Linked in the above thread:
http://www.motifator.com/index.php/forum/viewthread/451305/

Well, for grins I sent some of those undocumented ‘70’ messages back into the keyboard (changing the Model ID of course), but could not detect what (or if) any parameters might have been changed.

But that’s OK.  I’m able to do what I need to do by sending individual messages for each parameter that would be changed by doing a “Quick Setup”.  While I’m naturally curious, I don’t have the time to delve any deeper.

Thanks everyone—especially 5pin—for all of the useful information!

Regards,
John

jwatilo - 26 June 2014 09:22 AM

Well, for grins I sent some of those undocumented ‘70’ messages back into the keyboard (changing the Model ID of course), but could not detect what (or if) any parameters might have been changed.

But that’s OK.  I’m able to do what I need to do by sending individual messages for each parameter that would be changed by doing a “Quick Setup”.  While I’m naturally curious, I don’t have the time to delve any deeper.

Thanks everyone—especially 5pin—for all of the useful information!

Regards,
John

Thanks for the follow-up. By capturing the messages generated by button presses, you should mostly only have to change the model ID byte rather than needing to create each message from scratch.

If I had a MOXF I’d investigate further, but an XS and an XF are sufficient for now.  :-)