
66
changes. Holding the button down until ready to trigger it. Or it could be to overcome user behavior and
the lead foot!
Parameter #3
By default, buttons are not defined to trigger scrolls. What in the world is that? Recall that a button can be
programmed to process a Bank UP/DOWN, Preset UP/DOWN, Song UP/DOWN, Page UP/DOWN, Set-List
UP/DOWN, CONTEXT UP/DOWN, and so on. These commands are capable of being “ARMED only” by
default, or TRIGGERED. Imagine the ability to Change Banks (BANK UP) and press it multiple times
without actually changing banks until the proper bank is found. Each of the UP/DOWN functions are
called “SCROLL” functions. Any modifications to a SCROLL function are NOT processed until either (1) an
ENTER/SELECT button is pressed, or any button that is set to “Process Scroll(s).
Perhaps a natural example of this would be preset buttons. It would make sense to leave the BANK
UP/DOWN buttons with the default setting of “Don’t Process Scroll”, and set each of the Preset buttons
with a “Process Scroll(s)” trigger. In this example, we can BANK UP/DOWN all day, and only see on the
LCD what bank we are about to select. Nothing will happen until we press one of the Preset Buttons.
Being set to Trigger Scrolls, it will fire the trigger, notice the BANK change, and process it. It will then
select the first preset in the Bank that was just activated and load it.
Below are a couple DEFAULT PAGES IN A SAMPLE LAYOUT FORMAT (B1-B12 are shown)
01 Trigger Scroll
Don’t Process Scroll
01 Trigger Scroll
Process Scroll(s)
Содержание Mini
Страница 1: ...Table of Contents...
Страница 31: ...31 MSG01 CHANGE PAGE 08 011 LOOPERpg MSG02 CHANGE PAGE 08 010 MainPage...
Страница 67: ...67...
Страница 98: ...98 www FAMCmusic com...