2nd Gen MT-32 Control ROM

[reines]

Hi,

The service notes for the 2nd gen MT-32 documents only control ROMs up to 2.04.
I can't find documented changes of later control ROMs (2.05, 2.06, 2.07).
Does anyone have this information available?

As a sidenote, the service notes also doesn't mention later serial numbers (ZAxxxxx or FAxxxxx)
Perhaps there is a service bulletin available with all the above information?

Thanks

[NewRisingSUn]

VER 2.05 SN.F**1000-UP
When a MT-32 is playing the tune of "ISM" Library "EL-106-1", the MT-32 may stop sounding at the 10th measure of the tune wrongly. In this case, you must turn the power off once and on again to return to normal conidtion. (Objective version: 2.02, 2.03, 2.04)

VER 2.06 SN.FA31000-UP
- When a MT-32 receives "volume" message of "control change" at time intervals of shorter than several mm seconds, the received "volume" may be wrong. (It has been confirmed that this phenomenon occurs by "volume" message from FC-100MK2 or S-50.)
- When a MT-32 is playing many notes with a tone that consists of structure 11-14, the MT-32 may hang up. (There is no tone that consists of structure 11-14 in the MT-32 preset tone. Therefore this symptom will occur only when a software that has tone edit function is used with the MT-32 and a tone that consists of structure 11-14 is used.)
- When 8 part data are set to the patch temporary area of the MT-32 via MIDI exclusive at a time, the part 2-8 data and bender data will not change correctly. (Another data will change correctly.) (Objective version: 2.00-2.05)

VER 2.07 SN.FB63800-UP
- When a MT-32 receives "8x kk vv" (note off) in overflow assign mode, the MT-32 wrongly transmits "9x kk vv" (note on) instead of "8x kk vv" (note off). (Objective version: 2.06 only)
- With regard to 2-data-byte-message, when "FC" is inserted between the first data byte and the second data byte, the status and the first data byte will become indefinite.

---
I can attest to the first problem that ver 2.07 fixed --- the CM-64 has it as well.

[reines]

Thanks, much appreciated!

All Control ROM versions of CM-64 exhibit this problem (if there there were at all different ROM versions for CM-64...)?