MONTAGE M is Yamaha's first MIDI 2.0-compatible synthesizer

Reading chapter 7, I don't see anything that couldn't have been published after Montage M released firmware 2.0.  

I checked based on the Singapore version and that seems to be correct but the wording "couldn't have been' is significant since it has info that I haven't seen anywhere else - at least not from Yamaha. I put 1st line above the quote since the 1st line is the only thing most people will see until the forum is fixed. They don't seem to be reading the thread you posted about the '...'.

This is the link with added hyphens to make the link available - remove the hyphens and you should get the real link.

-h-t-t-p-s-:-/-/-s-g-.-y-a-m-a-h-a-.-c-o-m-/-en/products/contents/music_production/synth_50th/history/chapter007.html

There is a LOT of info related to MIDI 2.0 capability that people, myself included, have been wondering about. Paragraphs 2,3 and 4 are pretty detailed.

But there are still some knowledge gaps between what MIDI 2.0 resolution capability is actually used in the M. 

MIDI 2.0 data areas feature 32 usable bits for a staggering maximum resolution of nearly 4.3 billion steps (232 = 4,294,967,296). Velocity is also dramatically improved, with 16 bits for a maximum of 65,536 values.

. . .

It should be noted that these figures only represent what is possible with MIDI 2.0; actual equipment may not be capable of such high resolution.

My M8X only lets you choose velocity values from 0-127. So even if you could send a MIDI 2.0 velocity value with 16 bit resolution the current M would likely just scale it to the lower range. And Windows doesn't yet have any MIDI 2.0 device drivers.

So there is still a ways to go - but Yamaha is definitely setting the stage for the next resolution generation.

My initial thought was that Chapter 7 was withheld pending an announcement of say poly after touch on the M6 and M7 with 50th anniversary white versions.  40th anniversary had Motif XF white versions.   Or some other announcement that just couldn't be leaked in chapter 7.  Turns out this wasn't what the holdup was about and although I agree there's content that I don't think was mentioned elsewhere - however, that content isn't spoiling anything that hasn't already been public.