I was working my way through the 4th article by Manny Fernandez for his FM Explorations series.
https://yamahasynth.com/learn/montage-series-synthesizers/mannys-fm-xplorations-article-4/
When I was checking out part 2 for Motion Sequences and was on the 'Edit Part n -> Motion Seq - Lane' screen
I noticed the lights beneath the Part Buttons on the front panel. Buttons 1,3,5,7 were solid green
and buttons 2,4,6,8 were flashing blue.
The various colors and solid versus flashing must mean something but I haven't figured it out yet.
What I have seen in the past is this:
1. a button that is OFF means that function isn't available in the current context
2. a button that is DIM means the function is available but isn't current being used
3. a button that is a BRIGHT color means the function is both available AND is being used.
The problem is I can't figure out what the buttons are indicating for that performance.
Testing shows that the button state and color are saved with the performance and can be set even if no intentional
programming has been done.
The lane screen is shown on p.46 of the ops doc and the 8 part buttons are under the 8 sliders as shown on p.512.
I was able to reproduce the light combination using this simple test:
1. load Init Normal (AWM2) - FM-X will work also but not AN-X
2. go to the 'Edit Part 1 -> Motion Seq -> Lane' screen
3. notice that the 8 part button lights are all solid green
4. toggle buttons 2,4,6,8 to turn them solid blue.
5. press 'shift' and toggle buttons 2,4,6,8 and they will now flash solid blue
6. select a different lane and notice the pattern changes to the default but changes back to the solid/flashing pattern
when you reselect the lane you were using. Clearly whatever is being done is specific to the lane.
7. store the performance as a new performance
8. switch to a different performance and then reload the test performance
9. go to the 'Edit Part 1 -> Motion Seq -> Lane' screen
10. notice that the part button lights 1,3,5,7 are all solid green and lights 2,4,6,8 are flashing blue.
I was expecting the button/light configuration to be saved and restored.
The color and solid/flashing state appear to specific to a lane but none of the above actually depends on the Master
or Part Motion Seq switches being ON, any control assignments being done, or on any other programming.
The question is: what do the colors and flashing represent?
In the absence of any programming what does the color change when pressing a part button represent?
Similarly, for the above test what does the solid vs. flashing mean?
And are there any implications when the performance is actually being used?
Typically the buttons would be used to select a part (when 'shift' is not used) or to select an element/operator when 'shift' is used.
Once again, I'm hoping I've missed something really simple.
Maybe timestamp the video so it's easier to locate what you're referring to. I did slide around different times looking for it.
Current Yamaha Synthesizers: Montage Classic 7, Motif XF6, S90XS, MO6, EX5R
I guess what you're saying is that the video doesn't show anything flashing but your Montage M flashes something which probably isn't something a Montage Classic owner could observe.
Now the M "animates" the motion sequence so that difference may cascade to other parts of the interface. Can't really help you there.
Current Yamaha Synthesizers: Montage Classic 7, Motif XF6, S90XS, MO6, EX5R
Solved! - the button color and state, and sliders, edit sequence steps
I guess what you're saying is that the video doesn't show anything flashing but your Montage M flashes something which probably isn't something a Montage Classic owner could observe.
Yes - those videos are for the classic. So they don't show or discuss what happens on the M.
Turns out the button color (green/blue) and state (off, solid, flashing) and even the sliders reflect Motion Sequence parameters and can be used to edit those parameters just like they are used to select parts or control elements.
The docs never mention using them to edit sequence parms.
P.42 of the Montage classic reference doc shows a graphic when editing a motion sequence.
P.243 of the M doc shows a corresponding graphic
On the classic you have: Pulse A and B and Direction Forward/Reverse.
On the M you have: Pulse A and B and two small triangles (on the row to the right of 'Job') that represent Forward/Reverse. The left triangle is forward and the right one is reverse. Whichever one is lit is the 'chosen' one for that step.
Button Color: Green -> Pulse A, Blue -> Pulse B
Button State: Solid -> Forward, Flashing -> Reverse
The 8 buttons correspond to either sequence steps 1-8 or steps 9-16 depending on whether the 'Part group [1-8/9-16]/[USB AUDIO / A/D INPUT] button is flashing.
P.20 of the M quick guide has a graphic showing that button and the part buttons and says section 5-13 says this:
5-13 PART buttons (EL/OP/OSC)
When the Part group [1-8/9-16]/[USB AUDIO / A/D INPUT] button is set to “1-8/9-16,” you can use these buttons to
select Parts 1 to 8 or Parts 9 to 16.
When the Part group [1-8/9-16]/[USB AUDIO / A/D INPUT] button is set to “USB AUDIO / A/D INPUT,” you can use these
buttons to select DIGITAL IN, USB MAIN, USB ASSIGN, and A/D INPUT.
By pressing one of these buttons while holding down the [SHIFT] button, you can use the appropriate PART button to
select Elements 1 to 8, Operators 1 to 8, Oscillators 1 to 3, or Noise.
You use that 'Part group' button to switch the buttons (hold 'shift' down and press the button) and sliders from representing parts 1-8 to control parts 9-16 instead.
Likewise it switches between motion sequence steps 1-8 and steps 9-16 for the buttons and sliders.
So if you have a lane selected or are editing a sequence the buttons and sliders are actually programming the steps of the sequence. If you accidentally nudge a slider, and it is synced, it will change the value for that step. If you then restore that performance for any reason the change is permanent like other changes.
As bad luck would have it the performance in the article used nearly identical parms for Pulse A and B so it wasn't visually or aurally obvious that anything was happening when I changed the button state or color.
More bad luck since all of my sliders were at minimum but all of the sequence step values were at maximum. So moving a slider didn't change anything because the sliders weren't synced/hooked.