During testing it was discovered that there appear to be two new parameters that are saved into scene memory and also discovered that the actual positions of the Arpeggio and Motion Seq Memorize switches is reversed in the doc from the a dump shows.

When debugging a problem with some SysEx code we tracked the cause to incorrect information on p.234 of the ‘MONTAGE-M_DL_En_E0_web.pdf’ Data List doc in table ’06 02 0c’ that contains the performance common scene data.

The table size is shown as 18 bytes when a Bulk Dump (OS 2.01) shows it is really 20 bytes. It is possible that the table was correct for the original OS and the OS 2.00 update but was changed as part of the OS 2.01 update. I have no way of knowing.

This is one sample export record for scene 1

F0 43 00 7F 1C 00 17 0D 06 02 00 00 00 01 00 01 00 00 00 00 00 01 01 01 01 01 01 01 01 00 61 F7

06 02 00

0x00 00

0x01 00

0x02 01 - this is the Scene Motion Seq Memorize switch setting

0x03 00 - this is the Arp switch

0x04 01

0x05 00

0x06 00

0x07 00

0x08 00

0x09 00

0x0A 01 - Scene Super Knob Link Switch 1

0x0B 01

0x0C 01

0x0D 01

0x0E 01

0x0F 01

0x10 01

0x11 01 - Super Knob Link Switch 8

0x12 00 - Scene Keyboard Control Switch Memorize Switch

0x13 61 - ? What is this?

F7 – end of record

There are at least THREE mismatches between the above and the doc.

1) Notice that 0x02 and 0x03 are reversed from what the doc shows. The 0x02 is actually the Motion Seq Memorize switch but the doc shows it as the Arp Memorize switch. That is the one that caused our problem and took a while to track down.

2) Notice that the dump shows 0x0A as the position for super knob link switch 1 but the doc shows it as 0x09 – that suggests there is a new parameter somewhere earlier in the table. We haven’t been able to determine just where the new parameter is and/or whether it was inserted in-between other parameters which are now shifted to a new position.

3) There appears to be a new parameter at the end of the table at position 0x13 with a value of 0x61 (97 decimal). We have been unable to determine what this parameter represents or why it got saved to the scene. Our concern lies in the fact that the value at that position is different for the other seven scenes:

Scene 2 = 0x62

Scene 3 = 0x61

Scene 4 = 0x60

Scene 5 = 0x5F

Scene 6 = 0x5E

Scene 7 = 0x5D

Scene 8 = 0x5C

Curiously the values are sequentially decreasing. Our concern is that ‘unknown’ parameter value is being changed for each scene and we have no idea what it might be doing or how to change it.

The above test info was using an Init Normal (AWM2) performance and we were only testing the motion seq and arp switches to determine which was which.

We have emailed Tech Support to try to get an updated version of this table and will post the info if we get it.

I'm glad to know there appear to be two new parameters added to scene saves. I just wish I knew what they are so I can check them out.