Found it!
Utility> settings>Advanced >Midi: device number (1)
Device number was set to 2

Just so you know, DEVICE NUMBER identifies your MODX from any others receiving a System wide message. If you had two MODX’s, for example, you would make one of them Device #1 and the other Device #2, this way you can designate which one of the two you want to address. Device Number allows multiple devices of the same make and model to exist within a system, yet remain individually addressable. There are 16 Device Numbers provided by MIDI... for those with sixteen identical models can create unique System Exclusive messages for each individual instrument!

If you own only one MODX, you should leave this Device Number Set to either All or 1.

Enjoy Soundmondo...

Hi,

I needed to send SysEx messages for one of my projects, but it doesn’t work properly.

I’m trying to control the patches of Yamaha MOXF6 and Yamaha MOXF8 keyboards with an arduino device (both ‘at the same time’ on stage). I’m using standard midi cables for signal transmission. (Arduino → MOXF8 MIDI in, and MOXF8 MIDI thru-> MOXF6 MIDI in connections)

On the MOXF8 I set the Device number and Basic RcvCh to 1, and on the MOXF6 I set both to 2.
Within the mode, I can distinguish the patch change with using a midi channel.
I can distinguish which keyboard I send the SysEx message to using the device number in this 2-keyboards-chain.

My problem is that if I send 2 SysEx msgs to both of them, both ‘receive’ the other’s SysEx msg, and the one that is not for its own device number says ‘Device number mismatch’. Of course, it still sets the mode for it in the background because of the other well-addressed message, but when changing modes, you have to accept the ‘error message’ on both keys, which can be annoying during a live concert.
Can’t this ‘Device number mismatch’ report be turned off? Or do you have any other ideas?

These two messages go through the chain to switch modes:
SysEx to MOXF8:
F0 43 10 7F 1C 00 0A 00 01 00 F7
SysEx to MOXF6:
F0 43 11 7F 1C 00 0A 00 01 01 F7

Thank you very much in advance!

What are you trying to do with these messages?  Because after the 1C, I would expect to see an 07 (which is a model ID) given the context of what preceded.

If you could, detail what SysEx you're trying to send (parameter change, etc) and more details about exactly what you're trying to do and I can form a valid SysEx for that intent to try out.

What are you trying to do with these messages?  Because after the 1C, I would expect to see an 07 (which is a model ID) given the context of what preceded.

Not sure I understand that - OP provided the SysEx messages. They include '00' because that is the model ID for the MOXFs being used. The '07' you mention is for a Modx.

See the table at the top of p.125 of the data list doc.

OP is trying to do a mode change to 0 (Voice) for the F8 and to 1 (Performance) for the F6. The issue is that they are sending both messages to both instruments but the instruments are NOT ignoring the messages intended for the other instrument.

What does 'you have to accept the ‘error message’ on both keys' mean? Doesn't the message disappear by itselft?

Don't have a MOXF but on a Montage M8X the 'Device number mismatch' goes away on its own after a second or two.

Oops.  Been dealing with my Internet provider for a week with the service going down for the duration.  Forces using my phone which takes me down a notch.  Thanks for clarifying.

Ignore my last message.

Your messages look properly formed and so I go back to my initial (unpublished) reaction: I'm surprised the device number feature works like this.  I agree that this should seamlessly allow for multiple instruments of the same family to be connected on a single MIDI bus and individually addressed.  Looks like there's a seam.

Yes, that's exactly the problem, the message doesn't disappear by itself. It receives and processes the appropriate messages in the background, but the error message covers everything until I close it.

I suggest you use the 'Contact Us' link to ask support directly if that is 'working as designed' on the Modx. Include a link to this thread and please post any reply you get so we know what happened.

My experience on other Yamaha Synths is that the global commands (essentially a 'broadcast' message) are sent to all devices but instruments whose device id doesn't match the id in the message they ignore the message altogether or briefly display that ‘Device number mismatch’ message but without requiring any user intervention.

Displaying the message is useful as a visual indicator, during testing, that a command is invalid. But the message should go away on its own. Tests on Montage show that is just what happens.

There is no way that I am aware of to control whether the message is displayed or not.

If you send a properly formed SysEx to an address that doesn't belong to the keyboard then the keyboard should ignore it (for example: keyboard configured as device 4 and the incoming message is device 3).

In Omni mode, it will listen to every channel - so there should be no complains when in omni mode no matter the address as long as the device identifiers match.

This is me agreeing something seems wrong with the implementation.  

Posted by: Toby

↑

I suggest you use the 'Contact Us' link to ask support directly if that is 'working as designed' on the Modx. Include a link to this thread and please post any reply you get so we know what happened.

My experience on other Yamaha Synths is that the global commands (essentially a 'broadcast' message) are sent to all devices but instruments whose device id doesn't match the id in the message they ignore the message altogether or briefly display that ‘Device number mismatch’ message but without requiring any user intervention.

Displaying the message is useful as a visual indicator, during testing, that a command is invalid. But the message should go away on its own. Tests on Montage show that is just what happens.

There is no way that I am aware of to control whether the message is displayed or not.

It's a good idea. I wrote a mail to the Yamaha support, and I got the following answer:

'We understand, that you would like the "ID mismatch warning" to dissapear without manual confirmation.
Unfortunately, there is no easy solution four your this problem. It is not possible to change the message behaviour in the MOXF6 removed link
MOXF series is not actively supported any longer, which means, we do not have the instruments at hand for testing.

Maybe it could be helpful to send other MIDI messages to close the message window, but we can't test it here. Please try to send some
system messages like realtime commands start/stop etc. There is a slight chance, that they can close the nagging message window.

The only possible workaround would require a direct wiring using two seperate MIDI Ports, so that one instruments would not at all
receive the Sysex-Data intended for the other instrument.

But this requires a complete restructuring of your Arduino-setup.'

The cheapest way would be to add a second arduino MIDI out port and isolate everything by distinct MIDI buses - one for each keyboard.  The expensive way would be to use some hardware to split the one MIDI bus then on each leg of the split insert a hardware device that filters out certain SysEx messages (like a MIDI solutions event processor or a hardware box from Bome).   I can't consult without a lot of digging on which filter hardware can do the job of say looking for a pattern match on a given byte number in a SysEx message and not passing it along.  SysEx isn't generally well supported and I have my doubts the event processor product will fit the bill.

And then an uber expensive route would be to replace the two keyboards with ones that better respect the point of SysEx device number addressing and keep everything else the same (except for the software - since SysEx will change).

Congrats on getting a reply from Yamaha support!

Because you ask a 'how do I do xxx?' question and provided ALL the info needed to reproduce the problem you made it much easier for them to respond and try to answer your question. 

Maybe it could be helpful to send other MIDI messages to close the message window, but we can't test it here. Please try to send some
system messages like realtime commands start/stop etc. There is a slight chance, that they can close the nagging message window.

Make sure you try that method since it could work. The OS code is likely using an interrupt driven mechanism to respond to incoming messages. So even though it opened a Modal window that waits for a response a new incoming message could force that window to close so it can process the new message.

If so you would just need to use a two-step process:

1. send your global message to all devices

2. send a dummy 'do nothing' message to all devices

Since that 'modal' window problem doesn't exist on the new Montage M8X the developers likely identified it as a problem on the Moxf and changed the code to non-modal after a couple of seconds. I don't know when they did that.

Someone with a Modx or classic Montage would need to do their own test.

It is always worth trying the 'Contact Us' link to see if you can get an answer even though you may not get one. You will have the best chance when you ask SPECIFIC questions and provide a 'step-by-step' guide for how to reproduce the problem.

Thanks for posting the follow-up.

Posted by: Toby

↑

Congrats on getting a reply from Yamaha support!

Because you ask a 'how do I do xxx?' question and provided ALL the info needed to reproduce the problem you made it much easier for them to respond and try to answer your question. 

Maybe it could be helpful to send other MIDI messages to close the message window, but we can't test it here. Please try to send some
system messages like realtime commands start/stop etc. There is a slight chance, that they can close the nagging message window.

Make sure you try that method since it could work. The OS code is likely using an interrupt driven mechanism to respond to incoming messages. So even though it opened a Modal window that waits for a response a new incoming message could force that window to close so it can process the new message.

If so you would just need to use a two-step process:

1. send your global message to all devices

2. send a dummy 'do nothing' message to all devices

Since that 'modal' window problem doesn't exist on the new Montage M8X the developers likely identified it as a problem on the Moxf and changed the code to non-modal after a couple of seconds. I don't know when they did that.

Someone with a Modx or classic Montage would need to do their own test.

It is always worth trying the 'Contact Us' link to see if you can get an answer even though you may not get one. You will have the best chance when you ask SPECIFIC questions and provide a 'step-by-step' guide for how to reproduce the problem.

Thanks for posting the follow-up.

I found that the mentioned midi realtime command is only FA, ​​FB or FC (from data manual). So I tried to send the SysEx message to MOXF6 (with invalid id for the error log...) and then I tried to send the start, continue, stop bytes, but the message did not disappear. Could I send wrong data, or wrong format or something else is need for realtime command execution?

I tried these:

F0 43 10 7F 1C 00 0A 00 01 01 F7

FA

F0 43 10 7F 1C 00 0A 00 01 01 F7

FB

F0 43 10 7F 1C 00 0A 00 01 01 F7

FC