Tech Note:Active Page: Difference between revisions
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
''This Page Only'' triggers that particular widget on that particular page whenever the triggering MIDI comes in. The binding is to that particular widget. You can change the page's layout and the binding isn't affected because the binding targets the widget via a unique internal ID. | ''This Page Only'' triggers that particular widget on that particular page whenever the triggering MIDI comes in. The binding is to that particular widget. You can change the page's layout and the binding isn't affected because the binding targets the widget via a unique internal ID. | ||
''Active Page'' page bindings trigger only a widget on the page that it active when the triggering MIDI comes in. Unlike ''This Page Only'' bindings, the binding is to the widget at particular logical position. If your pages are not (logically) identical, it is possible that different widgets will be triggered by the same MIDI on different pages. For example, if you MIDI Learn a button called ''Play All'' for the ''Active Page'' and ''Play All'' is the first button on the page, you are really MIDI Learning the first button on the page. If your ''Play All'' is not the first button on page 2, it will not be triggered when page 2 is active. | ''Active Page'' bindings are based on the assumption that each page has an identical. If your pages are not identical, your ''Active Page'' bindings may not work as you expected. ''Active Page'' page bindings trigger only a widget on the page that it active when the triggering MIDI comes in. Unlike ''This Page Only'' bindings, the binding is to the widget at particular logical position. If your pages are not (logically) identical, it is possible that different widgets will be triggered by the same MIDI on different pages. For example, if you MIDI Learn a button called ''Play All'' for the ''Active Page'' and ''Play All'' is the first button on the page, you are really MIDI Learning the first button on the page. If your ''Play All'' is not the first button on page 2, it will not be triggered when page 2 is active. | ||
Revision as of 05:41, 3 April 2026
When MIDI Learn a widget, there is an option to MIDI Learn for This Page Only or for the Active Page. As explained in the Loopy Pro manual.
This Page Only triggers that particular widget on that particular page whenever the triggering MIDI comes in. The binding is to that particular widget. You can change the page's layout and the binding isn't affected because the binding targets the widget via a unique internal ID.
Active Page bindings are based on the assumption that each page has an identical. If your pages are not identical, your Active Page bindings may not work as you expected. Active Page page bindings trigger only a widget on the page that it active when the triggering MIDI comes in. Unlike This Page Only bindings, the binding is to the widget at particular logical position. If your pages are not (logically) identical, it is possible that different widgets will be triggered by the same MIDI on different pages. For example, if you MIDI Learn a button called Play All for the Active Page and Play All is the first button on the page, you are really MIDI Learning the first button on the page. If your Play All is not the first button on page 2, it will not be triggered when page 2 is active.
