Memory size has been a complaint before. Montage supports less sample memory than the predecessor which seems like a step in the wrong direction. MODX is at parity with its predecessor which doesn't fit the usual upward feature curve customers tend to have. Comparing memory sizes vs. general industry trends like sample libraries is not very informative since this is apples/oranges in the context of how Yamaha architects its keyboards. Would have been nice to see some upward specs like 1.75GB MODX and 3GB Montage. That said, it is what it is.

I have had fairly good results searching the documentation PDFs. That said - there are certainly undocumented "gotchas" which are mostly covered by the online tutorials.

That is not how this works at all. There are separate Bank Select and Program Changes for recalling entire Performances, versus recalling an individual Part within a Performance. This occurs no matter what is selected. Setting up to record as a 16 Part Multi-timbral MODX, is as simple as starting with the appropriate Init Performance.
Press [CATEGORY]
Touch “Init”
Select “Multi/GM”
This activates all sixteen Parts by placing a default instrument sound in each of the slots. You can now use the appropriate Bank Select and PC to recall the Single instrument you want in each of the sixteen Parts.

Bad Mr. I tried to do what you suggested, but it just doesn't work. I have my Multi/GM performance set up, but anytime I send a PC on a specified channel, the Performance (Multi/GM) changes according to the PC sent, no matter the channel I'm using.

What I need is to change parameters (PC, Volume, Pan, Rev Send. etc.) for each Part inside the Multi/GM Performance. This doesn't happen, even if I set appropriate MSB, LSB, PC to recall the sound I need. More, one of the Bank selectors activates the "Arp On" function, which is very strange.

 

anytime I send a PC on a specified channel, the Performance (Multi/GM) changes according to the PC sent

Just to clarify - do you mean that when you send the PC to a specific channel - the one PART matching the channel number (within the Multi/GM Performance) changes according to the PC sent? Your statement, possibly because the wording may not be clear, seems to indicate when you send the PC that the entire Performance changes - not just the single PART.

That said - IF the entire Performance changes instead of a single PART - then this would be a case of using the wrong MSB/LSB pair. The pair should be for the "Single Part" Performance change - not "Multi Part". The Single-PART ones affect only the single PART matching the MIDI channel used to send the message.

Exactly Jason. That's what happens. I found the answer to my problem in another post, the reply was yours and it was more helpful.

Yes, I used the wrong MSB value, but saying it's wrong doesn't help. In that other post of yours I found out that 64 is for Performance change, while 63 is for Part change.
This simple information alone solved my problem and I think (as a ton of other things) it should be told plain and simple in the basic manual, which is not well done, in my opinion.

I think it may be helpful to tell you why I got confused with the MSB value: simply said, when you look for a Performance's properties, it reads Bank 64, and it's right. But if you want to merge that Perf into another one, it should be said you have to use the value of 63 if you want to change instruments inside it.

Well, I was was working on understanding what you were communicating first before blasting out the "answer" if you were indeed using the wrong (multi-PART Performance) one. When a post is unclear and there could be multiple interpretations of intent behind a message - I would, in the past, spell out the answers to both scenarios. I've sometimes gotten push-back where the poster was offended like I was "talking down" by covering the bases - so I was working to be solid I understood the nature of your issue first before recommending a specific remedy.

Glad you could self-serve and found your way. Hopefully the param-with-part settings now match Phil's suggestion so you can more effectively use MODX in your workflow.